0	20:53:28.205	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.96 ms)
0	20:53:28.284	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.96 ms)
0	20:53:28.409	'66036191': previous successful authorization performed from 152.32.252.153
0	20:53:29.205	'66036191': ping to current access point DC#2 is 3.64 ms
1	20:56:28.674	'66036191': datacenter connecting failed [6]
0	20:56:28.987	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.64 ms)
0	20:56:29.034	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.64 ms)
0	20:56:29.174	'66036191': previous successful authorization performed from 152.32.252.153
1	21:08:09.830	'66036191': ping failed
0	21:08:10.221	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.64 ms)
0	21:08:10.315	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.64 ms)
0	21:08:10.455	'66036191': previous successful authorization performed from 152.32.252.153
1	21:10:10.424	'66036191': ping failed
1	21:10:10.424	'66036191': datacenter connecting failed [6]
0	21:10:10.987	'66036191': login on HeroCapitalPty-Server through DC#4 (ping: 89.74 ms)
0	21:10:11.705	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 89.74 ms)
0	21:10:12.018	'66036191': previous successful authorization performed from 152.32.252.153
1	22:33:05.346	'66036191': datacenter connecting failed [6]
0	22:33:05.799	'66036191': login on HeroCapitalPty-Server through DC#4 (ping: 89.74 ms)
0	22:33:06.471	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 89.74 ms)
0	22:33:06.737	'66036191': previous successful authorization performed from 152.32.252.153
0	22:33:07.424	'66036191': auto connecting to a better access point DC#2 (ping is 4.42 ms)
0	22:33:07.784	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 4.42 ms)
0	22:33:07.877	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 4.42 ms)
0	22:33:08.002	'66036191': previous successful authorization performed from 152.32.252.153
1	22:40:28.221	'66036191': ping failed
1	22:40:28.221	'66036191': datacenter connecting failed [6]
0	22:40:28.893	'66036191': login on HeroCapitalPty-Server through DC#4 (ping: 166.32 ms)
0	22:40:30.096	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 166.32 ms)
0	22:40:30.455	'66036191': previous successful authorization performed from 152.32.252.153
1	22:49:54.955	'66036191': datacenter connecting failed [6]
0	22:49:55.877	'66036191': login on HeroCapitalPty-Server through DC#4 (ping: 166.32 ms)
0	22:49:57.065	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 166.32 ms)
0	22:49:57.643	'66036191': previous successful authorization performed from 152.32.252.153
1	22:50:57.784	'66036191': ping failed
0	22:50:58.705	'66036191': login on HeroCapitalPty-Server through DC#4 (ping: 166.32 ms)
0	22:50:59.455	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 166.32 ms)
0	22:50:59.737	'66036191': previous successful authorization performed from 152.32.252.153
1	22:59:00.190	'66036191': ping failed
1	22:59:00.455	'66036191': connect failed [ûÓÐÁ¬½Ó]
0	22:59:16.034	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	22:59:16.659	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	22:59:16.784	'66036191': previous successful authorization performed from 152.32.252.153
0	22:59:20.690	'66036191': ping to current access point DC#2 is 2.93 ms