0	22:01:07.699	'66036191': login datacenter on HeroCapitalPty-Server
0	22:01:08.386	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 75.78 ms)
0	22:01:09.433	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 75.78 ms)
0	22:01:09.964	'66036191': previous successful authorization performed from 152.32.252.153
0	22:01:11.418	'66036191': auto connecting to a better access point DC#2 (ping is 2.20 ms)
0	22:01:20.839	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 2.20 ms)
0	22:01:22.808	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 2.20 ms)
0	22:01:23.246	'66036191': previous successful authorization performed from 152.32.252.153
1	22:08:27.277	'66036191': datacenter connecting failed [6]
0	22:08:28.074	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 69.16 ms)
0	22:08:30.730	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 69.16 ms)
0	22:08:30.964	'66036191': previous successful authorization performed from 152.32.252.153
1	22:20:04.081	'66036191': datacenter connecting failed [6]
0	22:20:06.893	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 93.34 ms)
0	22:20:26.518	'66036191': login datacenter on HeroCapitalPty-Server through DC#5 (ping: 93.34 ms)
0	22:20:38.346	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 93.34 ms)
0	22:20:39.940	'66036191': login datacenter on HeroCapitalPty-Server through DC#5 (ping: 93.34 ms)
0	22:20:40.268	'66036191': previous successful authorization performed from 152.32.252.153
0	22:30:35.878	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 93.34 ms)
0	22:30:37.315	'66036191': login datacenter on HeroCapitalPty-Server through DC#5 (ping: 93.34 ms)
0	22:30:37.643	'66036191': previous successful authorization performed from 152.32.252.153