1	01:49:16.818	'3001658': ping failed
1	01:49:16.849	'3001658': datacenter connecting failed [6]
0	01:49:17.287	'3001658': login on BroadmanVictory-Live through DC HK2 (ping: 2.12 ms)
0	01:49:17.865	'3001658': login datacenter on BroadmanVictory-Live through DC HK2 (ping: 2.12 ms)
0	01:49:18.037	'3001658': previous successful authorization performed from 152.32.128.46
0	01:49:20.974	'3001658': auto connecting to a better access point DC HK3 (ping is 1.89 ms)
0	01:49:21.333	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 1.89 ms)
0	01:49:21.708	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 1.89 ms)
0	01:49:22.083	'3001658': previous successful authorization performed from 152.32.128.46
1	08:28:26.203	'3001658': ping failed
0	08:28:26.218	'3001658': login datacenter on BroadmanVictory-Live
0	08:28:26.578	'3001658': login on BroadmanVictory-Live through DC HK2 (ping: 2.44 ms)
0	08:28:26.937	'3001658': login datacenter on BroadmanVictory-Live through DC HK2 (ping: 2.44 ms)
0	08:28:27.078	'3001658': previous successful authorization performed from 152.32.128.46
0	08:28:27.234	'3001658': ping to current access point DC HK2 is 2.25 ms