1	09:15:54.776	'66036191': ping failed
0	09:15:54.776	'66036191': login datacenter on HeroCapitalPty-Server
0	09:15:59.182	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 6.00 ms)
0	09:17:04.557	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 76.32 ms)
0	09:18:10.276	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 76.32 ms)
0	09:18:29.448	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 76.32 ms)
0	09:18:30.588	'66036191': previous successful authorization performed from 152.32.252.153
0	09:18:31.573	'66036191': auto connecting to a better access point DC#2-1 (ping is 12.88 ms)
0	09:18:31.791	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 12.88 ms)
0	09:18:32.229	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 12.88 ms)
0	09:18:32.854	'66036191': previous successful authorization performed from 152.32.252.153
1	22:31:49.598	'66036191': ping failed
1	22:31:49.598	'66036191': datacenter connecting failed [6]
0	22:31:50.051	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 32.84 ms)
0	22:31:54.254	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 32.84 ms)
0	22:31:55.254	'66036191': previous successful authorization performed from 152.32.252.153
0	22:32:03.113	'66036191': auto connecting to a better access point DC#2-1 (ping is 10.80 ms)
0	22:32:03.332	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 10.80 ms)
0	22:32:11.426	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 10.80 ms)
0	22:32:13.426	'66036191': previous successful authorization performed from 152.32.252.153