1	14:29:05.534	'3001658': ping failed
1	14:29:05.534	'3001658': datacenter connecting failed [6]
0	14:29:08.457	'3001658': login on BroadmanVictory-Live through DC HK4 (ping: 2.59 ms)
0	14:29:09.098	'3001658': login datacenter on BroadmanVictory-Live through DC HK4 (ping: 2.59 ms)
0	14:29:09.192	'3001658': previous successful authorization performed from 152.32.128.46
0	14:29:32.921	'3001658': auto connecting to a better access point DC HK3 (ping is 3.52 ms)
0	14:29:33.265	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 3.52 ms)
0	14:29:33.687	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 3.52 ms)
0	14:29:33.781	'3001658': previous successful authorization performed from 152.32.128.46
1	14:34:14.037	'3001658': ping failed
1	14:34:14.037	'3001658': datacenter connecting failed [6]
0	14:34:17.351	'3001658': login on BroadmanVictory-Live through DC HK4 (ping: 3.04 ms)
0	14:34:31.905	'3001658': login datacenter on BroadmanVictory-Live through DC HK4 (ping: 3.04 ms)
0	14:34:32.905	'3001658': previous successful authorization performed from 152.32.128.46
1	14:46:32.820	'3001658': ping failed
0	14:46:32.820	'3001658': login datacenter on BroadmanVictory-Live
0	14:46:33.148	'3001658': login on BroadmanVictory-Live through DC HK (ping: 4.10 ms)
0	14:46:33.476	'3001658': login datacenter on BroadmanVictory-Live through DC HK (ping: 4.10 ms)
0	14:46:33.617	'3001658': previous successful authorization performed from 152.32.128.46