1	09:00:37.878	'66036191': ping failed
1	09:00:37.878	'66036191': datacenter connecting failed [6]
0	09:00:38.081	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 7.30 ms)
0	09:01:41.597	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 7.30 ms)
0	09:01:43.956	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 7.30 ms)
0	09:01:44.956	'66036191': auto connecting to a better access point DC#2-1 (ping is 5.81 ms)
0	09:01:50.143	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 5.81 ms)
0	09:01:53.534	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 5.81 ms)
0	09:01:53.972	'66036191': previous successful authorization performed from 152.32.252.153
0	09:03:22.378	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 5.81 ms)
0	09:03:24.565	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 5.81 ms)
0	09:04:30.615	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 14.57 ms)
0	09:05:36.834	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 73.56 ms)
0	09:06:42.771	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 85.45 ms)
1	09:07:48.521	'66036191': connect failed [ûÓÐÁ¬½Ó]
0	09:07:53.787	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	09:08:05.631	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	09:08:07.068	'66036191': previous successful authorization performed from 152.32.252.153
0	09:08:11.740	'66036191': ping to current access point DC#2 is 62.20 ms
1	16:00:25.058	'66036191': ping failed
0	16:00:25.058	'66036191': login datacenter on HeroCapitalPty-Server
0	16:00:25.355	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 9.63 ms)
0	16:01:30.793	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 89.75 ms)
0	16:01:35.793	'66036191': login datacenter on HeroCapitalPty-Server through DC#5 (ping: 89.75 ms)
0	16:01:36.371	'66036191': previous successful authorization performed from 152.32.252.153
0	16:01:40.262	'66036191': auto connecting to a better access point DC#2-1 (ping is 14.32 ms)
0	16:01:40.449	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 14.32 ms)
0	16:02:45.637	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 26.96 ms)
0	16:02:48.933	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 26.96 ms)
0	16:02:52.199	'66036191': previous successful authorization performed from 152.32.252.153
1	23:09:21.898	'66036191': ping failed
0	23:09:21.898	'66036191': login datacenter on HeroCapitalPty-Server
0	23:09:22.773	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 91.63 ms)
0	23:09:23.976	'66036191': login datacenter on HeroCapitalPty-Server through DC#5 (ping: 91.63 ms)
0	23:09:24.679	'66036191': previous successful authorization performed from 152.32.252.153
0	23:09:28.351	'66036191': auto connecting to a better access point DC#2-1 (ping is 3.47 ms)
0	23:09:28.570	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 3.47 ms)
0	23:09:30.304	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 3.47 ms)
0	23:09:30.773	'66036191': previous successful authorization performed from 152.32.252.153
1	23:11:10.398	'66036191': ping failed
1	23:11:10.398	'66036191': datacenter connecting failed [6]
0	23:11:10.570	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 4.16 ms)
0	23:11:15.398	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 4.16 ms)
0	23:11:16.195	'66036191': previous successful authorization performed from 152.32.252.153