1	22:00:29.374	'805239': connect failed [ûÓÐÁ¬½Ó]
0	22:00:35.213	'805239': login on HTFXVULTD-Live through DC-4 (ping: 281.44 ms)
0	22:00:37.415	'805239': login datacenter on HTFXVULTD-Live through DC-4 (ping: 281.44 ms)
0	22:00:38.117	'805239': previous successful authorization performed from 152.32.128.46
0	22:00:43.254	'805239': auto connecting to a better access point DC-3 (ping is 218.66 ms)
0	22:00:44.020	'805239': login on HTFXVULTD-Live through DC-3 (ping: 218.66 ms)
0	22:00:45.550	'805239': login datacenter on HTFXVULTD-Live through DC-3 (ping: 218.66 ms)
0	22:00:46.127	'805239': previous successful authorization performed from 152.32.128.46
1	23:06:46.265	'805239': ping failed
1	23:06:46.280	'805239': datacenter connecting failed [6]
0	23:06:46.952	'805239': login on HTFXVULTD-Live through DC-1 (ping: 239.61 ms)
0	23:06:48.982	'805239': previous successful authorization performed from 152.32.128.46
0	23:06:56.336	'805239': auto connecting to a better access point DC-3 (ping is 218.74 ms)
0	23:06:57.132	'805239': login on HTFXVULTD-Live through DC-3 (ping: 218.74 ms)
0	23:06:58.647	'805239': login datacenter on HTFXVULTD-Live through DC-3 (ping: 218.74 ms)
0	23:06:59.240	'805239': previous successful authorization performed from 152.32.128.46
1	23:42:58.918	'805239': ping failed
1	23:42:58.933	'805239': datacenter connecting failed [6]
0	23:42:59.589	'805239': login on HTFXVULTD-Live through DC-1 (ping: 236.72 ms)
0	23:43:01.556	'805239': previous successful authorization performed from 152.32.128.46