0	09:43:20.446	'3001658': login on BroadmanVictory-Live through DC HK4 (ping: 2.29 ms)
0	09:43:20.571	'3001658': login datacenter on BroadmanVictory-Live through DC HK4 (ping: 2.29 ms)
0	09:43:20.711	'3001658': previous successful authorization performed from 152.32.128.46
0	09:43:31.321	'3001658': auto connecting to a better access point DC HK3 (ping is 2.50 ms)
0	09:43:31.680	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 2.50 ms)
0	09:43:32.040	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 2.50 ms)
0	09:43:32.180	'3001658': previous successful authorization performed from 152.32.128.46
1	10:31:54.339	'3001658': ping failed
1	10:31:54.339	'3001658': datacenter connecting failed [6]
0	10:31:57.714	'3001658': login on BroadmanVictory-Live through DC HK4 (ping: 2.12 ms)
0	10:31:57.808	'3001658': login datacenter on BroadmanVictory-Live through DC HK4 (ping: 2.12 ms)
0	10:31:57.933	'3001658': previous successful authorization performed from 152.32.128.46
1	16:50:15.694	'3001658': ping failed
1	16:50:15.694	'3001658': datacenter connecting failed [6]
0	16:50:16.085	'3001658': login on BroadmanVictory-Live through DC HK (ping: 4.13 ms)
0	16:50:16.444	'3001658': login datacenter on BroadmanVictory-Live through DC HK (ping: 4.13 ms)
0	16:50:16.632	'3001658': previous successful authorization performed from 152.32.128.46
0	16:50:37.054	'3001658': auto connecting to a better access point DC HK3 (ping is 2.61 ms)
0	16:50:37.397	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 2.61 ms)
0	16:50:37.757	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 2.61 ms)
0	16:50:37.913	'3001658': previous successful authorization performed from 152.32.128.46