0	19:47:11.153	'66036191': login datacenter on HeroCapitalPty-Server
0	19:47:11.887	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 71.27 ms)
0	19:47:15.778	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 71.27 ms)
0	19:47:15.997	'66036191': previous successful authorization performed from 152.32.252.153
0	19:47:31.184	'66036191': auto connecting to a better access point DC#2 (ping is 4.99 ms)
0	19:47:31.856	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 4.99 ms)
0	19:47:32.590	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 4.99 ms)
0	19:47:32.715	'66036191': previous successful authorization performed from 152.32.252.153
1	19:47:52.606	'66036191': ping failed
1	19:47:52.606	'66036191': datacenter connecting failed [6]
0	19:47:53.059	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 74.24 ms)
0	19:47:54.465	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 74.24 ms)
0	19:47:55.950	'66036191': previous successful authorization performed from 152.32.252.153
1	23:57:39.125	'66036191': ping failed
1	23:57:39.125	'66036191': datacenter connecting failed [6]
0	23:57:39.719	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 87.49 ms)
0	23:57:40.454	'66036191': login datacenter on HeroCapitalPty-Server through DC#5 (ping: 87.49 ms)
0	23:57:40.797	'66036191': previous successful authorization performed from 152.32.252.153
0	23:57:41.188	'66036191': auto connecting to a better access point DC#2 (ping is 3.38 ms)
0	23:57:41.563	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.38 ms)
0	23:57:42.032	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.38 ms)
0	23:57:42.172	'66036191': previous successful authorization performed from 152.32.252.153