1	16:06:12.368	'805239': connect failed [ûÓÐÁ¬½Ó]
0	16:07:05.075	'805239': login on CDGGlobal-Live through DC-3 (ping: n/a)
0	16:07:09.931	'805239': previous successful authorization performed from 152.32.128.46
0	16:07:12.273	'805239': auto connecting to a better access point DC-2 (ping is 186.48 ms)
0	16:07:12.881	'805239': login on CDGGlobal-Live through DC-2 (ping: 186.48 ms)
0	16:07:14.271	'805239': login datacenter on CDGGlobal-Live through DC-2 (ping: 186.48 ms)
0	16:07:14.583	'805239': previous successful authorization performed from 152.32.128.46
0	22:21:32.464	'805239': login on CDGGlobal-Live through DC-3 (ping: 201.85 ms)
0	22:21:34.041	'805239': previous successful authorization performed from 152.32.128.46
0	22:21:47.499	'805239': auto connecting to a better access point DC-2 (ping is 187.32 ms)
0	22:21:48.405	'805239': login on CDGGlobal-Live through DC-2 (ping: 187.32 ms)
0	22:21:50.263	'805239': login datacenter on CDGGlobal-Live through DC-2 (ping: 187.32 ms)
0	22:21:50.716	'805239': previous successful authorization performed from 152.32.128.46
1	22:27:50.320	'805239': ping failed
0	22:27:50.335	'805239': login datacenter on CDGGlobal-Live
0	22:27:51.257	'805239': login on CDGGlobal-Live through DC-1 (ping: 188.53 ms)
0	22:27:52.833	'805239': login datacenter on CDGGlobal-Live through DC-1 (ping: 188.53 ms)
0	22:27:53.239	'805239': previous successful authorization performed from 152.32.128.46