0	09:02:09.013	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 2.19 ms)
0	09:02:09.122	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 2.19 ms)
0	09:02:09.247	'3001658': previous successful authorization performed from 152.32.128.46
0	09:02:20.091	'3001658': ping to current access point DC HK3 is 2.34 ms
1	09:06:09.311	'3001658': ping failed
0	09:06:09.311	'3001658': login datacenter on BroadmanVictory-Live
0	09:06:09.592	'3001658': login on BroadmanVictory-Live through DC HK4 (ping: 2.12 ms)
0	09:06:09.702	'3001658': login datacenter on BroadmanVictory-Live through DC HK4 (ping: 2.12 ms)
0	09:06:09.795	'3001658': previous successful authorization performed from 152.32.128.46
1	10:31:53.771	'3001658': ping failed
1	10:31:53.771	'3001658': datacenter connecting failed [6]
0	10:31:54.052	'3001658': login on BroadmanVictory-Live through DC HK (ping: 4.24 ms)
0	10:31:54.412	'3001658': login datacenter on BroadmanVictory-Live through DC HK (ping: 4.24 ms)
0	10:31:54.537	'3001658': previous successful authorization performed from 152.32.128.46
0	10:32:05.224	'3001658': auto connecting to a better access point DC HK3 (ping is 3.66 ms)
0	10:32:05.584	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 3.66 ms)
0	10:32:05.662	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 3.66 ms)
0	10:32:05.756	'3001658': previous successful authorization performed from 152.32.128.46
1	10:35:25.819	'3001658': ping failed
1	10:35:25.851	'3001658': datacenter connecting failed [6]
0	10:35:29.210	'3001658': login on BroadmanVictory-Live through DC HK4 (ping: 3.15 ms)
0	10:35:29.288	'3001658': login datacenter on BroadmanVictory-Live through DC HK4 (ping: 3.15 ms)
0	10:35:29.397	'3001658': previous successful authorization performed from 152.32.128.46
0	12:03:04.578	'3001658': login on BroadmanVictory-Live through DC HK4 (ping: 3.15 ms)
0	12:03:04.672	'3001658': login datacenter on BroadmanVictory-Live through DC HK4 (ping: 3.15 ms)
0	12:03:04.766	'3001658': previous successful authorization performed from 152.32.128.46
0	12:03:15.703	'3001658': auto connecting to a better access point DC HK3 (ping is 2.13 ms)
0	12:03:16.078	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 2.13 ms)
0	12:03:16.156	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 2.13 ms)
0	12:03:16.250	'3001658': previous successful authorization performed from 152.32.128.46
0	15:01:55.362	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 2.13 ms)
0	15:01:55.487	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 2.13 ms)
0	15:01:55.596	'3001658': previous successful authorization performed from 152.32.128.46
0	15:02:06.425	'3001658': ping to current access point DC HK3 is 2.38 ms
1	15:04:46.894	'3001658': datacenter connecting failed [6]
0	15:04:47.238	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 2.38 ms)
0	15:04:47.332	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 2.38 ms)
0	15:04:47.441	'3001658': previous successful authorization performed from 152.32.128.46
1	16:46:12.767	'3001658': ping failed
0	16:46:13.064	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 2.38 ms)
0	16:46:22.173	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 2.38 ms)
0	16:46:22.267	'3001658': previous successful authorization performed from 152.32.128.46
0	16:46:33.064	'3001658': ping to current access point DC HK3 is 2.41 ms
1	18:40:37.829	'3001658': ping failed
1	18:40:37.829	'3001658': datacenter connecting failed [6]
0	18:40:47.204	'3001658': login on BroadmanVictory-Live through DC HK4 (ping: 2.38 ms)
0	18:40:47.298	'3001658': login datacenter on BroadmanVictory-Live through DC HK4 (ping: 2.38 ms)
0	18:40:47.407	'3001658': previous successful authorization performed from 152.32.128.46
0	18:40:58.298	'3001658': auto connecting to a better access point DC HK3 (ping is 2.10 ms)
0	18:40:58.626	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 2.10 ms)
0	18:40:58.720	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 2.10 ms)
0	18:40:58.813	'3001658': previous successful authorization performed from 152.32.128.46
1	20:03:03.183	'3001658': ping failed
0	20:03:03.496	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 2.10 ms)
0	20:03:03.590	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 2.10 ms)
0	20:03:03.683	'3001658': previous successful authorization performed from 152.32.128.46
0	20:03:14.590	'3001658': ping to current access point DC HK3 is 2.87 ms
0	20:17:05.720	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 2.87 ms)
0	20:17:05.814	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 2.87 ms)
0	20:17:05.907	'3001658': previous successful authorization performed from 152.32.128.46
0	21:01:00.189	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 2.87 ms)
0	21:01:00.283	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 2.87 ms)
0	21:01:00.392	'3001658': previous successful authorization performed from 152.32.128.46