1	02:33:18.336	'23221917': ping failed
1	02:33:18.571	'23221917': datacenter connecting failed [6]
0	02:33:19.555	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 251.52 ms)
0	02:33:21.727	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 251.52 ms)
0	02:33:23.055	'23221917': previous successful authorization performed from 152.32.252.153
0	02:33:47.868	'23221917': auto connecting to a better access point London Live SH5 (DC18-2) (ping is 190.26 ms)
0	02:33:49.102	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 190.26 ms)
0	02:33:51.508	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 190.26 ms)
0	02:33:52.055	'23221917': previous successful authorization performed from 152.32.252.153
1	03:01:53.461	'23221917': ping failed
0	03:01:54.618	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 190.26 ms)
0	03:01:56.977	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 190.26 ms)
0	03:01:57.899	'23221917': previous successful authorization performed from 152.32.252.153
1	07:59:32.133	'23221917': ping failed
0	07:59:33.180	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 190.26 ms)
0	07:59:35.305	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 190.26 ms)
0	07:59:35.774	'23221917': previous successful authorization performed from 152.32.252.153
0	07:59:53.743	'23221917': ping to current access point London Live SH5 (DC18-2) is 214.24 ms
1	10:20:22.008	'23221917': ping failed
1	10:20:22.821	'23221917': datacenter connecting failed [6]
0	10:20:24.024	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 251.42 ms)
0	10:20:26.383	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 251.42 ms)
0	10:20:27.321	'23221917': previous successful authorization performed from 152.32.252.153
0	10:20:43.305	'23221917': auto connecting to a better access point London Live SH5 (DC18-2) (ping is 189.79 ms)
0	10:20:44.430	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 189.79 ms)
0	10:20:46.836	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 189.79 ms)
0	10:20:47.789	'23221917': previous successful authorization performed from 152.32.252.153
1	15:28:28.133	'23221917': connect failed [ûÓÐÁ¬½Ó]
0	15:31:29.774	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live INX (DC18-1) (ping: n/a)
0	15:31:43.774	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live INX (DC18-1) (ping: n/a)
0	15:31:44.664	'23221917': previous successful authorization performed from 152.32.215.116
0	15:31:59.086	'23221917': auto connecting to a better access point London Live SH5 (DC18-1) (ping is 250.89 ms)
0	15:32:02.930	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 250.89 ms)
0	15:32:04.727	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 250.89 ms)
0	15:32:05.149	'23221917': previous successful authorization performed from 152.32.215.116
0	15:57:11.368	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live INX (DC18-1) (ping: 189.26 ms)
0	15:57:14.055	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live INX (DC18-1) (ping: 189.26 ms)
0	15:57:15.211	'23221917': previous successful authorization performed from 152.32.252.153