1	02:49:36.713	'23221917': datacenter connecting failed [6]
0	02:49:39.760	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 242.96 ms)
0	02:49:42.120	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 242.96 ms)
0	02:49:43.088	'23221917': previous successful authorization performed from 152.32.252.153
0	02:49:56.417	'23221917': auto connecting to a better access point London Live SH5 (DC18-1) (ping is 265.69 ms)
0	02:49:57.276	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 265.69 ms)
0	02:49:58.885	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 265.69 ms)
0	02:49:59.307	'23221917': previous successful authorization performed from 152.32.252.153
1	14:31:25.903	'23221917': connect failed [ûÓÐÁ¬½Ó]
0	14:33:43.184	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live RDB (DC18-1) (ping: n/a)
0	14:33:58.871	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live RDB (DC18-1) (ping: n/a)
0	14:33:59.918	'23221917': previous successful authorization performed from 152.32.215.116
0	14:34:04.762	'23221917': auto connecting to a better access point London Live SH5 (DC18-1) (ping is 244.38 ms)
0	14:34:05.840	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 244.38 ms)
0	14:34:08.231	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 244.38 ms)
0	14:34:08.778	'23221917': previous successful authorization performed from 152.32.215.116
0	15:08:08.609	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 244.38 ms)
0	15:08:11.234	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 244.38 ms)
0	15:08:12.031	'23221917': previous successful authorization performed from 152.32.215.116