0	10:57:38.061	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 3.23 ms)
0	10:57:38.374	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 3.23 ms)
0	10:57:38.936	'66036191': previous successful authorization performed from 152.32.252.153
0	10:57:39.796	'66036191': ping to current access point DC#2-1 is 2.84 ms
1	17:18:09.255	'66036191': ping failed
0	17:18:12.817	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 47.87 ms)
0	17:18:12.895	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 47.87 ms)
0	17:18:13.645	'66036191': previous successful authorization performed from 152.32.252.153
0	17:18:24.114	'66036191': auto connecting to a better access point DC#2-1 (ping is 2.33 ms)
0	17:18:24.442	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 2.33 ms)
0	17:18:25.114	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 2.33 ms)
0	17:18:25.661	'66036191': previous successful authorization performed from 152.32.252.153
1	22:57:56.696	'66036191': ping failed
0	22:57:56.696	'66036191': login datacenter on HeroCapitalPty-Server
0	22:57:57.493	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 13.71 ms)
0	22:57:59.227	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 13.71 ms)
0	22:58:00.477	'66036191': previous successful authorization performed from 152.32.252.153
0	22:58:02.227	'66036191': auto connecting to a better access point DC#2-1 (ping is 16.52 ms)
0	22:58:02.477	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 16.52 ms)
0	22:58:02.805	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 16.52 ms)
0	22:58:03.274	'66036191': previous successful authorization performed from 152.32.252.153