1	03:01:56.392	'66036191': ping failed
0	03:01:56.392	'66036191': login datacenter on HeroCapitalPty-Server
0	03:01:56.720	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 74.63 ms)
0	03:02:00.189	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 74.63 ms)
0	03:02:01.267	'66036191': auto connecting to a better access point DC#2-1 (ping is 9.52 ms)
0	03:02:06.564	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 9.52 ms)
0	03:02:09.392	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 9.52 ms)
0	03:02:09.861	'66036191': previous successful authorization performed from 152.32.252.153
1	03:02:37.955	'66036191': datacenter connecting failed [6]
0	03:02:38.345	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 14.35 ms)
0	03:03:44.580	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 75.18 ms)
0	03:04:50.564	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 91.96 ms)
0	03:04:53.111	'66036191': login datacenter on HeroCapitalPty-Server through DC#5 (ping: 91.96 ms)
0	03:04:54.002	'66036191': previous successful authorization performed from 152.32.252.153
1	03:44:06.159	'66036191': datacenter connecting failed [6]
1	03:44:06.221	'66036191': connect failed [ûÓÐÁ¬½Ó]
0	03:44:11.612	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	03:44:13.112	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	03:44:13.815	'66036191': previous successful authorization performed from 152.32.252.153
0	03:44:20.018	'66036191': ping to current access point DC#2 is 115.19 ms