1	00:45:04.534	'3001658': ping failed
0	00:45:04.908	'3001658': login on BroadmanVictory-Live through DC HK2 (ping: 2.14 ms)
0	00:45:05.674	'3001658': login datacenter on BroadmanVictory-Live through DC HK2 (ping: 2.14 ms)
0	00:45:05.830	'3001658': previous successful authorization performed from 152.32.128.46
0	00:45:05.971	'3001658': ping to current access point DC HK2 is 2.76 ms
1	09:42:41.406	'3001658': datacenter connecting failed [6]
0	09:43:42.359	'3001658': login on BroadmanVictory-Live through DC HK (ping: 5.93 ms)
0	09:43:42.750	'3001658': login datacenter on BroadmanVictory-Live through DC HK (ping: 5.93 ms)
0	09:43:42.891	'3001658': previous successful authorization performed from 152.32.128.46
0	09:43:59.297	'3001658': auto connecting to a better access point DC HK3 (ping is 2.60 ms)
0	09:43:59.609	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 2.60 ms)
0	09:43:59.984	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 2.60 ms)
0	09:44:00.125	'3001658': previous successful authorization performed from 152.32.128.46
0	09:45:15.250	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 2.60 ms)
0	09:45:29.438	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 2.60 ms)
0	09:45:29.563	'3001658': previous successful authorization performed from 152.32.128.46