1	00:45:53.868	'5002952': ping failed
1	00:45:53.883	'5002952': datacenter connecting failed [6]
0	00:45:58.133	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 278.96 ms)
0	00:46:01.227	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 278.96 ms)
0	00:46:03.696	'5002952': previous successful authorization performed from 103.233.11.58
0	00:46:33.948	'5002952': auto connecting to a better access point DataCenter Singapore (ping is 206.60 ms)
0	00:46:35.213	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 206.60 ms)
0	00:46:37.917	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 206.60 ms)
0	00:46:38.713	'5002952': previous successful authorization performed from 103.233.11.58
1	01:11:39.144	'5002952': ping failed
1	01:11:39.159	'5002952': datacenter connecting failed [6]
0	01:11:40.363	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 264.78 ms)
0	01:11:43.800	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 264.78 ms)
0	01:11:44.644	'5002952': previous successful authorization performed from 103.233.11.58
1	02:10:09.513	'5002952': ping failed
1	02:10:09.528	'5002952': datacenter connecting failed [6]
0	02:10:31.826	'5002952': login on RoboForex-Pro-2 through DataCenter Russia (ping: 302.02 ms)
0	02:10:34.545	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Russia (ping: 302.02 ms)
0	02:10:35.483	'5002952': previous successful authorization performed from 103.233.11.58
1	02:11:09.203	MQL5.community: authorization failed
0	02:11:19.125	'5002952': auto connecting to a better access point DataCenter Singapore (ping is 206.78 ms)
0	02:11:20.266	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 206.78 ms)
0	02:11:22.110	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 206.78 ms)
0	02:11:22.813	'5002952': previous successful authorization performed from 103.233.11.58
1	10:04:04.294	'5002952': ping failed
1	10:04:04.310	'5002952': datacenter connecting failed [6]
0	10:04:05.513	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 279.16 ms)
0	10:04:08.451	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 279.16 ms)
0	10:04:09.373	'5002952': previous successful authorization performed from 103.233.11.58
0	10:04:37.265	'5002952': auto connecting to a better access point DataCenter Singapore (ping is 205.14 ms)
0	10:04:38.359	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 205.14 ms)
0	10:04:40.171	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 205.14 ms)
0	10:04:40.796	'5002952': previous successful authorization performed from 103.233.11.58
1	10:31:41.482	'5002952': ping failed
1	10:31:41.498	'5002952': datacenter connecting failed [6]
0	10:31:45.732	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 266.53 ms)
0	10:31:48.701	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 266.53 ms)
0	10:31:49.545	'5002952': previous successful authorization performed from 103.233.11.58
1	11:56:52.943	'5002952': ping failed
1	11:56:52.958	'5002952': datacenter connecting failed [6]
0	11:56:54.161	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 269.38 ms)
0	11:56:57.911	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 269.38 ms)
0	11:56:58.802	'5002952': previous successful authorization performed from 103.233.11.58
0	11:57:28.132	'5002952': auto connecting to a better access point DataCenter Singapore (ping is 202.10 ms)
0	11:57:32.444	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 202.10 ms)
0	11:57:35.101	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 202.10 ms)
0	11:57:35.898	'5002952': previous successful authorization performed from 103.233.11.58
1	13:27:59.373	'5002952': ping failed
1	13:27:59.388	'5002952': datacenter connecting failed [6]
0	13:28:00.998	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 266.96 ms)
0	13:28:05.311	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 266.96 ms)
0	13:28:06.404	'5002952': previous successful authorization performed from 103.233.11.58
0	13:28:51.500	'5002952': auto connecting to a better access point DataCenter Singapore (ping is 207.02 ms)
0	13:28:52.657	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 207.02 ms)
0	13:28:55.969	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 207.02 ms)
0	13:28:56.766	'5002952': previous successful authorization performed from 103.233.11.58
1	14:54:32.712	'5002952': ping failed
1	14:54:32.728	'5002952': datacenter connecting failed [6]
0	14:54:33.978	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 285.91 ms)
0	14:54:36.915	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 285.91 ms)
0	14:54:37.806	'5002952': previous successful authorization performed from 103.233.11.58
0	14:55:07.495	'5002952': auto connecting to a better access point DataCenter Singapore (ping is 206.85 ms)
0	14:55:08.667	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 206.85 ms)
0	14:55:11.354	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 206.85 ms)
0	14:55:12.136	'5002952': previous successful authorization performed from 103.233.11.58
1	15:03:11.783	'5002952': ping failed
1	15:03:11.799	'5002952': datacenter connecting failed [6]
0	15:03:13.018	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 269.58 ms)
0	15:03:16.159	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 269.58 ms)
0	15:03:17.034	'5002952': previous successful authorization performed from 103.233.11.58
0	15:59:52.241	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 269.58 ms)
0	15:59:55.382	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 269.58 ms)
0	15:59:56.257	'5002952': previous successful authorization performed from 103.233.11.58
0	16:00:34.274	'5002952': auto connecting to a better access point DataCenter Singapore (ping is 201.95 ms)
0	16:00:35.227	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 201.95 ms)
0	16:00:40.087	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 201.95 ms)
0	16:00:40.696	'5002952': previous successful authorization performed from 103.233.11.58
1	19:09:49.811	'5002952': ping failed
0	19:09:50.874	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 201.95 ms)
0	19:09:52.764	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 201.95 ms)
0	19:09:53.358	'5002952': previous successful authorization performed from 103.233.11.58
0	19:10:23.500	'5002952': ping to current access point DataCenter Singapore is 202.82 ms
1	19:13:52.994	'5002952': ping failed
1	19:13:53.010	'5002952': datacenter connecting failed [6]
0	19:14:00.354	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 267.56 ms)
0	19:14:09.120	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 267.56 ms)
0	19:14:10.011	'5002952': previous successful authorization performed from 103.233.11.58
1	19:44:42.894	'5002952': datacenter connecting failed [6]
0	19:44:44.129	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 272.46 ms)
0	19:44:51.129	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 272.46 ms)
0	19:44:52.004	'5002952': previous successful authorization performed from 103.233.11.58
1	20:07:32.600	'5002952': ping failed
0	20:07:33.131	'5002952': login datacenter on RoboForex-Pro-2
0	20:07:34.709	'5002952': login on RoboForex-Pro-2 through DataCenter Russia (ping: 305.88 ms)
0	20:07:37.350	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Russia (ping: 305.88 ms)
0	20:07:38.256	'5002952': previous successful authorization performed from 103.233.11.58