1	02:59:24.763	'805239': ping failed
1	02:59:24.779	'805239': datacenter connecting failed [6]
0	02:59:25.373	'805239': login on CDGGlobal-Live through DC-3 (ping: 212.60 ms)
0	02:59:26.904	'805239': previous successful authorization performed from 152.32.128.46
0	02:59:29.685	'805239': auto connecting to a better access point DC-2 (ping is 186.56 ms)
0	02:59:30.420	'805239': login on CDGGlobal-Live through DC-2 (ping: 186.56 ms)
0	02:59:31.920	'805239': login datacenter on CDGGlobal-Live through DC-2 (ping: 186.56 ms)
0	02:59:32.248	'805239': previous successful authorization performed from 152.32.128.46
0	11:56:16.392	'805239': login on CDGGlobal-Live through DC-2 (ping: 186.56 ms)
0	11:56:17.829	'805239': login datacenter on CDGGlobal-Live through DC-2 (ping: 186.56 ms)
0	11:56:18.157	'805239': previous successful authorization performed from 152.32.128.46
0	11:56:23.857	'805239': auto connecting to a better access point DC-1 (ping is 186.70 ms)
0	11:56:24.622	'805239': login on CDGGlobal-Live through DC-1 (ping: 186.70 ms)
0	11:56:26.246	'805239': login datacenter on CDGGlobal-Live through DC-1 (ping: 186.70 ms)
0	11:56:26.605	'805239': previous successful authorization performed from 152.32.128.46
1	16:11:37.221	'805239': connect failed [ûÓÐÁ¬½Ó]
0	16:11:42.971	'805239': login on CDGGlobal-Live through DC-2 (ping: 188.43 ms)
0	16:11:44.378	'805239': login datacenter on CDGGlobal-Live through DC-2 (ping: 188.43 ms)
0	16:11:44.674	'805239': previous successful authorization performed from 152.32.128.46
0	16:11:47.112	'805239': ping to current access point DC-2 is 185.69 ms