1	14:13:55.914	'66036191': ping failed
1	14:13:56.023	'66036191': datacenter connecting failed [6]
0	14:13:56.554	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 8.16 ms)
0	14:13:56.632	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 8.16 ms)
0	14:13:57.445	'66036191': auto connecting to a better access point DC#2-1 (ping is 2.48 ms)
0	14:14:02.945	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 2.48 ms)
0	14:14:03.320	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 2.48 ms)
0	14:14:03.804	'66036191': previous successful authorization performed from 152.32.252.153
1	21:37:28.796	'66036191': ping failed
1	21:37:28.811	'66036191': datacenter connecting failed [6]
0	21:37:31.264	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 2.27 ms)
0	21:37:31.358	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 2.27 ms)
0	21:37:31.983	'66036191': previous successful authorization performed from 152.32.252.153
0	21:37:35.811	'66036191': ping to current access point DC#2 is 2.49 ms
1	21:40:56.827	'66036191': ping failed
1	21:40:56.921	'66036191': ping failed
1	21:40:56.936	'66036191': datacenter connecting failed [6]
0	21:40:58.171	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 3.30 ms)
0	21:40:58.311	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 3.30 ms)
0	21:40:58.749	'66036191': previous successful authorization performed from 152.32.252.153
0	21:55:08.921	'66036191': login datacenter on HeroCapitalPty-Server
1	21:55:09.030	'66036191': ping failed
0	21:55:09.780	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 86.17 ms)
0	21:55:11.155	'66036191': login datacenter on HeroCapitalPty-Server through DC#5 (ping: 86.17 ms)
0	21:55:11.827	'66036191': previous successful authorization performed from 152.32.252.153