1	14:10:53.744	'23221917': datacenter connecting failed [6]
0	14:10:54.728	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 269.67 ms)
0	14:10:56.478	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 269.67 ms)
0	14:10:57.228	'23221917': previous successful authorization performed from 162.62.125.91
0	14:11:02.525	'23221917': auto connecting to a better access point London Live Azure (DC18-1) (ping is 190.03 ms)
0	14:11:03.275	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: 190.03 ms)
0	14:11:04.807	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: 190.03 ms)
0	14:11:05.525	'23221917': previous successful authorization performed from 152.32.252.153
1	18:37:23.845	'23221917': ping failed
0	18:37:53.329	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 211.22 ms)
1	18:40:11.970	'23221917': datacenter connecting failed [6]
0	18:41:51.907	'23221917': auto connecting to a better access point London Live Azure (DC18-1) (ping is n/a)
0	18:41:54.485	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: n/a)
0	18:41:55.876	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: n/a)
0	18:41:56.563	'23221917': previous successful authorization performed from 152.32.252.153
0	18:42:10.016	'23221917': ping to current access point London Live Azure (DC18-1) is 189.75 ms