1	13:59:30.850	'3001658': ping failed
1	13:59:30.866	'3001658': datacenter connecting failed [6]
0	13:59:31.303	'3001658': login on BroadmanVickery-Live through DC HK3 (ping: 2.15 ms)
0	13:59:31.678	'3001658': login datacenter on BroadmanVickery-Live through DC HK3 (ping: 2.15 ms)
0	13:59:31.788	'3001658': previous successful authorization performed from 152.32.128.46
0	13:59:32.257	'3001658': auto connecting to a better access point DC HK2 (ping is 2.51 ms)
0	13:59:32.678	'3001658': login on BroadmanVickery-Live through DC HK2 (ping: 2.51 ms)
0	13:59:33.022	'3001658': login datacenter on BroadmanVickery-Live through DC HK2 (ping: 2.51 ms)
0	13:59:33.194	'3001658': previous successful authorization performed from 152.32.128.46
1	20:14:06.430	'3001658': datacenter connecting failed [6]
0	20:14:06.929	'3001658': login on BroadmanVickery-Live through DC HK3 (ping: 2.60 ms)
0	20:14:07.335	'3001658': login datacenter on BroadmanVickery-Live through DC HK3 (ping: 2.60 ms)
0	20:14:07.492	'3001658': previous successful authorization performed from 152.32.128.46
0	20:14:07.960	'3001658': ping to current access point DC HK3 is 2.37 ms
1	20:38:07.667	'3001658': ping failed
1	20:38:07.683	'3001658': datacenter connecting failed [6]
1	20:39:08.118	'3001658': connect failed [ûÓÐÁ¬½Ó]
0	20:39:13.693	'3001658': login on BroadmanVickery-Live through DC HK2 (ping: 3.02 ms)
0	20:39:14.021	'3001658': login datacenter on BroadmanVickery-Live through DC HK2 (ping: 3.02 ms)
0	20:39:14.162	'3001658': previous successful authorization performed from 152.32.128.46