0	16:23:11.273	'3001658': login on BroadmanVictory-Live through DC HK2 (ping: 2.30 ms)
0	16:23:11.632	'3001658': login datacenter on BroadmanVictory-Live through DC HK2 (ping: 2.30 ms)
0	16:23:11.773	'3001658': previous successful authorization performed from 152.32.128.46
0	16:23:11.866	'3001658': ping to current access point DC HK2 is 1.99 ms
1	17:16:23.998	'3001658': datacenter connecting failed [6]
0	17:17:06.369	'3001658': login on BroadmanVictory-Live through DC HK4 (ping: 1.85 ms)
0	17:17:06.728	'3001658': login datacenter on BroadmanVictory-Live through DC HK4 (ping: 1.85 ms)
0	17:17:06.868	'3001658': previous successful authorization performed from 152.32.128.46
1	18:33:44.454	'3001658': datacenter connecting failed [6]
0	18:33:44.767	'3001658': login on BroadmanVictory-Live through DC HK4 (ping: 1.85 ms)
0	18:33:45.142	'3001658': login datacenter on BroadmanVictory-Live through DC HK4 (ping: 1.85 ms)
0	18:33:45.282	'3001658': previous successful authorization performed from 152.32.128.46
0	18:33:45.298	'3001658': auto connecting to a better access point DC HK3 (ping is 1.89 ms)
0	18:33:45.673	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 1.89 ms)
0	18:33:46.032	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 1.89 ms)
0	18:33:46.173	'3001658': previous successful authorization performed from 152.32.128.46