1	09:59:03.910	'3001658': ping failed
1	09:59:03.910	'3001658': datacenter connecting failed [6]
0	09:59:04.253	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 9.77 ms)
0	09:59:04.347	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 9.77 ms)
0	09:59:04.441	'3001658': previous successful authorization performed from 152.32.128.46
0	09:59:24.664	'3001658': ping to current access point DC HK3 is 2.65 ms
1	16:28:49.853	'3001658': ping failed
1	16:28:49.853	'3001658': datacenter connecting failed [6]
0	16:28:50.228	'3001658': login on BroadmanVictory-Live through DC HK4 (ping: 2.71 ms)
0	16:28:50.368	'3001658': login datacenter on BroadmanVictory-Live through DC HK4 (ping: 2.71 ms)
0	16:28:50.478	'3001658': previous successful authorization performed from 152.32.128.46
0	16:29:01.947	'3001658': auto connecting to a better access point DC HK3 (ping is 2.53 ms)
0	16:29:02.259	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 2.53 ms)
0	16:29:02.400	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 2.53 ms)
0	16:29:02.493	'3001658': previous successful authorization performed from 152.32.128.46