1	06:01:48.555	'66036191': datacenter connecting failed [6]
0	06:01:48.790	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 11.30 ms)
0	06:01:51.446	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 11.30 ms)
0	06:01:52.290	'66036191': auto connecting to a better access point DC#2 (ping is 2.85 ms)
0	06:01:52.415	'66036191': login datacenter on HeroCapitalPty-Server
0	06:01:57.758	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 4.20 ms)
0	06:02:02.196	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 4.20 ms)
0	06:02:02.680	'66036191': previous successful authorization performed from 152.32.252.153
1	09:01:50.663	'66036191': ping failed
1	09:01:50.663	'66036191': datacenter connecting failed [6]
0	09:01:51.053	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 75.85 ms)
0	09:01:55.569	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 75.85 ms)
0	09:01:56.147	'66036191': previous successful authorization performed from 152.32.252.153
0	09:01:56.350	'66036191': auto connecting to a better access point DC#2-1 (ping is 2.90 ms)
0	09:01:56.538	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 2.90 ms)
0	09:01:58.538	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 2.90 ms)
0	09:01:59.038	'66036191': previous successful authorization performed from 152.32.252.153
1	10:01:21.314	'66036191': ping failed
1	10:01:21.330	'66036191': datacenter connecting failed [6]
0	10:01:21.564	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.30 ms)
0	10:01:21.689	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.30 ms)
0	10:01:22.189	'66036191': previous successful authorization performed from 152.32.252.153