1	00:55:48.031	'3001658': connect failed [ûÓÐÁ¬½Ó]
0	00:56:30.203	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: n/a)
0	00:56:30.750	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: n/a)
0	00:56:30.844	'3001658': previous successful authorization performed from 152.32.128.46
0	00:56:41.563	'3001658': ping to current access point DC HK3 is 2.81 ms
0	15:12:32.731	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 2.81 ms)
0	15:12:32.856	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 2.81 ms)
0	15:12:32.966	'3001658': previous successful authorization performed from 152.32.128.46
0	15:12:44.778	'3001658': ping to current access point DC HK3 is 2.52 ms
1	22:22:35.595	'3001658': ping failed
0	22:22:35.595	'3001658': login datacenter on BroadmanVictory-Live
0	22:22:35.923	'3001658': login on BroadmanVictory-Live through DC HK4 (ping: 2.44 ms)
0	22:22:36.017	'3001658': login datacenter on BroadmanVictory-Live through DC HK4 (ping: 2.44 ms)
0	22:22:36.111	'3001658': previous successful authorization performed from 152.32.128.46
0	22:22:47.720	'3001658': auto connecting to a better access point DC HK3 (ping is 2.62 ms)
0	22:22:48.048	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 2.62 ms)
0	22:22:48.142	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 2.62 ms)
0	22:22:48.236	'3001658': previous successful authorization performed from 152.32.128.46