1	00:06:02.751	'3001658': ping failed
1	00:06:02.767	'3001658': datacenter connecting failed [6]
0	00:06:24.160	'3001658': login on BroadmanVictory-Live through DC HK (ping: 3.86 ms)
0	00:06:24.676	'3001658': login datacenter on BroadmanVictory-Live through DC HK (ping: 3.86 ms)
0	00:06:24.817	'3001658': previous successful authorization performed from 152.32.128.46
0	00:06:35.849	'3001658': auto connecting to a better access point DC HK3 (ping is 2.25 ms)
0	00:06:36.177	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 2.25 ms)
0	00:06:36.552	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 2.25 ms)
0	00:06:36.693	'3001658': previous successful authorization performed from 152.32.128.46
1	00:07:16.808	'3001658': ping failed
0	00:07:41.139	'3001658': login on BroadmanVictory-Live through DC HK4 (ping: 2.62 ms)
0	00:07:41.249	'3001658': login datacenter on BroadmanVictory-Live through DC HK4 (ping: 2.62 ms)
0	00:07:41.342	'3001658': previous successful authorization performed from 152.32.128.46
1	00:09:01.311	'3001658': ping failed
1	00:09:01.358	'3001658': datacenter connecting failed [6]
0	00:09:02.171	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 2.25 ms)
0	00:10:08.054	'3001658': login on BroadmanVictory-Live through DC HK (ping: 4.43 ms)
0	00:10:08.305	'3001658': login datacenter on BroadmanVictory-Live through DC HK (ping: 4.43 ms)
0	00:10:08.445	'3001658': previous successful authorization performed from 152.32.128.46