1	11:51:41.080	'23221917': ping failed
1	11:51:41.095	'23221917': datacenter connecting failed [6]
0	11:51:42.251	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 389.30 ms)
0	11:51:44.720	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 389.30 ms)
0	11:51:45.626	'23221917': previous successful authorization performed from 152.32.215.116
0	11:51:50.423	'23221917': auto connecting to a better access point London Live Azure (DC18-1) (ping is 219.62 ms)
0	11:51:51.267	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: 219.62 ms)
0	11:51:52.923	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: 219.62 ms)
0	11:51:53.705	'23221917': previous successful authorization performed from 152.32.252.153
1	11:52:52.970	'23221917': ping failed
1	11:52:52.986	'23221917': datacenter connecting failed [6]
0	11:52:54.126	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 388.71 ms)
0	11:52:59.564	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 388.71 ms)
0	11:53:00.470	'23221917': previous successful authorization performed from 152.32.215.116
1	12:35:00.197	'23221917': datacenter connecting failed [6]
1	12:35:00.416	'23221917': connect failed [ûÓÐÁ¬½Ó]
0	12:35:06.385	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 389.56 ms)
0	12:35:08.916	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 389.56 ms)
0	12:35:09.869	'23221917': previous successful authorization performed from 152.32.215.116