1	17:28:17.781	'66036191': datacenter connecting failed [2]
0	17:28:21.156	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 64.30 ms)
0	17:28:22.937	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 64.30 ms)
0	17:28:23.172	'66036191': previous successful authorization performed from 152.32.252.153
0	17:28:33.641	'66036191': auto connecting to a better access point DC#2 (ping is 4.10 ms)
0	17:28:33.812	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 4.10 ms)
0	17:28:52.359	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 4.10 ms)
0	17:28:52.484	'66036191': previous successful authorization performed from 152.32.252.153
1	17:30:47.500	'66036191': ping failed
1	17:30:47.500	'66036191': datacenter connecting failed [6]
0	17:30:48.766	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 65.58 ms)
0	17:31:54.937	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 65.58 ms)
0	17:31:56.531	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 65.58 ms)
0	17:31:56.766	'66036191': previous successful authorization performed from 152.32.252.153
1	17:40:09.484	'66036191': datacenter connecting failed [6]
0	17:40:09.891	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 93.29 ms)
1	17:40:51.484	'66036191': datacenter connecting failed [6]
0	17:40:58.297	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 93.29 ms)
0	17:41:08.437	'66036191': login datacenter on HeroCapitalPty-Server through DC#5 (ping: 93.29 ms)
0	17:41:08.750	'66036191': previous successful authorization performed from 152.32.252.153
1	17:44:52.784	'66036191': datacenter connecting failed [6]
1	17:44:52.847	'66036191': connect failed [没有连接]
0	17:44:58.050	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	17:44:58.144	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	17:44:58.284	'66036191': previous successful authorization performed from 152.32.252.153
0	17:44:59.987	'66036191': ping to current access point DC#2 is 4.07 ms
1	17:54:46.144	'66036191': ping failed
1	17:54:46.144	'66036191': datacenter connecting failed [6]
0	17:54:58.925	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 64.90 ms)
0	17:55:01.894	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 64.90 ms)
0	17:55:02.097	'66036191': previous successful authorization performed from 152.32.252.153
1	18:05:35.784	'66036191': datacenter connecting failed [6]
0	18:06:00.581	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 90.13 ms)
1	18:07:05.815	'66036191': connect failed [没有连接]
0	18:07:14.034	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	18:07:14.659	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	18:07:15.112	'66036191': previous successful authorization performed from 152.32.252.153
0	18:07:19.331	'66036191': ping to current access point DC#2 is 3.59 ms
1	18:10:15.784	'66036191': datacenter connecting failed [6]
0	18:10:16.222	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 63.92 ms)
0	18:10:17.612	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 63.92 ms)
0	18:10:17.815	'66036191': previous successful authorization performed from 152.32.252.153
1	18:18:39.645	'66036191': ping failed
1	18:18:39.660	'66036191': datacenter connecting failed [6]
0	18:18:40.098	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 88.83 ms)
0	18:18:51.410	'66036191': login datacenter on HeroCapitalPty-Server through DC#5 (ping: 88.83 ms)
0	18:18:52.020	'66036191': previous successful authorization performed from 152.32.252.153
1	18:19:51.504	'66036191': ping failed
1	18:19:51.535	'66036191': datacenter connecting failed [6]
1	18:19:51.660	'66036191': connect failed [没有连接]
0	18:19:57.004	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	18:19:57.082	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	18:19:57.191	'66036191': previous successful authorization performed from 152.32.252.153
0	18:19:57.895	'66036191': ping to current access point DC#2 is 3.56 ms
1	18:21:17.145	'66036191': ping failed
1	18:21:17.145	'66036191': datacenter connecting failed [6]
0	18:21:17.691	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 65.33 ms)
0	18:21:18.957	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 65.33 ms)
0	18:21:19.176	'66036191': previous successful authorization performed from 152.32.252.153
1	21:03:14.719	'66036191': ping failed
1	21:03:14.734	'66036191': datacenter connecting failed [6]
0	21:03:15.859	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 85.92 ms)
0	21:03:19.734	'66036191': login datacenter on HeroCapitalPty-Server through DC#5 (ping: 85.92 ms)
0	21:03:21.281	'66036191': previous successful authorization performed from 152.32.252.153
0	21:03:24.641	'66036191': auto connecting to a better access point DC#2 (ping is 3.39 ms)
0	21:03:24.922	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.39 ms)
0	21:03:25.000	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.39 ms)
0	21:03:25.109	'66036191': previous successful authorization performed from 152.32.252.153
1	21:04:05.031	'66036191': ping failed
0	21:04:05.031	'66036191': login datacenter on HeroCapitalPty-Server
0	21:04:06.250	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 85.45 ms)
0	21:04:11.281	'66036191': login datacenter on HeroCapitalPty-Server through DC#5 (ping: 85.45 ms)
0	21:04:11.844	'66036191': previous successful authorization performed from 152.32.252.153
0	22:13:59.330	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 85.45 ms)
0	22:15:09.221	'66036191': login datacenter on HeroCapitalPty-Server
0	22:15:14.799	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 67.47 ms)
0	22:15:16.736	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 67.47 ms)
0	22:15:17.861	'66036191': previous successful authorization performed from 152.32.252.153
0	22:15:26.768	'66036191': auto connecting to a better access point DC#2 (ping is 4.66 ms)
0	22:15:30.049	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 4.66 ms)
0	22:15:33.783	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 4.66 ms)
0	22:15:34.799	'66036191': previous successful authorization performed from 152.32.252.153
0	22:19:18.674	'66036191': login datacenter on HeroCapitalPty-Server
0	22:19:19.080	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 62.42 ms)
0	22:19:19.533	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 62.42 ms)
0	22:19:20.471	'66036191': previous successful authorization performed from 152.32.252.153
1	22:20:00.018	'66036191': ping failed
1	22:20:00.018	'66036191': datacenter connecting failed [6]
0	22:20:00.830	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 88.07 ms)
0	22:20:12.221	'66036191': login datacenter on HeroCapitalPty-Server through DC#5 (ping: 88.07 ms)
0	22:20:13.533	'66036191': previous successful authorization performed from 152.32.252.153
1	22:23:44.783	'66036191': datacenter connecting failed [6]
1	22:23:44.846	'66036191': connect failed [没有连接]
0	22:23:50.346	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	22:23:50.955	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	22:23:51.080	'66036191': previous successful authorization performed from 152.32.252.153
0	22:23:51.846	'66036191': ping to current access point DC#2 is 2.96 ms