1	19:36:17.777	'23221917': datacenter connecting failed [6]
0	19:36:18.683	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 254.78 ms)
0	19:36:20.949	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 254.78 ms)
0	19:36:22.230	'23221917': previous successful authorization performed from 106.75.31.170
0	19:36:36.480	'23221917': auto connecting to a better access point London Live SH5 (DC18-2) (ping is 187.69 ms)
0	19:36:37.308	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 187.69 ms)
0	19:36:38.933	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 187.69 ms)
0	19:36:39.652	'23221917': previous successful authorization performed from 152.32.252.153
1	23:29:09.528	'23221917': datacenter connecting failed [6]
0	23:29:10.512	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 188.74 ms)
0	23:29:17.090	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 188.74 ms)
0	23:29:18.372	'23221917': previous successful authorization performed from 152.32.252.153
0	23:29:37.481	'23221917': auto connecting to a better access point London Live Azure (DC18-1) (ping is 198.24 ms)
0	23:29:59.622	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 217.91 ms)
0	23:30:02.153	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 217.91 ms)
0	23:30:03.668	'23221917': previous successful authorization performed from 152.32.252.153