1	13:05:46.830	'805239': datacenter connecting failed [6]
1	13:05:47.002	'805239': connect failed [ûÓÐÁ¬½Ó]
0	13:05:52.798	'805239': login on CDGGlobal-Live through DC-4 (ping: 275.94 ms)
0	13:05:54.501	'805239': login datacenter on CDGGlobal-Live through DC-4 (ping: 275.94 ms)
0	13:05:55.188	'805239': previous successful authorization performed from 152.32.128.46
0	13:06:08.544	'805239': auto connecting to a better access point DC-1 (ping is 190.16 ms)
0	13:06:09.138	'805239': login on CDGGlobal-Live through DC-1 (ping: 190.16 ms)
0	13:06:11.200	'805239': login datacenter on CDGGlobal-Live through DC-1 (ping: 190.16 ms)
0	13:06:11.778	'805239': previous successful authorization performed from 152.32.128.46
1	22:00:53.250	'805239': ping failed
1	22:00:53.266	'805239': datacenter connecting failed [6]
0	22:00:53.953	'805239': login on CDGGlobal-Live through DC-3 (ping: 200.12 ms)
0	22:00:56.047	'805239': previous successful authorization performed from 152.32.128.46
0	22:01:09.672	'805239': auto connecting to a better access point DC-1 (ping is 190.33 ms)
0	22:01:10.578	'805239': login on CDGGlobal-Live through DC-1 (ping: 190.33 ms)
0	22:01:12.875	'805239': login datacenter on CDGGlobal-Live through DC-1 (ping: 190.33 ms)
0	22:01:13.453	'805239': previous successful authorization performed from 152.32.128.46
1	22:09:17.531	'805239': datacenter connecting failed [6]
0	22:09:18.234	'805239': login on CDGGlobal-Live through DC-3 (ping: 217.86 ms)
0	22:09:20.406	'805239': previous successful authorization performed from 152.32.128.46