1	16:07:18.834	'66036191': ping failed
1	16:07:18.834	'66036191': datacenter connecting failed [6]
0	16:07:19.490	'66036191': login on HeroCapitalPty-Server through DC#4 (ping: 112.87 ms)
0	16:07:20.756	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 112.87 ms)
0	16:07:21.131	'66036191': previous successful authorization performed from 152.32.252.153
0	16:07:21.537	'66036191': auto connecting to a better access point DC#2 (ping is 3.32 ms)
0	16:07:24.943	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.32 ms)
0	16:07:25.021	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.32 ms)
0	16:07:25.162	'66036191': previous successful authorization performed from 152.32.252.153
1	21:44:30.903	'66036191': ping failed
1	21:44:30.903	'66036191': datacenter connecting failed [6]
0	21:44:31.559	'66036191': login on HeroCapitalPty-Server through DC#4 (ping: 187.35 ms)
0	21:44:32.809	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 187.35 ms)
0	21:44:33.184	'66036191': previous successful authorization performed from 152.32.252.153
0	21:44:33.622	'66036191': auto connecting to a better access point DC#2 (ping is 4.12 ms)
0	21:44:33.856	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 4.12 ms)
0	21:44:33.950	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 4.12 ms)
0	21:44:34.122	'66036191': previous successful authorization performed from 152.32.252.153