1	14:16:29.255	'66036191': ping failed
1	14:16:29.317	'66036191': ping failed
1	14:16:29.348	'66036191': datacenter connecting failed [6]
0	14:16:30.958	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 2.28 ms)
0	14:16:31.489	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 2.28 ms)
0	14:16:32.098	'66036191': previous successful authorization performed from 152.32.252.153
0	14:16:33.255	'66036191': auto connecting to a better access point DC#2 (ping is 2.74 ms)
0	14:16:33.442	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 2.74 ms)
0	14:16:33.755	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 2.74 ms)
0	14:16:34.239	'66036191': previous successful authorization performed from 152.32.252.153
1	14:26:25.536	'66036191': ping failed
1	14:26:25.567	'66036191': datacenter connecting failed [6]
0	14:26:26.848	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 2.60 ms)
0	14:26:27.708	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 2.60 ms)
0	14:26:28.177	'66036191': previous successful authorization performed from 152.32.252.153
1	21:49:07.910	'66036191': ping failed
0	21:49:08.644	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 76.08 ms)
0	21:49:10.207	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 76.08 ms)
0	21:49:11.035	'66036191': auto connecting to a better access point DC#2 (ping is 2.21 ms)
0	21:49:11.629	'66036191': login datacenter on HeroCapitalPty-Server
0	21:49:18.035	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 2.24 ms)
0	21:49:18.707	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 2.24 ms)
0	21:49:19.160	'66036191': previous successful authorization performed from 152.32.252.153