1	13:35:49.000	'805239': connect failed [ûÓÐÁ¬½Ó]
0	13:35:59.969	'805239': login on CDGGlobal-Live through DC-3 (ping: 199.41 ms)
0	13:36:01.922	'805239': previous successful authorization performed from 152.32.128.46
0	13:36:21.750	'805239': auto connecting to a better access point DC-1 (ping is 172.21 ms)
0	13:36:25.359	'805239': login on CDGGlobal-Live through DC-1 (ping: 172.21 ms)
0	13:36:26.672	'805239': login datacenter on CDGGlobal-Live through DC-1 (ping: 172.21 ms)
0	13:36:27.094	'805239': previous successful authorization performed from 152.32.128.46
1	22:57:44.203	'805239': datacenter connecting failed [6]
0	22:57:44.922	'805239': login on CDGGlobal-Live through DC-2 (ping: 184.35 ms)
0	22:57:46.406	'805239': login datacenter on CDGGlobal-Live through DC-2 (ping: 184.35 ms)
0	22:57:46.750	'805239': previous successful authorization performed from 152.32.128.46
0	22:58:02.422	'805239': auto connecting to a better access point DC-1 (ping is 169.15 ms)
0	22:58:03.125	'805239': login on CDGGlobal-Live through DC-1 (ping: 169.15 ms)
0	22:58:15.297	'805239': login datacenter on CDGGlobal-Live through DC-1 (ping: 169.15 ms)
0	22:58:15.656	'805239': previous successful authorization performed from 152.32.128.46
1	23:02:20.453	'805239': datacenter connecting failed [6]
0	23:02:21.140	'805239': login on CDGGlobal-Live through DC-2 (ping: 186.82 ms)
0	23:02:22.656	'805239': login datacenter on CDGGlobal-Live through DC-2 (ping: 186.82 ms)
0	23:02:22.969	'805239': previous successful authorization performed from 152.32.128.46