1	21:30:20.909	'66036191': ping failed
0	21:30:20.924	'66036191': login datacenter on HeroCapitalPty-Server
0	21:30:21.784	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 74.53 ms)
0	21:30:37.502	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 74.53 ms)
0	21:30:39.705	'66036191': auto connecting to a better access point DC#2 (ping is 4.50 ms)
0	21:30:48.643	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 4.50 ms)
0	21:31:54.252	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 4.54 ms)
0	21:31:55.487	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 4.54 ms)
0	21:31:56.002	'66036191': previous successful authorization performed from 152.32.252.153
1	21:38:35.846	'66036191': ping failed
1	21:38:35.846	'66036191': datacenter connecting failed [2]
0	21:38:37.612	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 73.97 ms)
0	21:38:50.768	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 73.97 ms)
0	21:38:51.909	'66036191': previous successful authorization performed from 152.32.252.153
1	23:14:19.237	'66036191': ping failed
1	23:14:19.237	'66036191': datacenter connecting failed [6]
0	23:14:23.018	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 73.97 ms)
0	23:14:25.940	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 73.97 ms)
0	23:14:27.784	'66036191': previous successful authorization performed from 152.32.252.153
0	23:14:31.862	'66036191': auto connecting to a better access point DC#2-1 (ping is 2.29 ms)
0	23:14:32.252	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 2.29 ms)
0	23:14:33.237	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 2.29 ms)
0	23:14:33.737	'66036191': previous successful authorization performed from 152.32.252.153