1	14:46:05.064	'3001658': ping failed
0	14:46:05.064	'3001658': login datacenter on BroadmanVictory-Live
0	14:46:38.464	'3001658': login on BroadmanVictory-Live through DC HK4 (ping: 2.38 ms)
0	14:47:43.981	'3001658': login on BroadmanVictory-Live through DC HK4 (ping: 2.38 ms)
0	14:47:44.231	'3001658': login datacenter on BroadmanVictory-Live through DC HK4 (ping: 2.38 ms)
0	14:47:44.388	'3001658': previous successful authorization performed from 152.32.128.46
0	14:48:06.785	'3001658': auto connecting to a better access point DC HK3 (ping is 2.38 ms)
0	14:48:07.160	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 2.38 ms)
0	14:48:07.550	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 2.38 ms)
0	14:48:07.644	'3001658': previous successful authorization performed from 152.32.128.46
1	15:06:48.910	'3001658': ping failed
0	15:06:48.910	'3001658': login datacenter on BroadmanVictory-Live
0	15:06:49.363	'3001658': login on BroadmanVictory-Live through DC HK4 (ping: 3.78 ms)
0	15:06:58.883	'3001658': login datacenter on BroadmanVictory-Live through DC HK4 (ping: 3.78 ms)
0	15:06:58.977	'3001658': previous successful authorization performed from 152.32.128.46
1	15:44:27.421	'3001658': ping failed
0	15:44:27.421	'3001658': login datacenter on BroadmanVictory-Live
0	15:44:31.062	'3001658': login on BroadmanVictory-Live through DC HK (ping: 4.35 ms)
0	15:44:47.671	'3001658': login datacenter on BroadmanVictory-Live through DC HK (ping: 4.35 ms)
0	15:44:52.312	'3001658': previous successful authorization performed from 152.32.128.46