1	00:08:36.389	'23221917': ping failed
0	00:08:37.233	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 268.69 ms)
0	00:08:38.795	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 268.69 ms)
0	00:08:39.686	'23221917': previous successful authorization performed from 152.32.215.116
0	00:08:45.030	'23221917': ping to current access point London Live SH5 (DC18-1) is 240.05 ms
0	09:10:10.733	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 240.05 ms)
0	09:10:12.545	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 240.05 ms)
0	09:10:12.983	'23221917': previous successful authorization performed from 152.32.252.153
0	09:10:18.467	'23221917': ping to current access point London Live SH5 (DC18-1) is 243.07 ms
0	09:34:52.655	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 243.07 ms)
0	09:34:56.561	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 243.07 ms)
0	09:34:57.311	'23221917': previous successful authorization performed from 152.32.215.116
1	10:07:58.014	'23221917': ping failed
0	10:07:59.639	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 243.07 ms)
0	10:08:02.936	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 243.07 ms)
0	10:08:04.702	'23221917': previous successful authorization performed from 152.32.215.116
1	15:05:18.608	'23221917': datacenter connecting failed [6]
0	15:05:25.733	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 243.07 ms)
0	15:05:29.233	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 243.07 ms)
0	15:05:30.327	'23221917': previous successful authorization performed from 152.32.215.116
0	15:05:36.530	'23221917': auto connecting to a better access point London Live SH5 (DC18-2) (ping is 241.03 ms)
0	15:05:37.436	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 241.03 ms)
0	15:05:41.608	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 241.03 ms)
0	15:05:42.202	'23221917': previous successful authorization performed from 152.32.252.153
0	15:07:21.373	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 241.03 ms)
0	15:07:25.202	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 241.03 ms)
0	15:07:26.795	'23221917': previous successful authorization performed from 152.32.252.153
0	15:24:41.764	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 241.03 ms)
0	15:24:45.280	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 241.03 ms)
0	15:24:46.202	'23221917': previous successful authorization performed from 152.32.252.153
0	15:53:00.483	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 269.53 ms)
0	15:53:04.702	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 269.53 ms)
0	15:53:06.764	'23221917': previous successful authorization performed from 152.32.252.153
0	16:20:18.233	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live INX (DC18-1) (ping: 189.75 ms)
0	16:20:19.827	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live INX (DC18-1) (ping: 189.75 ms)
0	16:20:20.717	'23221917': previous successful authorization performed from 152.32.252.153
0	16:20:25.905	'23221917': auto connecting to a better access point London Live SH5 (DC18-1) (ping is 241.28 ms)
0	16:20:27.530	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 241.28 ms)
0	16:20:29.967	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 241.28 ms)
0	16:20:30.389	'23221917': previous successful authorization performed from 152.32.252.153
0	16:34:14.014	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 241.28 ms)
0	16:34:23.467	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 241.28 ms)
0	16:34:24.608	'23221917': previous successful authorization performed from 152.32.252.153
0	16:50:01.717	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 268.46 ms)
0	16:50:04.905	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 268.46 ms)
0	16:50:05.811	'23221917': previous successful authorization performed from 152.32.252.153
0	16:54:25.842	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 268.46 ms)
0	16:54:28.030	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 268.46 ms)
0	16:54:28.467	'23221917': previous successful authorization performed from 152.32.252.153
0	17:40:42.592	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 268.46 ms)
0	17:40:44.889	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 268.46 ms)
0	17:40:45.827	'23221917': previous successful authorization performed from 152.32.215.116
0	17:40:53.811	'23221917': ping to current access point London Live SH5 (DC18-2) is 239.72 ms
0	17:51:23.264	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 239.72 ms)
0	17:51:26.405	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 239.72 ms)
0	17:51:26.780	'23221917': previous successful authorization performed from 152.32.252.153
0	18:05:14.092	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 239.72 ms)
0	18:05:16.389	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 239.72 ms)
0	18:05:17.358	'23221917': previous successful authorization performed from 152.32.215.116
0	19:41:49.545	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 239.72 ms)
0	19:41:51.405	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 239.72 ms)
0	19:41:52.248	'23221917': previous successful authorization performed from 152.32.215.116
0	19:41:58.467	'23221917': auto connecting to a better access point London Live SH5 (DC18-1) (ping is 241.64 ms)
0	19:41:59.202	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 241.64 ms)
0	19:42:01.061	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 241.64 ms)
0	19:42:01.592	'23221917': previous successful authorization performed from 152.32.252.153
0	20:06:12.952	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 242.36 ms)
0	20:06:17.905	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 242.36 ms)
0	20:06:18.748	'23221917': previous successful authorization performed from 152.32.252.153
0	20:07:58.592	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 242.36 ms)
0	20:08:01.795	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 242.36 ms)
0	20:08:02.405	'23221917': previous successful authorization performed from 152.32.252.153
1	20:21:29.467	'23221917': connect failed [ûÓÐÁ¬½Ó]
0	20:21:35.061	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live INX (DC18-1) (ping: 288.81 ms)
0	20:21:36.623	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live INX (DC18-1) (ping: 288.81 ms)
0	20:21:37.514	'23221917': previous successful authorization performed from 152.32.215.116