1	20:30:23.081	'66036191': ping failed
0	20:30:23.081	'66036191': login datacenter on HeroCapitalPty-Server
0	20:30:23.581	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 65.04 ms)
0	20:30:24.097	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 65.04 ms)
0	20:30:24.300	'66036191': previous successful authorization performed from 152.32.252.153
0	20:30:24.784	'66036191': auto connecting to a better access point DC#2 (ping is 3.44 ms)
0	20:30:25.253	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.44 ms)
0	20:30:25.378	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.44 ms)
0	20:30:25.503	'66036191': previous successful authorization performed from 152.32.252.153
1	22:55:32.230	'66036191': ping failed
1	22:55:32.230	'66036191': datacenter connecting failed [6]
0	22:55:32.792	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 65.04 ms)
0	22:55:33.339	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 65.04 ms)
0	22:55:33.558	'66036191': previous successful authorization performed from 152.32.252.153
0	22:55:37.386	'66036191': auto connecting to a better access point DC#2 (ping is 3.23 ms)
0	22:55:37.902	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.23 ms)
0	22:55:38.058	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.23 ms)
0	22:55:38.480	'66036191': previous successful authorization performed from 152.32.252.153