1	00:00:47.074	'5002952': ping failed
1	00:00:47.090	'5002952': datacenter connecting failed [6]
0	00:00:49.449	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 278.87 ms)
0	00:00:56.574	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 278.87 ms)
0	00:01:10.091	'5002952': previous successful authorization performed from 103.233.11.58
1	00:02:36.907	'5002952': ping failed
1	00:02:36.923	'5002952': datacenter connecting failed [6]
0	00:02:38.189	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 290.82 ms)
0	00:02:44.158	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 290.82 ms)
0	00:02:47.814	'5002952': previous successful authorization performed from 103.233.11.58
1	00:07:24.640	'5002952': ping failed
0	00:07:25.952	'5002952': login on RoboForex-Pro-2 through DataCenter Russia (ping: 320.10 ms)
0	00:07:28.655	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Russia (ping: 320.10 ms)
0	00:07:29.593	'5002952': previous successful authorization performed from 103.233.11.58
1	00:16:05.586	'5002952': ping failed
1	00:16:05.602	'5002952': datacenter connecting failed [6]
0	00:16:07.039	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #5 (ping: 374.45 ms)
0	00:16:29.306	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #5 (ping: 374.45 ms)
0	00:16:30.415	'5002952': previous successful authorization performed from 103.233.11.58
0	00:17:16.214	'5002952': auto connecting to a better access point DataCenter Singapore (ping is 210.20 ms)
0	00:17:17.261	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 210.20 ms)
0	00:17:22.637	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 210.20 ms)
0	00:17:23.246	'5002952': previous successful authorization performed from 103.233.11.58
1	02:32:49.021	'5002952': ping failed
1	02:32:49.036	'5002952': datacenter connecting failed [6]
0	02:32:50.318	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 283.67 ms)
0	02:32:56.380	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 283.67 ms)
0	02:32:57.271	'5002952': previous successful authorization performed from 103.233.11.58
0	02:33:47.039	'5002952': auto connecting to a better access point DataCenter Singapore (ping is 210.44 ms)
0	02:33:50.555	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 210.44 ms)
0	02:33:59.587	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 210.44 ms)
0	02:34:00.243	'5002952': previous successful authorization performed from 103.233.11.58
0	02:47:29.156	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 210.44 ms)
0	02:47:35.500	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 210.44 ms)
0	02:47:36.047	'5002952': previous successful authorization performed from 103.233.11.58
1	02:57:36.763	'5002952': ping failed
0	02:57:37.904	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 210.44 ms)
0	02:57:40.419	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 210.44 ms)
0	02:57:45.873	'5002952': previous successful authorization performed from 103.233.11.58
1	02:58:31.859	MQL5.community: authorization failed
1	03:20:09.546	'5002952': datacenter connecting failed [6]
0	03:20:10.968	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 277.14 ms)
0	03:20:14.327	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 277.14 ms)
0	03:20:15.233	'5002952': previous successful authorization performed from 103.233.11.58
1	03:25:34.858	'5002952': ping failed
1	03:25:34.874	'5002952': datacenter connecting failed [6]
0	03:25:36.952	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 279.52 ms)
0	03:25:57.750	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 279.52 ms)
0	03:25:58.609	'5002952': previous successful authorization performed from 103.233.11.58
1	03:34:38.446	'5002952': ping failed
1	03:34:38.462	'5002952': datacenter connecting failed [6]
0	03:34:39.977	'5002952': login on RoboForex-Pro-2 through DataCenter Russia (ping: 317.75 ms)
0	03:35:41.215	'5002952': login datacenter on RoboForex-Pro-2
0	03:35:57.606	'5002952': login on RoboForex-Pro-2 through DataCenter Brazil (ping: 347.65 ms)
0	03:36:15.779	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Brazil (ping: 347.65 ms)
0	03:36:19.482	'5002952': previous successful authorization performed from 103.233.11.58
0	03:36:44.655	'5002952': auto connecting to a better access point DataCenter Singapore (ping is 210.34 ms)
0	03:36:45.890	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 210.34 ms)
0	03:36:51.109	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 210.34 ms)
0	03:36:51.812	'5002952': previous successful authorization performed from 103.233.11.58
1	03:38:11.362	'5002952': ping failed
1	03:38:11.378	'5002952': datacenter connecting failed [6]
0	03:38:15.691	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 276.06 ms)
0	03:38:25.926	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 276.06 ms)
0	03:38:26.863	'5002952': previous successful authorization performed from 103.233.11.58
1	03:39:46.679	'5002952': datacenter connecting failed [6]
0	03:39:51.023	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 278.12 ms)
0	03:39:54.414	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 278.12 ms)
0	03:39:55.617	'5002952': previous successful authorization performed from 103.233.11.58
1	03:42:59.814	'5002952': ping failed
1	03:42:59.829	'5002952': datacenter connecting failed [6]
0	03:43:01.298	'5002952': login on RoboForex-Pro-2 through DataCenter Russia (ping: 328.86 ms)
0	03:43:05.579	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Russia (ping: 328.86 ms)
0	03:43:06.876	'5002952': previous successful authorization performed from 103.233.11.58
1	03:46:31.683	'5002952': ping failed
1	03:46:31.699	'5002952': datacenter connecting failed [6]
0	03:46:33.433	'5002952': login on RoboForex-Pro-2 through DataCenter Brazil (ping: 339.61 ms)
0	03:46:37.543	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Brazil (ping: 339.61 ms)
0	03:46:38.730	'5002952': previous successful authorization performed from 103.233.11.58
1	03:49:29.676	'5002952': datacenter connecting failed [6]
0	03:49:50.333	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #5 (ping: 369.83 ms)
1	03:51:11.665	'5002952': datacenter connecting failed [6]
0	03:51:18.634	'5002952': login on RoboForex-Pro-2 through Europe DNS (ping: 276.85 ms)
0	03:51:21.165	'5002952': login datacenter on RoboForex-Pro-2 through Europe DNS (ping: 276.85 ms)
0	03:51:22.025	'5002952': previous successful authorization performed from 103.233.11.58
0	03:51:43.666	'5002952': ping to current access point Europe DNS is n/a
1	03:52:44.685	'5002952': datacenter connecting failed [6]
0	03:52:45.935	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 210.36 ms)
0	03:52:47.857	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 210.36 ms)
0	03:52:48.451	'5002952': previous successful authorization performed from 103.233.11.58
1	08:06:22.639	'5002952': ping failed
1	08:06:22.654	'5002952': datacenter connecting failed [6]
0	08:06:23.873	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 282.03 ms)
0	08:06:55.906	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 282.03 ms)
0	08:07:04.406	'5002952': previous successful authorization performed from 103.233.11.58
0	08:08:08.128	'5002952': auto connecting to a better access point DataCenter Singapore (ping is 210.35 ms)
0	08:08:09.300	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 210.35 ms)
0	08:08:14.206	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 210.35 ms)
0	08:08:14.800	'5002952': previous successful authorization performed from 103.233.11.58
1	08:09:34.320	'5002952': ping failed
1	08:09:34.335	'5002952': datacenter connecting failed [6]
0	08:09:35.695	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 280.02 ms)
0	08:09:43.070	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 280.02 ms)
0	08:09:43.945	'5002952': previous successful authorization performed from 103.233.11.58
1	08:16:03.635	'5002952': ping failed
1	08:16:03.650	'5002952': datacenter connecting failed [6]
0	08:16:14.182	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 291.78 ms)
0	08:16:20.839	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 291.78 ms)
0	08:16:21.745	'5002952': previous successful authorization performed from 103.233.11.58
1	08:20:41.304	'5002952': ping failed
1	08:20:41.320	'5002952': datacenter connecting failed [6]
0	08:20:44.273	'5002952': login on RoboForex-Pro-2 through DataCenter Russia (ping: 323.73 ms)
0	08:21:45.245	'5002952': login datacenter on RoboForex-Pro-2
0	08:21:55.292	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #5 (ping: 357.46 ms)
0	08:22:43.669	'5002952': ping to current access point DataCenter Europe #5 is 379.37 ms
0	08:22:59.358	'5002952': login datacenter on RoboForex-Pro-2
0	08:23:06.186	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 214.03 ms)
0	08:23:08.483	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 214.03 ms)
0	08:23:09.202	'5002952': previous successful authorization performed from 103.233.11.58
0	08:23:43.657	'5002952': ping to current access point DataCenter Singapore is 209.06 ms
1	08:23:59.861	MQL5.community: authorization failed
1	08:32:16.212	'5002952': ping failed
0	08:32:20.447	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 280.02 ms)
0	08:32:27.134	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 280.02 ms)
0	08:32:28.041	'5002952': previous successful authorization performed from 103.233.11.58
1	08:33:57.842	'5002952': datacenter connecting failed [6]
0	08:33:59.154	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 281.25 ms)
0	08:34:13.327	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 281.25 ms)
0	08:34:14.311	'5002952': previous successful authorization performed from 103.233.11.58
1	08:37:33.758	'5002952': ping failed
1	08:37:33.774	'5002952': datacenter connecting failed [6]
0	08:37:35.368	'5002952': login on RoboForex-Pro-2 through DataCenter Russia (ping: 322.99 ms)
0	08:37:51.337	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Russia (ping: 322.99 ms)
0	08:37:52.275	'5002952': previous successful authorization performed from 103.233.11.58
1	08:41:04.987	'5002952': ping failed
1	08:41:05.003	'5002952': datacenter connecting failed [6]
0	08:41:06.440	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #5 (ping: 362.21 ms)
0	08:41:09.894	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #5 (ping: 362.21 ms)
0	08:41:10.909	'5002952': previous successful authorization performed from 103.233.11.58
1	08:43:37.963	'5002952': datacenter connecting failed [6]
0	08:43:39.385	'5002952': login on RoboForex-Pro-2 through Europe DNS (ping: 277.78 ms)
0	08:43:45.870	'5002952': login datacenter on RoboForex-Pro-2 through Europe DNS (ping: 277.78 ms)
0	08:43:46.729	'5002952': previous successful authorization performed from 103.233.11.58
1	08:46:06.236	'5002952': ping failed
1	08:46:06.251	'5002952': datacenter connecting failed [6]
0	08:46:10.783	'5002952': login on RoboForex-Pro-2 through DataCenter India (ping: 405.86 ms)
0	08:47:11.458	'5002952': login datacenter on RoboForex-Pro-2
0	08:47:20.708	'5002952': login on RoboForex-Pro-2 through DataCenter Brazil (ping: 532.58 ms)
0	08:47:56.303	'5002952': ping to current access point DataCenter Brazil is 526.13 ms
0	08:48:21.601	'5002952': login datacenter on RoboForex-Pro-2
0	08:48:28.352	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 210.63 ms)
0	08:48:30.196	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 210.63 ms)
0	08:48:30.789	'5002952': previous successful authorization performed from 103.233.11.58
0	08:48:52.915	'5002952': ping to current access point DataCenter Singapore is 217.42 ms
1	09:00:10.791	'5002952': ping failed
1	09:00:10.807	'5002952': datacenter connecting failed [6]
0	09:00:12.979	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 279.26 ms)
0	09:00:17.885	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 279.26 ms)
0	09:00:18.792	'5002952': previous successful authorization performed from 103.233.11.58
1	09:00:59.856	MQL5.community: authorization failed
1	09:49:13.477	'5002952': ping failed
1	09:49:13.493	'5002952': datacenter connecting failed [6]
0	09:49:14.790	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 275.19 ms)
0	09:49:17.759	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 275.19 ms)
0	09:49:20.024	'5002952': previous successful authorization performed from 103.233.11.58
0	09:49:52.542	'5002952': auto connecting to a better access point DataCenter Singapore (ping is 210.37 ms)
0	09:49:53.745	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 210.37 ms)
0	09:49:55.885	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 210.37 ms)
0	09:49:56.636	'5002952': previous successful authorization performed from 103.233.11.58
1	15:36:10.758	'5002952': ping failed
1	15:36:10.774	'5002952': datacenter connecting failed [6]
0	15:36:12.196	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 277.46 ms)
0	15:36:16.165	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 277.46 ms)
0	15:36:17.149	'5002952': previous successful authorization performed from 103.233.11.58
0	15:37:03.323	'5002952': auto connecting to a better access point DataCenter Singapore (ping is 211.94 ms)
0	15:37:04.698	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 211.94 ms)
0	15:37:07.339	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 211.94 ms)
0	15:37:08.089	'5002952': previous successful authorization performed from 103.233.11.58
0	16:06:28.594	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 211.94 ms)
0	16:06:31.235	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 211.94 ms)
0	16:06:32.016	'5002952': previous successful authorization performed from 103.233.11.58
1	19:17:26.808	'5002952': datacenter connecting failed [6]
0	19:17:28.120	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 278.36 ms)
0	19:17:31.198	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 278.36 ms)
0	19:17:32.042	'5002952': previous successful authorization performed from 103.233.11.58
0	19:18:02.825	'5002952': auto connecting to a better access point DataCenter Singapore (ping is 210.32 ms)
0	19:18:03.887	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 210.32 ms)
0	19:18:06.044	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 210.32 ms)
0	19:18:06.778	'5002952': previous successful authorization performed from 103.233.11.58
1	20:12:35.026	'5002952': ping failed
1	20:12:35.042	'5002952': datacenter connecting failed [6]
0	20:12:37.183	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 273.75 ms)
0	20:12:46.543	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 273.75 ms)
0	20:12:48.090	'5002952': previous successful authorization performed from 103.233.11.58
0	23:12:04.645	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 273.75 ms)
0	23:12:07.723	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 273.75 ms)
0	23:12:08.770	'5002952': previous successful authorization performed from 103.233.11.58
0	23:12:38.193	'5002952': auto connecting to a better access point DataCenter Singapore (ping is 215.18 ms)
0	23:12:42.319	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 215.18 ms)
0	23:12:47.147	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 215.18 ms)
0	23:12:47.741	'5002952': previous successful authorization performed from 103.233.11.58
1	23:20:39.076	'5002952': datacenter connecting failed [6]
1	23:21:40.610	'5002952': connect failed [Ò»°ã´íÎó]
0	23:21:46.985	'5002952': login on RoboForex-Pro-2 through Europe DNS (ping: 267.48 ms)
0	23:21:49.688	'5002952': login datacenter on RoboForex-Pro-2 through Europe DNS (ping: 267.48 ms)
0	23:21:50.548	'5002952': previous successful authorization performed from 103.233.11.58
1	23:22:57.426	'5002952': datacenter connecting failed [6]
0	23:23:02.051	'5002952': login on RoboForex-Pro-2 through DataCenter India (ping: 404.87 ms)
0	23:23:05.473	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter India (ping: 404.87 ms)
0	23:23:06.520	'5002952': previous successful authorization performed from 103.233.11.58
1	23:31:34.950	'5002952': ping failed
1	23:31:34.966	'5002952': datacenter connecting failed [6]
0	23:31:39.747	'5002952': login on RoboForex-Pro-2 through DataCenter Brazil (ping: 527.59 ms)
0	23:31:44.060	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Brazil (ping: 527.59 ms)
0	23:31:45.279	'5002952': previous successful authorization performed from 103.233.11.58
1	23:34:48.428	'5002952': datacenter connecting failed [6]
0	23:34:50.100	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: n/a)
0	23:34:56.882	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: n/a)
0	23:34:57.897	'5002952': previous successful authorization performed from 103.233.11.58
0	23:35:33.962	'5002952': ping to current access point DataCenter Europe #3 is 280.19 ms
1	23:47:25.901	'5002952': ping failed
1	23:47:25.917	'5002952': datacenter connecting failed [6]
0	23:47:27.058	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 210.50 ms)
0	23:47:32.089	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 210.50 ms)
0	23:47:32.683	'5002952': previous successful authorization performed from 103.233.11.58
1	23:56:02.551	'5002952': datacenter connecting failed [6]
0	23:56:06.864	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 286.15 ms)
0	23:56:19.599	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 286.15 ms)
0	23:56:20.552	'5002952': previous successful authorization performed from 103.233.11.58