1	04:49:33.687	'3001658': connect failed [没有连接]
0	04:50:10.555	'3001658': login on BroadmanVickery-Live through DC HK4 (ping: n/a)
0	04:50:10.790	'3001658': login datacenter on BroadmanVickery-Live through DC HK4 (ping: n/a)
0	04:50:10.899	'3001658': previous successful authorization performed from 152.32.128.46
0	04:50:11.024	'3001658': ping to current access point DC HK4 is 1.94 ms
1	10:50:36.877	'3001658': ping failed
1	10:50:36.892	'3001658': datacenter connecting failed [6]
0	10:50:46.439	'3001658': login on BroadmanVickery-Live through DC HK2 (ping: 2.71 ms)
0	10:50:46.799	'3001658': login datacenter on BroadmanVickery-Live through DC HK2 (ping: 2.71 ms)
0	10:50:46.939	'3001658': previous successful authorization performed from 152.32.128.46
0	10:50:57.799	'3001658': auto connecting to a better access point DC HK4 (ping is 1.89 ms)
0	10:50:58.267	'3001658': login on BroadmanVickery-Live through DC HK4 (ping: 1.89 ms)
0	10:50:58.377	'3001658': login datacenter on BroadmanVickery-Live through DC HK4 (ping: 1.89 ms)
0	10:50:58.471	'3001658': previous successful authorization performed from 152.32.128.46
1	10:52:58.471	'3001658': ping failed
0	10:53:07.971	'3001658': login on BroadmanVickery-Live through DC HK3 (ping: 2.34 ms)
0	10:53:08.330	'3001658': login datacenter on BroadmanVickery-Live through DC HK3 (ping: 2.34 ms)
0	10:53:08.471	'3001658': previous successful authorization performed from 152.32.128.46
1	10:55:25.799	'3001658': datacenter connecting failed [6]
0	10:55:56.330	'3001658': login on BroadmanVickery-Live through DC HK2 (ping: 3.77 ms)
0	10:55:56.721	'3001658': login datacenter on BroadmanVickery-Live through DC HK2 (ping: 3.77 ms)
0	10:55:56.861	'3001658': previous successful authorization performed from 152.32.128.46
1	10:57:56.814	'3001658': ping failed
1	10:57:56.814	'3001658': datacenter connecting failed [6]
0	10:58:06.346	'3001658': login on BroadmanVickery-Live through DC HK3 (ping: 2.34 ms)
0	10:58:06.705	'3001658': login datacenter on BroadmanVickery-Live through DC HK3 (ping: 2.34 ms)
0	10:58:06.846	'3001658': previous successful authorization performed from 152.32.128.46
1	11:03:07.142	'3001658': ping failed
1	11:03:28.221	'3001658': connect failed [没有连接]
0	11:03:54.877	'3001658': login on BroadmanVickery-Live through DC HK2 (ping: n/a)
0	11:03:55.267	'3001658': login datacenter on BroadmanVickery-Live through DC HK2 (ping: n/a)
0	11:03:55.408	'3001658': previous successful authorization performed from 152.32.128.46
0	11:03:55.517	'3001658': ping to current access point DC HK2 is 1.93 ms
1	11:06:26.814	'3001658': datacenter connecting failed [6]
0	11:06:57.439	'3001658': login on BroadmanVickery-Live through DC HK2 (ping: 1.93 ms)
0	11:08:03.392	'3001658': login on BroadmanVickery-Live through DC HK4 (ping: 1.88 ms)
0	11:08:03.502	'3001658': login datacenter on BroadmanVickery-Live through DC HK4 (ping: 1.88 ms)
0	11:08:03.611	'3001658': previous successful authorization performed from 152.32.128.46
1	11:09:03.580	'3001658': ping failed
0	11:09:03.580	'3001658': login datacenter on BroadmanVickery-Live
0	11:09:04.080	'3001658': login on BroadmanVickery-Live through DC HK3 (ping: 2.17 ms)
0	11:09:04.471	'3001658': login datacenter on BroadmanVickery-Live through DC HK3 (ping: 2.17 ms)
0	11:09:04.611	'3001658': previous successful authorization performed from 152.32.128.46
1	11:12:04.721	'3001658': ping failed
1	11:12:04.736	'3001658': datacenter connecting failed [6]
0	11:12:05.252	'3001658': login on BroadmanVickery-Live through DC HK (ping: 4.30 ms)
0	11:12:05.658	'3001658': login datacenter on BroadmanVickery-Live through DC HK (ping: 4.30 ms)
0	11:12:05.783	'3001658': previous successful authorization performed from 152.32.128.46
1	11:17:25.908	'3001658': ping failed
1	11:17:25.924	'3001658': datacenter connecting failed [6]
1	11:17:25.971	'3001658': connect failed [没有连接]
0	11:17:31.611	'3001658': login on BroadmanVickery-Live through DC HK2 (ping: n/a)
0	11:17:32.017	'3001658': login datacenter on BroadmanVickery-Live through DC HK2 (ping: n/a)
0	11:17:32.158	'3001658': previous successful authorization performed from 152.32.128.46
0	11:17:32.314	'3001658': ping to current access point DC HK2 is 1.82 ms
1	18:29:53.309	'3001658': datacenter connecting failed [6]
0	18:29:53.778	'3001658': login on BroadmanVickery-Live through DC HK4 (ping: 1.80 ms)
0	18:29:53.903	'3001658': login datacenter on BroadmanVickery-Live through DC HK4 (ping: 1.80 ms)
0	18:29:53.997	'3001658': previous successful authorization performed from 152.32.128.46
0	18:29:54.231	'3001658': auto connecting to a better access point DC HK2 (ping is 2.45 ms)
0	18:29:54.777	'3001658': login on BroadmanVickery-Live through DC HK2 (ping: 2.45 ms)
0	18:29:55.121	'3001658': login datacenter on BroadmanVickery-Live through DC HK2 (ping: 2.45 ms)
0	18:29:55.324	'3001658': previous successful authorization performed from 152.32.128.46
1	18:33:55.225	'3001658': ping failed
1	18:33:55.256	'3001658': datacenter connecting failed [6]
0	18:34:19.819	'3001658': login on BroadmanVickery-Live through DC HK4 (ping: 2.07 ms)
0	18:34:19.929	'3001658': login datacenter on BroadmanVickery-Live through DC HK4 (ping: 2.07 ms)
0	18:34:20.038	'3001658': previous successful authorization performed from 152.32.128.46
1	18:39:59.909	'3001658': datacenter connecting failed [6]
0	18:40:00.487	'3001658': login on BroadmanVickery-Live through DC HK (ping: 4.22 ms)
0	18:40:00.831	'3001658': login datacenter on BroadmanVickery-Live through DC HK (ping: 4.22 ms)
0	18:40:00.987	'3001658': previous successful authorization performed from 152.32.128.46