1	12:13:24.726	'66036191': ping failed
0	12:13:24.726	'66036191': login datacenter on HeroCapitalPty-Server
0	12:13:25.133	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 65.27 ms)
0	12:13:25.633	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 65.27 ms)
0	12:13:25.851	'66036191': previous successful authorization performed from 152.32.252.153
0	12:13:29.367	'66036191': auto connecting to a better access point DC#2 (ping is 3.82 ms)
0	12:13:29.664	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.82 ms)
0	12:13:29.773	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.82 ms)
0	12:13:29.898	'66036191': previous successful authorization performed from 152.32.252.153
1	22:05:24.614	'66036191': ping failed
1	22:05:24.614	'66036191': datacenter connecting failed [6]
0	22:05:25.536	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 67.12 ms)
0	22:05:26.052	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 67.12 ms)
0	22:05:26.270	'66036191': previous successful authorization performed from 152.32.252.153
0	22:05:26.786	'66036191': auto connecting to a better access point DC#2 (ping is 3.07 ms)
0	22:05:27.177	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.07 ms)
0	22:05:27.270	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.07 ms)
0	22:05:27.395	'66036191': previous successful authorization performed from 152.32.252.153