0	14:48:55.331	'66036191': login datacenter on HeroCapitalPty-Server
1	14:48:55.596	'66036191': ping failed
0	14:48:56.159	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 2.54 ms)
0	14:48:56.346	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 2.54 ms)
0	14:48:56.503	'66036191': previous successful authorization performed from 152.32.252.153
0	14:49:13.174	'66036191': auto connecting to a better access point DC#2-1 (ping is 2.64 ms)
0	14:49:13.440	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 2.64 ms)
0	14:49:13.503	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 2.64 ms)
0	14:49:13.612	'66036191': previous successful authorization performed from 152.32.252.153
1	22:00:52.138	'66036191': ping failed
1	22:00:52.138	'66036191': datacenter connecting failed [6]
0	22:00:52.450	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 2.11 ms)
0	22:00:52.575	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 2.11 ms)
0	22:00:52.700	'66036191': previous successful authorization performed from 152.32.252.153
0	22:01:17.794	'66036191': auto connecting to a better access point DC#2-1 (ping is 2.95 ms)
0	22:01:18.138	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 2.95 ms)
0	22:01:18.247	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 2.95 ms)
0	22:01:18.341	'66036191': previous successful authorization performed from 152.32.252.153