1	15:05:59.620	'66036191': ping failed
1	15:05:59.698	'66036191': datacenter connecting failed [6]
0	15:06:00.479	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 12.39 ms)
0	15:06:00.776	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 12.39 ms)
0	15:06:01.729	'66036191': previous successful authorization performed from 152.32.252.153
0	15:06:01.761	'66036191': auto connecting to a better access point DC#2 (ping is 3.49 ms)
0	15:06:02.011	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.49 ms)
0	15:06:02.229	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.49 ms)
0	15:06:02.667	'66036191': previous successful authorization performed from 152.32.252.153
1	20:14:30.384	'66036191': ping failed
0	20:14:31.931	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 3.11 ms)
0	20:14:32.290	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 3.11 ms)
0	20:14:33.181	'66036191': ping to current access point DC#2-1 is 2.07 ms
0	20:14:33.274	'66036191': previous successful authorization performed from 152.32.252.153
1	20:23:10.681	'66036191': ping failed
0	20:23:11.509	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.25 ms)
0	20:23:11.681	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.25 ms)
0	20:23:12.118	'66036191': previous successful authorization performed from 152.32.252.153
1	20:25:03.837	'66036191': ping failed
1	20:25:03.931	'66036191': datacenter connecting failed [6]
0	20:25:07.415	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 74.64 ms)
0	20:25:08.056	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 74.64 ms)
0	20:25:08.665	'66036191': previous successful authorization performed from 152.32.252.153