1	15:35:55.026	'3001658': datacenter connecting failed [6]
0	15:35:55.448	'3001658': login on BroadmanVickery-Live through DC HK4 (ping: 2.22 ms)
0	15:35:55.557	'3001658': login datacenter on BroadmanVickery-Live through DC HK4 (ping: 2.22 ms)
0	15:35:55.666	'3001658': previous successful authorization performed from 152.32.128.46
0	15:35:55.916	'3001658': auto connecting to a better access point DC HK2 (ping is 2.21 ms)
0	15:35:56.416	'3001658': login on BroadmanVickery-Live through DC HK2 (ping: 2.21 ms)
0	15:35:56.759	'3001658': login datacenter on BroadmanVickery-Live through DC HK2 (ping: 2.21 ms)
0	15:35:56.900	'3001658': previous successful authorization performed from 152.32.128.46
1	23:52:23.967	'3001658': ping failed
1	23:52:23.967	'3001658': datacenter connecting failed [6]
0	23:52:24.467	'3001658': login on BroadmanVickery-Live through DC HK3 (ping: 2.26 ms)
0	23:52:24.951	'3001658': login datacenter on BroadmanVickery-Live through DC HK3 (ping: 2.26 ms)
0	23:52:25.201	'3001658': previous successful authorization performed from 152.32.128.46
0	23:52:46.751	'3001658': auto connecting to a better access point DC HK2 (ping is 2.17 ms)
0	23:52:47.220	'3001658': login on BroadmanVickery-Live through DC HK2 (ping: 2.17 ms)
0	23:52:47.532	'3001658': login datacenter on BroadmanVickery-Live through DC HK2 (ping: 2.17 ms)
0	23:52:47.641	'3001658': previous successful authorization performed from 152.32.128.46