1	01:23:31.975	'23221917': connect failed [ûÓÐÁ¬½Ó]
0	01:23:37.771	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 259.23 ms)
0	01:23:39.584	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 259.23 ms)
0	01:23:40.037	'23221917': previous successful authorization performed from 162.62.125.91
0	01:23:52.584	'23221917': auto connecting to a better access point London Live SH5 (DC18-1) (ping is 259.29 ms)
0	01:23:56.475	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 259.29 ms)
0	01:23:58.818	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 259.29 ms)
0	01:23:59.912	'23221917': previous successful authorization performed from 152.32.215.116
1	16:30:01.203	'23221917': datacenter connecting failed [6]
0	16:30:02.500	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 259.62 ms)
0	16:30:05.000	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 259.62 ms)
0	16:30:05.593	'23221917': previous successful authorization performed from 152.32.252.153
0	16:30:16.281	'23221917': auto connecting to a better access point London Live Azure (DC18-1) (ping is 188.81 ms)
0	16:30:16.968	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: 188.81 ms)
0	16:30:18.203	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: 188.81 ms)
0	16:30:18.531	'23221917': previous successful authorization performed from 152.32.252.153