1	02:32:24.004	'66036191': ping failed
1	02:32:24.004	'66036191': datacenter connecting failed [6]
0	02:32:24.348	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 2.77 ms)
0	02:32:24.661	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 2.77 ms)
0	02:32:25.145	'66036191': previous successful authorization performed from 152.32.252.153
0	02:32:25.692	'66036191': ping to current access point DC#2-1 is 2.93 ms
0	15:30:38.626	'66036191': login datacenter on HeroCapitalPty-Server
0	15:30:38.986	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 5.37 ms)
0	15:30:40.111	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 5.37 ms)
0	15:30:40.798	'66036191': previous successful authorization performed from 152.32.252.153
0	15:30:42.048	'66036191': auto connecting to a better access point DC#2-1 (ping is 5.11 ms)
0	15:30:42.236	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 5.11 ms)
0	15:30:42.751	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 5.11 ms)
0	15:30:43.220	'66036191': previous successful authorization performed from 152.32.252.153
1	19:00:32.580	'66036191': ping failed
0	19:00:32.580	'66036191': login datacenter on HeroCapitalPty-Server
0	19:00:32.799	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 56.95 ms)
0	19:00:33.002	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 56.95 ms)
0	19:00:33.612	'66036191': previous successful authorization performed from 152.32.252.153
0	19:00:40.971	'66036191': auto connecting to a better access point DC#2-1 (ping is 5.23 ms)
0	19:00:41.127	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 5.23 ms)
0	19:00:42.955	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 5.23 ms)
0	19:00:43.518	'66036191': previous successful authorization performed from 152.32.252.153