1	01:03:01.639	'3001658': datacenter connecting failed [6]
0	01:03:02.045	'3001658': login on BroadmanVictory-Live through DC HK4 (ping: 1.91 ms)
0	01:03:02.482	'3001658': login datacenter on BroadmanVictory-Live through DC HK4 (ping: 1.91 ms)
0	01:03:02.592	'3001658': previous successful authorization performed from 152.32.128.46
0	01:03:02.763	'3001658': auto connecting to a better access point DC HK3 (ping is 1.92 ms)
0	01:03:03.154	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 1.92 ms)
0	01:03:03.529	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 1.92 ms)
0	01:03:03.654	'3001658': previous successful authorization performed from 152.32.128.46
0	01:36:58.069	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 1.92 ms)
0	01:36:58.647	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 1.92 ms)
0	01:36:58.772	'3001658': previous successful authorization performed from 152.32.128.46
1	04:33:06.964	'3001658': ping failed
1	04:33:06.980	'3001658': datacenter connecting failed [6]
0	04:33:16.323	'3001658': login on BroadmanVictory-Live through DC HK4 (ping: 1.87 ms)
0	04:33:16.713	'3001658': login datacenter on BroadmanVictory-Live through DC HK4 (ping: 1.87 ms)
0	04:33:16.854	'3001658': auto connecting to a better access point DC HK2 (ping is 1.97 ms)
0	04:33:22.353	'3001658': login on BroadmanVictory-Live through DC HK2 (ping: 1.97 ms)
0	04:33:22.681	'3001658': login datacenter on BroadmanVictory-Live through DC HK2 (ping: 1.97 ms)
0	04:33:22.853	'3001658': previous successful authorization performed from 152.32.128.46
1	05:21:04.847	'3001658': ping failed
1	05:21:04.863	'3001658': datacenter connecting failed [6]
0	05:21:08.206	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 2.34 ms)
0	05:21:11.424	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 2.34 ms)
0	05:21:11.518	'3001658': previous successful authorization performed from 152.32.128.46
1	05:27:31.916	'3001658': ping failed
0	05:27:32.260	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 2.34 ms)
0	05:27:32.619	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 2.34 ms)
0	05:27:32.760	'3001658': previous successful authorization performed from 152.32.128.46
0	08:13:48.366	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 2.34 ms)
0	08:13:48.741	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 2.34 ms)
0	08:13:48.881	'3001658': previous successful authorization performed from 152.32.128.46
0	08:13:48.975	'3001658': ping to current access point DC HK3 is 1.85 ms
1	11:27:45.869	'3001658': datacenter connecting failed [6]
0	11:27:46.197	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 1.85 ms)
0	11:27:46.556	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 1.85 ms)
0	11:27:46.697	'3001658': ping to current access point DC HK3 is 1.90 ms
0	11:27:46.697	'3001658': previous successful authorization performed from 152.32.128.46