1	15:28:03.684	'23221917': datacenter connecting failed [6]
0	15:28:07.653	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 270.44 ms)
0	15:28:09.388	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 270.44 ms)
0	15:28:10.184	'23221917': previous successful authorization performed from 152.32.215.116
0	15:28:21.122	'23221917': auto connecting to a better access point London Live Azure (DC18-1) (ping is 190.30 ms)
0	15:28:22.184	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: 190.30 ms)
0	15:30:09.669	'23221917': login datacenter on FOREX.comGlobalCN-Live 118
0	15:30:14.809	'23221917': auto connecting to a better access point London Live Azure (DC18-1) (ping is 190.54 ms)
0	15:30:15.841	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: 190.54 ms)
0	15:30:17.044	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: 190.54 ms)
0	15:30:17.669	'23221917': previous successful authorization performed from 152.32.252.153
0	15:32:29.778	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 270.49 ms)
0	15:32:32.434	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 270.49 ms)
0	15:32:33.700	'23221917': previous successful authorization performed from 152.32.252.153
1	16:26:35.170	'23221917': ping failed
1	16:26:35.232	'23221917': datacenter connecting failed [6]
0	16:26:36.389	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 275.84 ms)
0	16:26:42.373	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 275.84 ms)
0	16:26:44.217	'23221917': previous successful authorization performed from 152.32.252.153