1	04:02:13.262	'66036191': ping failed
1	04:02:13.262	'66036191': datacenter connecting failed [6]
0	04:02:32.012	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 92.50 ms)
0	04:02:54.559	'66036191': login datacenter on HeroCapitalPty-Server through DC#5 (ping: 92.50 ms)
0	04:02:54.840	'66036191': previous successful authorization performed from 152.32.252.153
0	04:02:55.309	'66036191': auto connecting to a better access point DC#2 (ping is 2.50 ms)
0	04:02:55.715	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 2.50 ms)
0	04:02:55.809	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 2.50 ms)
0	04:02:55.934	'66036191': previous successful authorization performed from 152.32.252.153
1	22:01:21.824	'66036191': ping failed
1	22:01:21.824	'66036191': datacenter connecting failed [6]
0	22:01:22.324	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 64.80 ms)
0	22:01:23.793	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 64.80 ms)
0	22:01:24.340	'66036191': previous successful authorization performed from 152.32.252.153
0	22:01:24.558	'66036191': auto connecting to a better access point DC#2 (ping is 2.71 ms)
0	22:01:24.824	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 2.71 ms)
0	22:01:25.433	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 2.71 ms)
0	22:01:25.543	'66036191': previous successful authorization performed from 152.32.252.153
0	22:56:29.634	'66036191': login datacenter on HeroCapitalPty-Server
0	22:56:30.055	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 64.25 ms)
0	22:56:32.337	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 64.25 ms)
0	22:56:32.555	'66036191': previous successful authorization performed from 152.32.252.153