1	21:02:42.837	'3001658': datacenter connecting failed [6]
0	21:02:52.284	'3001658': login on BroadmanVickery-Live through DC HK4 (ping: 2.24 ms)
0	21:03:34.359	'3001658': login datacenter on BroadmanVickery-Live through DC HK4 (ping: 2.24 ms)
0	21:03:49.495	'3001658': previous successful authorization performed from 152.32.128.46
0	21:04:55.483	'3001658': auto connecting to a better access point DC HK2 (ping is 4328.56 ms)
0	21:05:27.035	'3001658': login on BroadmanVickery-Live through DC HK2 (ping: 4328.56 ms)
0	21:06:50.731	'3001658': login datacenter on BroadmanVickery-Live
0	21:07:16.250	'3001658': auto connecting to a better access point DC HK2 (ping is n/a)
0	21:07:34.099	'3001658': login on BroadmanVickery-Live through DC HK (ping: n/a)
0	21:08:05.012	'3001658': ping to current access point DC HK is 3.64 ms
0	21:08:07.833	'3001658': login datacenter on BroadmanVickery-Live through DC HK (ping: 3.64 ms)
0	21:08:08.566	'3001658': previous successful authorization performed from 152.32.128.46
1	21:11:46.389	'3001658': ping failed
0	21:11:46.638	'3001658': login datacenter on BroadmanVickery-Live
1	21:11:51.377	'3001658': ping failed
0	21:12:02.570	'3001658': login on BroadmanVickery-Live through DC HK2 (ping: 2.08 ms)
0	21:12:04.051	'3001658': login datacenter on BroadmanVickery-Live through DC HK2 (ping: 2.08 ms)
0	21:12:05.657	'3001658': previous successful authorization performed from 152.32.128.46
1	21:21:03.222	'3001658': ping failed
0	21:21:05.358	'3001658': login datacenter on BroadmanVickery-Live
0	21:21:24.002	'3001658': login on BroadmanVickery-Live through DC HK3 (ping: 2.43 ms)
0	21:21:25.077	'3001658': login datacenter on BroadmanVickery-Live through DC HK3 (ping: 2.43 ms)
0	21:21:26.075	'3001658': previous successful authorization performed from 152.32.128.46