1	01:11:17.114	'3001658': ping failed
1	01:11:17.129	'3001658': datacenter connecting failed [2]
0	01:11:17.457	'3001658': login on BroadmanVictory-Live through DC HK4 (ping: 2.48 ms)
0	01:11:17.551	'3001658': login datacenter on BroadmanVictory-Live through DC HK4 (ping: 2.48 ms)
0	01:11:17.645	'3001658': previous successful authorization performed from 152.32.128.46
0	01:11:28.879	'3001658': auto connecting to a better access point DC HK3 (ping is 1.92 ms)
0	01:11:29.239	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 1.92 ms)
0	01:11:29.614	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 1.92 ms)
0	01:11:29.754	'3001658': previous successful authorization performed from 152.32.128.46
1	03:06:55.804	'3001658': ping failed
1	03:06:55.804	'3001658': datacenter connecting failed [6]
0	03:06:56.101	'3001658': login on BroadmanVictory-Live through DC HK4 (ping: 3.19 ms)
0	03:06:56.195	'3001658': login datacenter on BroadmanVictory-Live through DC HK4 (ping: 3.19 ms)
0	03:06:56.304	'3001658': previous successful authorization performed from 152.32.128.46
0	03:07:07.101	'3001658': auto connecting to a better access point DC HK3 (ping is 2.64 ms)
0	03:07:07.476	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 2.64 ms)
0	03:07:07.805	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 2.64 ms)
0	03:07:07.945	'3001658': previous successful authorization performed from 152.32.128.46
0	04:04:02.712	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 2.64 ms)
0	04:04:03.040	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 2.64 ms)
0	04:04:03.181	'3001658': previous successful authorization performed from 152.32.128.46