1	04:50:13.500	'3001658': connect failed [ûÓÐÁ¬½Ó]
0	04:50:50.614	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: n/a)
0	04:50:51.161	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: n/a)
0	04:50:51.302	'3001658': previous successful authorization performed from 152.32.128.46
0	04:51:02.616	'3001658': ping to current access point DC HK3 is 2.54 ms
1	05:43:14.427	'3001658': ping failed
0	05:43:14.755	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 2.54 ms)
0	05:43:15.115	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 2.54 ms)
0	05:43:15.255	'3001658': previous successful authorization performed from 152.32.128.46
1	16:27:21.758	'3001658': ping failed
0	16:27:21.758	'3001658': login datacenter on BroadmanVictory-Live
0	16:27:22.086	'3001658': login on BroadmanVictory-Live through DC HK4 (ping: 2.58 ms)
0	16:27:22.180	'3001658': login datacenter on BroadmanVictory-Live through DC HK4 (ping: 2.58 ms)
0	16:27:22.274	'3001658': previous successful authorization performed from 152.32.128.46
0	16:27:44.493	'3001658': ping to current access point DC HK4 is 2.54 ms
1	16:28:22.227	'3001658': ping failed
1	16:28:22.227	'3001658': datacenter connecting failed [6]
0	16:28:22.571	'3001658': login on BroadmanVictory-Live through DC HK (ping: 4.24 ms)
0	16:28:22.931	'3001658': login datacenter on BroadmanVictory-Live through DC HK (ping: 4.24 ms)
0	16:28:23.056	'3001658': previous successful authorization performed from 152.32.128.46