1	19:43:15.557	'3001658': ping failed
1	19:43:15.589	'3001658': datacenter connecting failed [6]
0	19:43:58.354	'3001658': login on BroadmanVickery-Live through DC HK (ping: 3.77 ms)
0	19:43:58.823	'3001658': login datacenter on BroadmanVickery-Live through DC HK (ping: 3.77 ms)
0	19:43:58.995	'3001658': auto connecting to a better access point DC HK2 (ping is 2.22 ms)
0	19:44:05.073	'3001658': login on BroadmanVickery-Live through DC HK2 (ping: 2.22 ms)
0	19:44:05.464	'3001658': login datacenter on BroadmanVickery-Live through DC HK2 (ping: 2.22 ms)
0	19:44:05.667	'3001658': previous successful authorization performed from 152.32.128.46
0	19:46:24.543	'3001658': login on BroadmanVickery-Live through DC HK2 (ping: 2.22 ms)
0	19:46:24.918	'3001658': login datacenter on BroadmanVickery-Live through DC HK2 (ping: 2.22 ms)
0	19:46:25.043	'3001658': previous successful authorization performed from 152.32.128.46
1	19:49:05.045	'3001658': ping failed
1	19:49:05.045	'3001658': datacenter connecting failed [6]
0	19:49:05.514	'3001658': login on BroadmanVickery-Live through DC HK3 (ping: 2.33 ms)
0	19:49:05.967	'3001658': login datacenter on BroadmanVickery-Live through DC HK3 (ping: 2.33 ms)
0	19:49:06.185	'3001658': previous successful authorization performed from 152.32.128.46
1	19:50:06.342	'3001658': ping failed
1	19:50:06.420	'3001658': datacenter connecting failed [6]
0	19:50:28.218	'3001658': login on BroadmanVickery-Live through DC HK (ping: 3.06 ms)
0	19:50:28.546	'3001658': login datacenter on BroadmanVickery-Live through DC HK (ping: 3.06 ms)
0	19:50:28.718	'3001658': previous successful authorization performed from 152.32.128.46