1	17:24:17.005	'68022821': ping failed
1	17:24:17.083	'68022821': datacenter connecting failed [6]
0	17:24:17.567	'68022821': login on GWFX-Live through JP Access 1 (ping: 102.67 ms)
0	17:24:18.677	'68022821': login datacenter on GWFX-Live through JP Access 1 (ping: 102.67 ms)
0	17:24:18.927	'68022821': previous successful authorization performed from 101.36.110.43
0	17:24:41.817	'68022821': auto connecting to a better access point CN Access 3 (ping is 49.73 ms)
0	17:24:42.208	'68022821': login on GWFX-Live through CN Access 3 (ping: 49.73 ms)
0	17:24:46.271	'68022821': login datacenter on GWFX-Live through CN Access 3 (ping: 49.73 ms)
0	17:24:49.864	'68022821': previous successful authorization performed from 101.36.110.43
1	17:27:05.567	'68022821': ping failed
1	17:27:05.583	'68022821': datacenter connecting failed [6]
0	17:27:05.989	'68022821': login on GWFX-Live through CN Access 6 (ping: 63.72 ms)
0	17:27:16.989	'68022821': login datacenter on GWFX-Live through CN Access 6 (ping: 63.72 ms)
0	17:27:17.771	'68022821': previous successful authorization performed from 101.36.110.43
1	22:50:12.745	'68022821': ping failed
1	22:50:13.292	'68022821': datacenter connecting failed [6]
0	22:50:14.167	'68022821': login on GWFX-Live through CN Access 2 (ping: 86.04 ms)
0	22:50:16.214	'68022821': login datacenter on GWFX-Live through CN Access 2 (ping: 86.04 ms)
0	22:50:17.073	'68022821': previous successful authorization performed from 101.36.110.43
0	22:50:43.448	'68022821': auto connecting to a better access point CN Access 3 (ping is 41.27 ms)
0	22:50:46.886	'68022821': login on GWFX-Live through CN Access 3 (ping: 41.27 ms)
0	22:51:52.464	'68022821': login on GWFX-Live through CN Access 2 (ping: 86.46 ms)
0	22:51:54.776	'68022821': login datacenter on GWFX-Live through CN Access 2 (ping: 86.46 ms)
0	22:51:54.979	'68022821': previous successful authorization performed from 101.36.110.43