1	20:49:09.202	'66036191': ping failed
1	20:49:09.202	'66036191': datacenter connecting failed [6]
0	20:49:09.671	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 72.94 ms)
0	20:49:10.187	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 72.94 ms)
0	20:49:10.734	'66036191': previous successful authorization performed from 152.32.252.153
0	20:49:12.405	'66036191': auto connecting to a better access point DC#2 (ping is 2.23 ms)
0	20:49:12.937	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 2.23 ms)
0	20:49:16.562	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 2.23 ms)
0	20:49:16.687	'66036191': previous successful authorization performed from 152.32.252.153
1	21:36:30.020	'66036191': ping failed
1	21:36:30.020	'66036191': datacenter connecting failed [6]
0	21:36:30.598	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 65.76 ms)
0	21:36:31.129	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 65.76 ms)
0	21:36:31.348	'66036191': previous successful authorization performed from 152.32.252.153
1	22:53:00.649	'66036191': ping failed
1	22:53:00.649	'66036191': datacenter connecting failed [6]
1	22:53:21.867	'66036191': connect failed [ûÓÐÁ¬½Ó]
0	22:53:32.664	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	22:53:32.742	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	22:53:33.008	'66036191': previous successful authorization performed from 152.32.252.153
0	22:53:33.649	'66036191': ping to current access point DC#2 is 4.28 ms
1	22:58:17.305	'66036191': datacenter connecting failed [6]
0	22:58:17.914	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 64.97 ms)
0	22:58:18.930	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 64.97 ms)
0	22:58:19.164	'66036191': previous successful authorization performed from 152.32.252.153