1	21:25:50.213	'66036191': ping failed
0	21:25:50.244	'66036191': login datacenter on HeroCapitalPty-Server
0	21:25:50.666	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 64.02 ms)
0	21:25:53.197	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 64.02 ms)
0	21:25:53.432	'66036191': previous successful authorization performed from 152.32.252.153
0	21:25:57.213	'66036191': auto connecting to a better access point DC#2 (ping is 4.13 ms)
0	21:26:00.854	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 4.13 ms)
0	21:26:05.760	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 4.13 ms)
0	21:26:05.869	'66036191': previous successful authorization performed from 152.32.252.153
1	21:36:53.869	'66036191': ping failed
0	21:36:53.869	'66036191': login datacenter on HeroCapitalPty-Server
0	21:36:54.385	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 65.62 ms)
0	21:36:55.057	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 65.62 ms)
0	21:36:55.291	'66036191': previous successful authorization performed from 152.32.252.153
1	21:38:55.197	'66036191': ping failed
1	21:38:55.197	'66036191': datacenter connecting failed [6]
0	21:39:04.900	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 92.64 ms)
0	21:40:05.369	'66036191': login datacenter on HeroCapitalPty-Server
1	21:40:10.572	'66036191': connect failed [ûÓÐÁ¬½Ó]
0	21:40:12.650	'66036191': auto connecting to a better access point DC#2 (ping is 2.75 ms)
0	21:40:15.791	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 2.75 ms)
0	21:40:15.869	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 2.75 ms)
0	21:40:16.010	'66036191': previous successful authorization performed from 152.32.252.153
0	21:53:42.021	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 2.75 ms)
0	21:53:42.100	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 2.75 ms)
0	21:53:42.225	'66036191': previous successful authorization performed from 152.32.252.153
1	21:54:02.131	'66036191': ping failed
0	21:54:02.131	'66036191': login datacenter on HeroCapitalPty-Server
0	21:54:02.740	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 65.18 ms)
0	21:54:03.256	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 65.18 ms)
0	21:54:03.490	'66036191': previous successful authorization performed from 152.32.252.153
1	22:37:53.923	'66036191': ping failed
1	22:37:53.923	'66036191': datacenter connecting failed [6]
0	22:37:54.392	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 91.78 ms)
0	22:38:12.001	'66036191': login datacenter on HeroCapitalPty-Server through DC#5 (ping: 91.78 ms)
0	22:38:14.454	'66036191': previous successful authorization performed from 152.32.252.153
0	23:22:23.280	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 91.78 ms)
0	23:22:24.311	'66036191': login datacenter on HeroCapitalPty-Server through DC#5 (ping: 91.78 ms)
0	23:22:24.577	'66036191': previous successful authorization performed from 152.32.252.153
0	23:22:25.905	'66036191': auto connecting to a better access point DC#2 (ping is 3.57 ms)
0	23:22:26.280	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.57 ms)
0	23:22:26.343	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.57 ms)
0	23:22:26.468	'66036191': previous successful authorization performed from 152.32.252.153