1	11:44:32.991	'66036191': ping failed
1	11:44:33.194	'66036191': ping failed
1	11:44:33.194	'66036191': datacenter connecting failed [6]
0	11:44:33.756	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 3.30 ms)
0	11:44:34.256	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 3.30 ms)
0	11:44:34.710	'66036191': previous successful authorization performed from 152.32.252.153
0	11:44:41.491	'66036191': auto connecting to a better access point DC#2 (ping is 2.35 ms)
0	11:44:41.788	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 2.35 ms)
0	11:44:41.850	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 2.35 ms)
0	11:44:42.319	'66036191': previous successful authorization performed from 152.32.252.153
1	15:09:40.727	'66036191': ping failed
0	15:09:40.743	'66036191': login datacenter on HeroCapitalPty-Server
0	15:09:41.743	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 2.94 ms)
0	15:09:42.305	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 2.94 ms)
0	15:09:43.149	'66036191': previous successful authorization performed from 152.32.252.153
0	15:09:51.243	'66036191': auto connecting to a better access point DC#2 (ping is 2.25 ms)
0	15:09:51.508	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 2.25 ms)
0	15:09:51.602	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 2.25 ms)
0	15:09:52.071	'66036191': previous successful authorization performed from 152.32.252.153