1	03:05:18.873	'66036191': connect failed [没有连接]
0	03:09:02.467	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	03:10:07.936	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: n/a)
0	03:10:09.311	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: n/a)
0	03:10:09.545	'66036191': previous successful authorization performed from 152.32.252.153
0	03:10:10.076	'66036191': auto connecting to a better access point DC#2 (ping is 4.73 ms)
0	03:10:10.233	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 4.73 ms)
0	03:10:32.764	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 4.73 ms)
0	03:10:32.904	'66036191': previous successful authorization performed from 152.32.252.153
1	05:01:22.373	'66036191': connect failed [没有连接]
0	05:02:03.561	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	05:02:03.764	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	05:02:03.889	'66036191': previous successful authorization performed from 152.32.252.153
0	05:02:04.295	'66036191': ping to current access point DC#2 is 2.79 ms
1	09:36:56.904	'66036191': ping failed
1	09:36:56.904	'66036191': datacenter connecting failed [6]
0	09:36:57.342	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 65.81 ms)
0	09:36:57.889	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 65.81 ms)
0	09:36:58.154	'66036191': previous successful authorization performed from 152.32.252.153
0	09:36:58.608	'66036191': auto connecting to a better access point DC#2 (ping is 2.81 ms)
0	09:36:58.904	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 2.81 ms)
0	09:36:59.061	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 2.81 ms)
0	09:36:59.858	'66036191': previous successful authorization performed from 152.32.252.153
1	20:34:50.404	'66036191': ping failed
1	20:34:50.404	'66036191': datacenter connecting failed [6]
0	20:34:50.764	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 66.22 ms)
0	20:34:54.061	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 66.22 ms)
0	20:34:55.201	'66036191': previous successful authorization performed from 152.32.252.153
0	20:35:10.889	'66036191': auto connecting to a better access point DC#2 (ping is 4.72 ms)
0	20:35:11.123	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 4.72 ms)
0	20:35:11.373	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 4.72 ms)
0	20:35:11.514	'66036191': previous successful authorization performed from 152.32.252.153
1	20:38:32.076	'66036191': ping failed
0	20:38:32.076	'66036191': login datacenter on HeroCapitalPty-Server
1	20:38:53.342	'66036191': connect failed [没有连接]
0	20:38:59.108	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 68.88 ms)
0	20:39:03.404	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 68.88 ms)
0	20:39:03.639	'66036191': previous successful authorization performed from 152.32.252.153
1	20:40:03.498	'66036191': ping failed
1	20:40:03.514	'66036191': datacenter connecting failed [6]
1	20:40:03.592	'66036191': connect failed [没有连接]
0	20:40:08.967	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	20:40:09.061	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	20:40:09.201	'66036191': previous successful authorization performed from 152.32.252.153
0	20:40:38.108	'66036191': ping to current access point DC#2 is 3.61 ms