1	20:15:31.870	'66036191': ping failed
1	20:15:31.870	'66036191': datacenter connecting failed [6]
0	20:15:32.401	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 65.53 ms)
0	20:15:33.386	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 65.53 ms)
0	20:15:33.667	'66036191': previous successful authorization performed from 152.32.252.153
0	20:15:34.151	'66036191': auto connecting to a better access point DC#2 (ping is 3.42 ms)
0	20:15:34.558	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.42 ms)
0	20:15:34.651	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.42 ms)
0	20:15:34.776	'66036191': previous successful authorization performed from 152.32.252.153
0	22:04:32.601	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.42 ms)
0	22:04:33.055	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.42 ms)
0	22:04:33.180	'66036191': previous successful authorization performed from 152.32.252.153
0	22:04:33.914	'66036191': ping to current access point DC#2 is 3.49 ms
0	22:05:32.570	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.49 ms)
0	22:05:32.789	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.49 ms)
0	22:05:39.383	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.49 ms)
0	22:05:39.508	'66036191': previous successful authorization performed from 152.32.252.153
1	22:06:53.336	'66036191': datacenter connecting failed [6]
0	22:06:54.258	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.49 ms)
0	22:06:54.555	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.49 ms)
0	22:06:54.680	'66036191': previous successful authorization performed from 152.32.252.153
1	22:07:33.039	'66036191': datacenter connecting failed [6]
0	22:07:33.492	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.49 ms)
1	22:08:04.461	'66036191': datacenter connecting failed [6]
0	22:08:10.211	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.49 ms)
0	22:09:10.555	'66036191': login datacenter on HeroCapitalPty-Server
0	22:09:11.305	'66036191': auto connecting to a better access point DC#2 (ping is 3.23 ms)
0	22:09:15.883	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.23 ms)
0	22:09:29.070	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.23 ms)
0	22:09:29.180	'66036191': previous successful authorization performed from 152.32.252.153
1	22:21:56.535	'66036191': datacenter connecting failed [6]
0	22:21:57.441	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 67.34 ms)
0	22:21:58.098	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 67.34 ms)
0	22:21:58.316	'66036191': previous successful authorization performed from 152.32.252.153
1	22:22:34.894	'66036191': datacenter connecting failed [6]
0	22:22:35.254	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 67.34 ms)
0	22:22:35.738	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 67.34 ms)
0	22:22:35.973	'66036191': previous successful authorization performed from 152.32.252.153