1	05:44:06.923	'3001658': ping failed
0	05:44:07.188	'3001658': login on BroadmanVictory-Live through DC HK (ping: 4.97 ms)
0	05:44:07.626	'3001658': login datacenter on BroadmanVictory-Live through DC HK (ping: 4.97 ms)
0	05:44:07.704	'3001658': auto connecting to a better access point DC HK2 (ping is 1.97 ms)
0	05:44:13.172	'3001658': login on BroadmanVictory-Live through DC HK2 (ping: 1.97 ms)
0	05:44:13.500	'3001658': login datacenter on BroadmanVictory-Live through DC HK2 (ping: 1.97 ms)
0	05:44:13.625	'3001658': previous successful authorization performed from 152.32.128.46
1	05:51:24.565	'3001658': datacenter connecting failed [6]
0	05:51:24.878	'3001658': login on BroadmanVictory-Live through DC HK2 (ping: 1.97 ms)
0	05:51:25.253	'3001658': login datacenter on BroadmanVictory-Live through DC HK2 (ping: 1.97 ms)
0	05:51:25.393	'3001658': previous successful authorization performed from 152.32.128.46
1	05:52:59.899	'3001658': datacenter connecting failed [6]
0	05:53:00.243	'3001658': login on BroadmanVictory-Live through DC HK2 (ping: 1.97 ms)
0	05:53:00.602	'3001658': login datacenter on BroadmanVictory-Live through DC HK2 (ping: 1.97 ms)
0	05:53:00.743	'3001658': previous successful authorization performed from 152.32.128.46
0	05:54:16.282	'3001658': login on BroadmanVictory-Live through DC HK2 (ping: 1.97 ms)
0	05:54:16.657	'3001658': login datacenter on BroadmanVictory-Live through DC HK2 (ping: 1.97 ms)
0	05:54:16.798	'3001658': previous successful authorization performed from 152.32.128.46
1	06:58:39.848	'3001658': ping failed
1	06:58:39.848	'3001658': datacenter connecting failed [6]
0	06:58:43.223	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 1.87 ms)
0	06:58:43.582	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 1.87 ms)
0	06:58:43.723	'3001658': previous successful authorization performed from 152.32.128.46
0	06:58:43.863	'3001658': ping to current access point DC HK3 is 1.89 ms
0	07:51:55.137	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 1.89 ms)
0	07:51:55.544	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 1.89 ms)
0	07:51:55.653	'3001658': previous successful authorization performed from 152.32.128.46
1	08:37:24.204	'3001658': ping failed
1	08:37:24.220	'3001658': datacenter connecting failed [6]
0	08:37:24.564	'3001658': login on BroadmanVictory-Live through DC HK2 (ping: 2.01 ms)
0	08:37:24.876	'3001658': login datacenter on BroadmanVictory-Live through DC HK2 (ping: 2.01 ms)
0	08:37:25.017	'3001658': previous successful authorization performed from 152.32.128.46
0	08:37:25.126	'3001658': auto connecting to a better access point DC HK3 (ping is 1.90 ms)
0	08:37:25.470	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 1.90 ms)
0	08:37:25.860	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 1.90 ms)
0	08:37:25.986	'3001658': previous successful authorization performed from 152.32.128.46
1	08:38:06.097	'3001658': ping failed
0	08:38:06.488	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 1.90 ms)
0	08:38:06.800	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 1.90 ms)
0	08:38:06.941	'3001658': previous successful authorization performed from 152.32.128.46
0	09:12:01.603	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 1.90 ms)
0	09:12:01.931	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 1.90 ms)
0	09:12:02.072	'3001658': previous successful authorization performed from 152.32.128.46
0	09:32:53.189	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 1.90 ms)
0	09:32:53.502	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 1.90 ms)
0	09:32:53.642	'3001658': previous successful authorization performed from 152.32.128.46
0	11:02:04.409	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 1.90 ms)
0	11:02:04.737	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 1.90 ms)
0	11:02:04.878	'3001658': previous successful authorization performed from 152.32.128.46
0	11:02:04.972	'3001658': ping to current access point DC HK3 is 1.89 ms
0	11:03:56.597	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 1.89 ms)
0	11:03:56.972	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 1.89 ms)
0	11:03:57.113	'3001658': previous successful authorization performed from 152.32.128.46
1	11:57:40.517	'3001658': ping failed
0	11:57:40.548	'3001658': login datacenter on BroadmanVictory-Live
1	11:57:40.658	'3001658': ping failed
0	11:57:41.158	'3001658': login on BroadmanVictory-Live through DC HK2 (ping: 2.04 ms)
0	11:57:41.533	'3001658': login datacenter on BroadmanVictory-Live through DC HK2 (ping: 2.04 ms)
0	11:57:41.673	'3001658': previous successful authorization performed from 152.32.128.46
1	13:23:21.987	'3001658': datacenter connecting failed [6]
0	13:23:22.299	'3001658': login on BroadmanVictory-Live through DC HK2 (ping: 2.04 ms)
0	13:23:22.690	'3001658': login datacenter on BroadmanVictory-Live through DC HK2 (ping: 2.04 ms)
0	13:23:22.831	'3001658': previous successful authorization performed from 152.32.128.46
0	13:23:22.940	'3001658': auto connecting to a better access point DC HK3 (ping is 1.86 ms)
0	13:23:23.268	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 1.86 ms)
0	13:23:23.628	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 1.86 ms)
0	13:23:23.768	'3001658': previous successful authorization performed from 152.32.128.46
1	13:56:05.644	'3001658': ping failed
1	13:56:05.660	'3001658': datacenter connecting failed [6]
0	13:56:06.050	'3001658': login on BroadmanVictory-Live through DC HK4 (ping: 1.84 ms)
0	13:56:06.613	'3001658': login datacenter on BroadmanVictory-Live through DC HK4 (ping: 1.84 ms)
0	13:56:06.738	'3001658': previous successful authorization performed from 152.32.128.46