1	16:43:31.713	'805239': ping failed
1	16:43:31.728	'805239': datacenter connecting failed [6]
0	16:43:32.573	'805239': login on CDGGlobal-Live through DC-4 (ping: 208.23 ms)
0	16:43:34.309	'805239': login datacenter on CDGGlobal-Live through DC-4 (ping: 208.23 ms)
0	16:43:34.700	'805239': previous successful authorization performed from 152.32.128.46
0	16:43:38.000	'805239': auto connecting to a better access point DC-1 (ping is 175.49 ms)
0	16:43:38.735	'805239': login on CDGGlobal-Live through DC-1 (ping: 175.49 ms)
0	16:43:40.315	'805239': login datacenter on CDGGlobal-Live through DC-1 (ping: 175.49 ms)
0	16:43:41.550	'805239': previous successful authorization performed from 152.32.128.46
1	22:32:52.197	'805239': datacenter connecting failed [6]
0	22:32:52.979	'805239': login on CDGGlobal-Live through DC-4 (ping: 208.92 ms)
0	22:32:54.575	'805239': login datacenter on CDGGlobal-Live through DC-4 (ping: 208.92 ms)
0	22:32:54.950	'805239': previous successful authorization performed from 152.32.128.46
0	22:33:01.847	'805239': auto connecting to a better access point DC-1 (ping is 189.49 ms)
0	22:33:02.488	'805239': login on CDGGlobal-Live through DC-1 (ping: 189.49 ms)
0	22:33:04.553	'805239': login datacenter on CDGGlobal-Live through DC-1 (ping: 189.49 ms)
0	22:33:04.913	'805239': previous successful authorization performed from 152.32.128.46
1	22:49:23.767	'805239': datacenter connecting failed [6]
0	22:49:24.580	'805239': login on CDGGlobal-Live through DC-4 (ping: 207.32 ms)
0	22:49:26.269	'805239': login datacenter on CDGGlobal-Live through DC-4 (ping: 207.32 ms)
0	22:49:26.692	'805239': previous successful authorization performed from 152.32.128.46