1	05:41:34.796	'23221917': datacenter connecting failed [6]
0	05:41:35.531	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: 190.11 ms)
0	05:41:36.843	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: 190.11 ms)
0	05:41:37.500	'23221917': previous successful authorization performed from 152.32.215.116
0	05:41:44.312	'23221917': ping to current access point London Live Azure (DC18-1) is 189.43 ms
1	06:09:10.477	'23221917': datacenter connecting failed [6]
0	06:09:11.368	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: 189.43 ms)
0	06:09:12.649	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: 189.43 ms)
0	06:09:13.305	'23221917': previous successful authorization performed from 152.32.215.116
1	06:11:15.524	'23221917': datacenter connecting failed [6]
0	06:11:16.243	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: 189.43 ms)
0	06:11:17.446	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: 189.43 ms)
0	06:11:18.086	'23221917': previous successful authorization performed from 152.32.215.116
1	06:21:17.915	'23221917': ping failed
1	06:21:18.915	'23221917': datacenter connecting failed [6]
0	06:21:19.774	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 270.73 ms)
0	06:21:21.805	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 270.73 ms)
0	06:21:22.711	'23221917': previous successful authorization performed from 152.32.252.153
1	06:32:02.508	'23221917': ping failed
1	06:32:23.527	'23221917': datacenter connecting failed [6]
0	06:32:27.667	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 274.53 ms)
0	06:32:30.417	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 274.53 ms)
0	06:32:31.855	'23221917': previous successful authorization performed from 152.32.215.116
1	08:25:15.076	'23221917': datacenter connecting failed [6]
0	08:25:16.138	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 274.53 ms)
0	08:25:22.201	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 274.53 ms)
0	08:25:23.623	'23221917': previous successful authorization performed from 152.32.252.153
0	08:25:29.279	'23221917': auto connecting to a better access point London Live Azure (DC18-1) (ping is 190.34 ms)
0	08:25:30.060	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: 190.34 ms)
0	08:25:31.294	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: 190.34 ms)
0	08:25:31.966	'23221917': previous successful authorization performed from 152.32.252.153
1	09:41:14.857	'23221917': ping failed
1	09:41:14.888	'23221917': datacenter connecting failed [6]
0	09:41:15.857	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 403.29 ms)
0	09:41:17.888	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 403.29 ms)
0	09:41:18.763	'23221917': previous successful authorization performed from 152.32.252.153
0	09:41:23.998	'23221917': auto connecting to a better access point London Live Azure (DC18-1) (ping is 190.09 ms)
0	09:41:24.748	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: 190.09 ms)
0	09:41:26.013	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: 190.09 ms)
0	09:41:26.654	'23221917': previous successful authorization performed from 152.32.252.153