1	15:25:59.046	'66036191': ping failed
1	15:25:59.046	'66036191': datacenter connecting failed [6]
0	15:25:59.468	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 41.06 ms)
0	15:26:03.874	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 41.06 ms)
0	15:26:05.296	'66036191': ping to current access point DC#2 is 17.51 ms
0	15:26:05.530	'66036191': previous successful authorization performed from 152.32.252.153
1	17:30:30.134	'66036191': datacenter connecting failed [6]
0	17:30:30.446	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 18.83 ms)
0	17:31:36.509	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 75.38 ms)
0	17:32:40.477	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 75.38 ms)
0	17:33:02.915	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 75.38 ms)
0	17:33:06.462	'66036191': previous successful authorization performed from 152.32.252.153
0	17:33:10.743	'66036191': auto connecting to a better access point DC#2 (ping is 13.56 ms)
0	17:33:10.946	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 13.56 ms)
0	17:33:14.946	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 13.56 ms)
0	17:33:15.571	'66036191': previous successful authorization performed from 152.32.252.153