0	16:10:53.642	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live INX (DC18-1) (ping: n/a)
0	16:10:55.502	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live INX (DC18-1) (ping: n/a)
0	16:10:56.845	'23221917': previous successful authorization performed from 152.32.252.153
0	16:10:59.033	'23221917': auto connecting to a better access point London Live Azure (DC18-1) (ping is 268.04 ms)
0	16:10:59.814	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: 268.04 ms)
0	16:11:01.502	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: 268.04 ms)
0	16:11:02.189	'23221917': previous successful authorization performed from 152.32.252.153
1	18:17:04.010	'23221917': datacenter connecting failed [6]
0	18:17:04.557	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: 268.04 ms)
0	18:17:05.714	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: 268.04 ms)
0	18:17:06.339	'23221917': previous successful authorization performed from 152.32.215.116
0	18:17:09.604	'23221917': ping to current access point London Live Azure (DC18-1) is 268.51 ms
1	18:22:42.871	'23221917': datacenter connecting failed [2]
0	18:22:43.371	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: 268.51 ms)
0	18:22:44.605	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: 268.51 ms)
0	18:22:45.261	'23221917': previous successful authorization performed from 152.32.252.153