1	02:23:17.172	'5002952': ping failed
1	02:23:17.188	'5002952': datacenter connecting failed [6]
0	02:23:57.504	'5002952': login on RoboForex-Pro-2 through Singapore (ping: 192.11 ms)
0	02:23:58.816	'5002952': login datacenter on RoboForex-Pro-2 through Singapore (ping: 192.11 ms)
0	02:23:59.473	'5002952': previous successful authorization performed from 101.36.110.43
0	02:24:58.113	'5002952': auto connecting to a better access point Hong Kong (ping is 181.09 ms)
0	02:24:58.801	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 181.09 ms)
0	02:25:00.145	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 181.09 ms)
0	02:25:00.754	'5002952': previous successful authorization performed from 101.36.110.43
1	02:31:00.426	'5002952': ping failed
1	02:31:00.441	'5002952': datacenter connecting failed [6]
1	02:32:01.082	'5002952': connect failed [一般错误]
0	02:32:06.785	'5002952': login on RoboForex-Pro-2 through Czech Republic (ping: 208.91 ms)
0	02:32:08.629	'5002952': login datacenter on RoboForex-Pro-2 through Czech Republic (ping: 208.91 ms)
0	02:32:09.332	'5002952': previous successful authorization performed from 101.36.110.43
0	02:43:04.566	'5002952': login on RoboForex-Pro-2 through Czech Republic (ping: 208.91 ms)
0	02:43:06.551	'5002952': login datacenter on RoboForex-Pro-2 through Czech Republic (ping: 208.91 ms)
0	02:43:07.332	'5002952': previous successful authorization performed from 101.36.110.43
1	02:44:26.832	'5002952': ping failed
1	02:44:26.848	'5002952': datacenter connecting failed [6]
0	02:44:28.098	'5002952': login on RoboForex-Pro-2 through Brazil (ping: 591.96 ms)
0	02:44:31.457	'5002952': login datacenter on RoboForex-Pro-2 through Brazil (ping: 591.96 ms)
0	02:44:32.645	'5002952': previous successful authorization performed from 101.36.110.43
0	02:47:47.957	'5002952': login on RoboForex-Pro-2 through Brazil (ping: 591.96 ms)
0	02:47:51.363	'5002952': login datacenter on RoboForex-Pro-2 through Brazil (ping: 591.96 ms)
0	02:47:52.598	'5002952': previous successful authorization performed from 101.36.110.43
0	03:06:19.026	'5002952': login on RoboForex-Pro-2 through Brazil (ping: 591.96 ms)
0	03:06:22.448	'5002952': login datacenter on RoboForex-Pro-2 through Brazil (ping: 591.96 ms)
0	03:06:23.605	'5002952': previous successful authorization performed from 101.36.110.43
1	03:14:43.167	'5002952': ping failed
1	03:14:43.167	'5002952': datacenter connecting failed [6]
1	03:14:43.183	'5002952': connect failed [没有连接]
0	03:14:48.901	'5002952': login on RoboForex-Pro-2 through Singapore (ping: n/a)
0	03:14:50.245	'5002952': login datacenter on RoboForex-Pro-2 through Singapore (ping: n/a)
0	03:14:50.948	'5002952': previous successful authorization performed from 101.36.110.43
0	03:15:49.089	'5002952': ping to current access point Singapore is 190.69 ms
1	03:17:10.386	'5002952': ping failed
1	03:17:10.386	'5002952': datacenter connecting failed [6]
0	03:17:44.761	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 181.31 ms)
0	03:18:50.808	'5002952': login on RoboForex-Pro-2 through Czech Republic (ping: 198.40 ms)
0	03:18:52.730	'5002952': login datacenter on RoboForex-Pro-2 through Czech Republic (ping: 198.40 ms)
0	03:18:53.495	'5002952': previous successful authorization performed from 101.36.110.43
1	03:20:18.933	'5002952': datacenter connecting failed [6]
0	03:21:08.261	'5002952': login on RoboForex-Pro-2 through Czech Republic (ping: 198.40 ms)
0	03:22:15.323	'5002952': login on RoboForex-Pro-2 through Brazil (ping: 500.71 ms)
0	03:22:18.698	'5002952': login datacenter on RoboForex-Pro-2 through Brazil (ping: 500.71 ms)
0	03:22:19.808	'5002952': previous successful authorization performed from 101.36.110.43
1	03:34:19.590	'5002952': ping failed
1	03:34:19.606	'5002952': datacenter connecting failed [6]
1	03:34:19.621	'5002952': connect failed [没有连接]
0	03:34:25.340	'5002952': login on RoboForex-Pro-2 through Singapore (ping: n/a)
0	03:34:26.824	'5002952': login datacenter on RoboForex-Pro-2 through Singapore (ping: n/a)
0	03:34:27.402	'5002952': previous successful authorization performed from 101.36.110.43
1	03:35:27.481	'5002952': ping failed
0	03:35:35.090	'5002952': ping to current access point Singapore is 191.98 ms
0	03:36:10.324	'5002952': login on RoboForex-Pro-2 through Czech Republic (ping: 195.07 ms)
0	03:36:12.043	'5002952': login datacenter on RoboForex-Pro-2 through Czech Republic (ping: 195.07 ms)
0	03:36:12.731	'5002952': previous successful authorization performed from 101.36.110.43
0	03:41:05.668	'5002952': login on RoboForex-Pro-2 through Czech Republic (ping: 195.07 ms)
0	03:41:07.449	'5002952': login datacenter on RoboForex-Pro-2 through Czech Republic (ping: 195.07 ms)
0	03:41:08.231	'5002952': previous successful authorization performed from 101.36.110.43
1	03:48:48.012	'5002952': ping failed
1	03:48:48.012	'5002952': datacenter connecting failed [6]
0	03:48:48.731	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 180.96 ms)
0	03:48:50.106	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 180.96 ms)
0	03:48:50.684	'5002952': previous successful authorization performed from 101.36.110.43
0	03:50:19.465	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 180.96 ms)
0	03:50:20.481	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 180.96 ms)
0	03:50:21.918	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 180.96 ms)
0	03:50:22.449	'5002952': previous successful authorization performed from 101.36.110.43
1	04:19:03.274	'5002952': ping failed
1	04:19:03.305	'5002952': datacenter connecting failed [2]
0	04:19:04.039	'5002952': login on RoboForex-Pro-2 through Singapore (ping: 191.98 ms)
0	04:19:05.461	'5002952': login datacenter on RoboForex-Pro-2 through Singapore (ping: 191.98 ms)
0	04:19:06.055	'5002952': previous successful authorization performed from 101.36.110.43
1	04:23:45.879	'5002952': datacenter connecting failed [6]
0	04:23:46.770	'5002952': login on RoboForex-Pro-2 through Singapore (ping: 191.98 ms)
0	04:23:49.082	'5002952': login datacenter on RoboForex-Pro-2 through Singapore (ping: 191.98 ms)
0	04:23:49.598	'5002952': previous successful authorization performed from 101.36.110.43
0	04:26:21.441	'5002952': login on RoboForex-Pro-2 through Brazil (ping: 509.69 ms)
0	04:26:24.879	'5002952': login datacenter on RoboForex-Pro-2 through Brazil (ping: 509.69 ms)
0	04:26:25.988	'5002952': previous successful authorization performed from 101.36.110.43
1	04:40:05.832	'5002952': ping failed
1	04:40:05.848	'5002952': datacenter connecting failed [6]
0	04:40:06.676	'5002952': login on RoboForex-Pro-2 through Singapore (ping: 191.98 ms)
0	04:40:08.457	'5002952': login datacenter on RoboForex-Pro-2 through Singapore (ping: 191.98 ms)
0	04:40:09.207	'5002952': previous successful authorization performed from 101.36.110.43
0	04:41:07.082	'5002952': auto connecting to a better access point Czech Republic (ping is 187.22 ms)
0	04:41:07.832	'5002952': login on RoboForex-Pro-2 through Czech Republic (ping: 187.22 ms)
0	04:41:09.488	'5002952': login datacenter on RoboForex-Pro-2 through Czech Republic (ping: 187.22 ms)
0	04:41:10.191	'5002952': previous successful authorization performed from 101.36.110.43
1	04:46:29.910	'5002952': ping failed
1	04:46:29.926	'5002952': datacenter connecting failed [6]
0	04:46:30.816	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 180.83 ms)
0	04:46:44.020	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 180.83 ms)
0	04:46:53.441	'5002952': previous successful authorization performed from 101.36.110.43
1	05:42:15.485	'5002952': ping failed
1	05:42:15.501	'5002952': datacenter connecting failed [2]
0	05:42:16.173	'5002952': login on RoboForex-Pro-2 through Singapore (ping: 200.89 ms)
0	05:42:17.392	'5002952': login datacenter on RoboForex-Pro-2 through Singapore (ping: 200.89 ms)
0	05:42:17.923	'5002952': previous successful authorization performed from 101.36.110.43
0	05:43:16.095	'5002952': auto connecting to a better access point Czech Republic (ping is 189.52 ms)
0	05:43:16.829	'5002952': login on RoboForex-Pro-2 through Czech Republic (ping: 189.52 ms)
0	05:43:18.642	'5002952': login datacenter on RoboForex-Pro-2 through Czech Republic (ping: 189.52 ms)
0	05:43:19.439	'5002952': previous successful authorization performed from 101.36.110.43
0	05:50:28.704	'5002952': login on RoboForex-Pro-2 through Czech Republic (ping: 189.52 ms)
0	05:50:30.548	'5002952': login datacenter on RoboForex-Pro-2 through Czech Republic (ping: 189.52 ms)
0	05:50:31.282	'5002952': previous successful authorization performed from 101.36.110.43
1	06:00:09.039	'5002952': datacenter connecting failed [6]
0	06:00:09.789	'5002952': login on RoboForex-Pro-2 through Czech Republic (ping: 189.52 ms)
0	06:00:11.602	'5002952': login datacenter on RoboForex-Pro-2 through Czech Republic (ping: 189.52 ms)
0	06:00:12.305	'5002952': previous successful authorization performed from 101.36.110.43
1	06:10:52.336	'5002952': ping failed
1	06:10:52.352	'5002952': datacenter connecting failed [6]
0	06:10:53.070	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 181.08 ms)
0	06:10:54.570	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 181.08 ms)
0	06:10:55.086	'5002952': previous successful authorization performed from 101.36.110.43
1	06:14:14.727	'5002952': ping failed
1	06:14:14.742	'5002952': datacenter connecting failed [2]
0	06:14:15.367	'5002952': login on RoboForex-Pro-2 through Singapore (ping: 190.51 ms)
0	06:14:16.711	'5002952': login datacenter on RoboForex-Pro-2 through Singapore (ping: 190.51 ms)
0	06:14:17.289	'5002952': previous successful authorization performed from 101.36.110.43
1	06:18:57.414	'5002952': datacenter connecting failed [6]
0	06:18:58.242	'5002952': login on RoboForex-Pro-2 through Singapore (ping: 190.51 ms)
0	06:19:01.383	'5002952': login datacenter on RoboForex-Pro-2 through Singapore (ping: 190.51 ms)
0	06:19:02.023	'5002952': previous successful authorization performed from 101.36.110.43
0	06:21:38.367	'5002952': login on RoboForex-Pro-2 through Singapore (ping: 190.51 ms)
0	06:21:39.695	'5002952': login datacenter on RoboForex-Pro-2 through Singapore (ping: 190.51 ms)
0	06:21:40.305	'5002952': previous successful authorization performed from 101.36.110.43
1	06:28:20.057	'5002952': ping failed
1	06:28:20.072	'5002952': datacenter connecting failed [6]
0	06:28:39.885	'5002952': login on RoboForex-Pro-2 through Brazil (ping: 501.29 ms)
0	06:29:04.697	'5002952': login datacenter on RoboForex-Pro-2 through Brazil (ping: 501.29 ms)
0	06:29:05.807	'5002952': previous successful authorization performed from 101.36.110.43
0	06:52:19.010	'5002952': login on RoboForex-Pro-2 through Brazil (ping: 501.29 ms)
1	06:53:24.088	'5002952': connect failed [没有连接]
0	06:53:29.791	'5002952': login on RoboForex-Pro-2 through Singapore (ping: n/a)
0	06:53:31.072	'5002952': login datacenter on RoboForex-Pro-2 through Singapore (ping: n/a)
0	06:53:31.557	'5002952': previous successful authorization performed from 101.36.110.43
0	06:54:49.097	'5002952': ping to current access point Singapore is 196.66 ms
1	06:57:31.784	'5002952': ping failed
0	06:58:02.925	'5002952': login on RoboForex-Pro-2 through Czech Republic (ping: 207.71 ms)
0	06:58:04.581	'5002952': login datacenter on RoboForex-Pro-2 through Czech Republic (ping: 207.71 ms)
0	06:58:05.269	'5002952': previous successful authorization performed from 101.36.110.43
1	07:00:25.284	'5002952': datacenter connecting failed [6]
0	07:00:35.347	'5002952': login on RoboForex-Pro-2 through Czech Republic (ping: 207.71 ms)
0	07:00:37.440	'5002952': login datacenter on RoboForex-Pro-2 through Czech Republic (ping: 207.71 ms)
0	07:00:38.253	'5002952': previous successful authorization performed from 101.36.110.43
1	07:06:57.940	'5002952': ping failed
1	07:06:57.956	'5002952': datacenter connecting failed [6]
0	07:06:58.628	'5002952': login on RoboForex-Pro-2 through Singapore (ping: 196.66 ms)
0	07:07:00.050	'5002952': login datacenter on RoboForex-Pro-2 through Singapore (ping: 196.66 ms)
0	07:07:00.769	'5002952': previous successful authorization performed from 101.36.110.43
1	07:09:20.206	'5002952': ping failed
1	07:09:20.206	'5002952': datacenter connecting failed [6]
1	07:09:20.206	'5002952': connect failed [没有连接]
0	07:09:25.862	'5002952': login on RoboForex-Pro-2 through Singapore (ping: n/a)
0	07:09:27.347	'5002952': login datacenter on RoboForex-Pro-2 through Singapore (ping: n/a)
0	07:09:28.019	'5002952': previous successful authorization performed from 101.36.110.43
0	07:10:27.097	'5002952': ping to current access point Singapore is 190.52 ms
1	07:19:07.847	'5002952': ping failed
1	07:19:07.847	'5002952': datacenter connecting failed [6]
0	07:19:08.581	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 180.72 ms)
0	07:19:09.909	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 180.72 ms)
0	07:19:10.394	'5002952': previous successful authorization performed from 101.36.110.43
1	23:25:25.847	'5002952': datacenter connecting failed [6]
1	23:26:12.050	'5002952': connect failed [没有连接]
0	23:27:18.893	'5002952': login on RoboForex-Pro-2 through Russia (ping: n/a)
0	23:27:20.768	'5002952': login datacenter on RoboForex-Pro-2 through Russia (ping: n/a)
0	23:27:21.643	'5002952': previous successful authorization performed from 101.36.110.43
0	23:28:13.347	'5002952': auto connecting to a better access point Hong Kong (ping is 181.75 ms)
0	23:28:14.034	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 181.75 ms)
0	23:28:15.315	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 181.75 ms)
0	23:28:15.909	'5002952': previous successful authorization performed from 101.36.110.43