1	02:45:05.961	'3001658': ping failed
1	02:45:05.961	'3001658': datacenter connecting failed [6]
0	02:45:06.820	'3001658': login on BroadmanVictory-Live through DC HK2 (ping: 2.71 ms)
0	02:45:07.117	'3001658': login datacenter on BroadmanVictory-Live through DC HK2 (ping: 2.71 ms)
0	02:45:07.257	'3001658': previous successful authorization performed from 152.32.128.46
0	02:45:07.304	'3001658': auto connecting to a better access point DC HK3 (ping is 1.86 ms)
0	02:45:07.726	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 1.86 ms)
0	02:45:08.038	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 1.86 ms)
0	02:45:08.179	'3001658': previous successful authorization performed from 152.32.128.46
0	23:30:44.732	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 1.86 ms)
0	23:31:06.995	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 1.86 ms)
0	23:31:07.120	'3001658': previous successful authorization performed from 152.32.128.46
0	23:31:07.292	'3001658': auto connecting to a better access point DC HK2 (ping is 2.30 ms)
0	23:31:07.620	'3001658': login on BroadmanVictory-Live through DC HK2 (ping: 2.30 ms)
0	23:31:07.995	'3001658': login datacenter on BroadmanVictory-Live through DC HK2 (ping: 2.30 ms)
0	23:31:08.136	'3001658': previous successful authorization performed from 152.32.128.46