1	12:21:16.397	'3001658': connect failed [ûÓÐÁ¬½Ó]
0	12:21:30.851	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 7.33 ms)
0	12:21:30.960	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 7.33 ms)
0	12:21:31.054	'3001658': previous successful authorization performed from 152.32.128.46
0	12:21:45.335	'3001658': ping to current access point DC HK3 is 3.31 ms
1	14:44:37.683	'3001658': ping failed
1	14:44:37.683	'3001658': datacenter connecting failed [6]
0	14:44:38.042	'3001658': login on BroadmanVictory-Live through DC HK4 (ping: 3.27 ms)
0	14:44:38.105	'3001658': login datacenter on BroadmanVictory-Live through DC HK4 (ping: 3.27 ms)
0	14:44:38.199	'3001658': previous successful authorization performed from 152.32.128.46
0	14:44:49.996	'3001658': auto connecting to a better access point DC HK3 (ping is 2.92 ms)
0	14:44:50.371	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 2.92 ms)
0	14:44:50.464	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 2.92 ms)
0	14:44:50.558	'3001658': previous successful authorization performed from 152.32.128.46
1	17:04:37.105	'3001658': ping failed
0	17:04:37.105	'3001658': login datacenter on BroadmanVictory-Live
0	17:04:37.449	'3001658': login on BroadmanVictory-Live through DC HK4 (ping: 2.65 ms)
0	17:04:37.558	'3001658': login datacenter on BroadmanVictory-Live through DC HK4 (ping: 2.65 ms)
0	17:04:37.652	'3001658': previous successful authorization performed from 152.32.128.46
0	17:04:48.496	'3001658': auto connecting to a better access point DC HK3 (ping is 2.87 ms)
0	17:04:48.840	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 2.87 ms)
0	17:04:48.918	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 2.87 ms)
0	17:04:49.012	'3001658': previous successful authorization performed from 152.32.128.46