1	12:13:26.657	'66036191': ping failed
1	12:13:26.657	'66036191': datacenter connecting failed [6]
0	12:13:27.172	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 75.51 ms)
0	12:13:28.079	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 75.51 ms)
0	12:13:28.297	'66036191': previous successful authorization performed from 152.32.252.153
0	12:13:36.907	'66036191': auto connecting to a better access point DC#2 (ping is 2.93 ms)
0	12:13:37.282	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 2.93 ms)
0	12:13:37.391	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 2.93 ms)
0	12:13:37.532	'66036191': previous successful authorization performed from 152.32.252.153
1	15:23:06.445	'66036191': ping failed
0	15:23:06.445	'66036191': login datacenter on HeroCapitalPty-Server
0	15:23:06.913	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 69.31 ms)
0	15:23:10.476	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 69.31 ms)
0	15:23:10.726	'66036191': previous successful authorization performed from 152.32.252.153
0	15:23:34.679	'66036191': auto connecting to a better access point DC#2 (ping is 4.33 ms)
0	15:23:34.898	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 4.33 ms)
0	15:23:34.960	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 4.33 ms)
0	15:23:35.101	'66036191': previous successful authorization performed from 152.32.252.153