1	07:58:43.889	'66036191': ping failed
1	07:58:43.889	'66036191': datacenter connecting failed [6]
0	07:58:44.467	'66036191': login on HeroCapitalPty-Server through DC#4 (ping: 92.17 ms)
0	07:58:45.124	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 92.17 ms)
0	07:58:45.389	'66036191': previous successful authorization performed from 152.32.252.153
0	07:58:45.811	'66036191': auto connecting to a better access point DC#2 (ping is 2.39 ms)
0	07:58:46.249	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 2.39 ms)
0	07:58:46.358	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 2.39 ms)
0	07:58:46.483	'66036191': previous successful authorization performed from 152.32.252.153
1	19:05:39.504	'66036191': ping failed
1	19:05:39.504	'66036191': datacenter connecting failed [6]
0	19:05:39.973	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 65.97 ms)
0	19:05:40.598	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 65.97 ms)
0	19:05:40.848	'66036191': previous successful authorization performed from 152.32.252.153
0	19:05:41.942	'66036191': auto connecting to a better access point DC#2 (ping is 2.79 ms)
0	19:05:42.239	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 2.79 ms)
0	19:05:42.426	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 2.79 ms)
0	19:05:42.567	'66036191': previous successful authorization performed from 152.32.252.153