1	00:08:48.077	'5002952': ping failed
1	00:08:48.093	'5002952': datacenter connecting failed [6]
0	00:08:58.124	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 213.92 ms)
0	00:09:03.109	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 213.92 ms)
0	00:09:04.546	'5002952': previous successful authorization performed from 103.233.11.57
0	00:09:16.219	'5002952': auto connecting to a better access point DataCenter Hong Kong (ping is 196.57 ms)
0	00:09:17.219	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.57 ms)
0	00:09:18.766	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.57 ms)
0	00:09:19.344	'5002952': previous successful authorization performed from 103.233.11.57
0	00:35:14.996	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.57 ms)
0	00:35:30.231	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.57 ms)
0	00:35:30.746	'5002952': previous successful authorization performed from 103.233.11.57
1	01:01:31.477	'5002952': ping failed
1	01:01:31.492	'5002952': datacenter connecting failed [6]
0	01:01:53.493	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 208.53 ms)
0	01:01:58.868	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 208.53 ms)
0	01:01:59.603	'5002952': previous successful authorization performed from 103.233.11.57
0	01:28:22.959	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 208.53 ms)
0	01:28:24.787	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 208.53 ms)
0	01:28:26.022	'5002952': previous successful authorization performed from 103.233.11.57
0	01:28:51.648	'5002952': auto connecting to a better access point DataCenter Hong Kong (ping is 196.91 ms)
0	01:28:52.585	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.91 ms)
0	01:28:54.054	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.91 ms)
0	01:28:54.570	'5002952': previous successful authorization performed from 103.233.11.57
1	01:54:36.002	'5002952': ping failed
0	01:54:39.924	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.91 ms)
0	01:54:54.706	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.91 ms)
0	01:54:55.222	'5002952': previous successful authorization performed from 103.233.11.57
1	02:20:56.639	'5002952': ping failed
0	02:21:18.750	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 211.19 ms)
0	02:21:21.469	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 211.19 ms)
0	02:21:22.203	'5002952': previous successful authorization performed from 103.233.11.57
1	02:47:42.903	'5002952': ping failed
1	02:47:42.918	'5002952': datacenter connecting failed [6]
0	02:47:46.997	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.91 ms)
0	02:47:48.497	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.91 ms)
0	02:47:49.044	'5002952': previous successful authorization performed from 103.233.11.57
0	02:48:01.669	'5002952': ping to current access point DataCenter Hong Kong is 196.44 ms
0	03:13:45.992	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.44 ms)
0	03:14:10.931	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.44 ms)
0	03:14:17.181	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.44 ms)
0	03:14:17.681	'5002952': previous successful authorization performed from 103.233.11.57
1	03:40:52.209	'5002952': ping failed
1	03:40:52.225	'5002952': datacenter connecting failed [6]
0	03:40:53.303	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 211.13 ms)
0	03:41:00.725	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 211.13 ms)
0	03:41:01.429	'5002952': previous successful authorization performed from 103.233.11.57
1	04:07:22.160	'5002952': ping failed
1	04:07:22.160	'5002952': datacenter connecting failed [6]
0	04:07:26.207	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 212.64 ms)
0	04:07:28.129	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 212.64 ms)
0	04:07:28.769	'5002952': previous successful authorization performed from 103.233.11.57
0	04:07:40.848	'5002952': auto connecting to a better access point DataCenter Hong Kong (ping is 196.48 ms)
0	04:07:41.864	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.48 ms)
0	04:07:43.348	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.48 ms)
0	04:07:43.817	'5002952': previous successful authorization performed from 103.233.11.57
1	04:33:25.202	'5002952': ping failed
0	04:33:50.235	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 200.92 ms)
0	04:33:55.751	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 200.92 ms)
0	04:33:56.454	'5002952': previous successful authorization performed from 103.233.11.57
0	05:00:24.091	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 200.92 ms)
0	05:00:25.998	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 200.92 ms)
0	05:00:26.732	'5002952': previous successful authorization performed from 103.233.11.57
1	05:26:47.432	'5002952': ping failed
1	05:26:47.447	'5002952': datacenter connecting failed [6]
0	05:26:51.510	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.48 ms)
0	05:26:53.323	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.48 ms)
0	05:26:53.807	'5002952': previous successful authorization performed from 103.233.11.57
0	05:27:06.933	'5002952': ping to current access point DataCenter Hong Kong is 196.52 ms
0	05:53:23.648	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 210.89 ms)
0	05:53:25.492	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 210.89 ms)
0	05:53:26.164	'5002952': previous successful authorization performed from 103.233.11.57
1	06:46:08.157	'5002952': ping failed
1	06:46:08.172	'5002952': datacenter connecting failed [6]
0	06:46:12.266	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.52 ms)
0	06:46:18.907	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.52 ms)
0	06:46:19.485	'5002952': previous successful authorization performed from 103.233.11.57
0	06:46:31.955	'5002952': ping to current access point DataCenter Hong Kong is 196.37 ms
1	07:38:42.150	'5002952': ping failed
0	07:39:04.260	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 211.36 ms)
0	07:39:14.260	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 211.36 ms)
0	07:39:15.011	'5002952': previous successful authorization performed from 103.233.11.57
1	08:05:35.710	'5002952': ping failed
1	08:05:35.726	'5002952': datacenter connecting failed [6]
0	08:05:45.804	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.37 ms)
0	08:05:47.289	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.37 ms)
0	08:05:47.851	'5002952': previous successful authorization performed from 103.233.11.57
0	08:06:00.602	'5002952': ping to current access point DataCenter Hong Kong is 196.27 ms
1	08:31:48.503	'5002952': ping failed
1	08:31:48.519	'5002952': datacenter connecting failed [6]
0	08:32:10.676	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 205.02 ms)
0	08:32:12.567	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 205.02 ms)
0	08:32:13.301	'5002952': previous successful authorization performed from 103.233.11.57
0	09:25:10.077	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 205.02 ms)
0	09:25:11.920	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 205.02 ms)
0	09:25:12.639	'5002952': previous successful authorization performed from 103.233.11.57
0	09:25:26.890	'5002952': auto connecting to a better access point DataCenter Europe #3 (ping is 206.87 ms)
0	09:25:28.546	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 206.87 ms)
0	09:25:31.140	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 206.87 ms)
0	09:25:31.859	'5002952': previous successful authorization performed from 103.233.11.57
1	09:51:12.541	'5002952': ping failed
1	09:51:12.557	'5002952': datacenter connecting failed [6]
0	09:51:37.652	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 203.02 ms)
0	09:51:39.574	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 203.02 ms)
0	09:51:40.433	'5002952': previous successful authorization performed from 103.233.11.57
0	10:18:04.414	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 203.02 ms)
0	10:18:06.899	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 203.02 ms)
0	10:18:07.633	'5002952': previous successful authorization performed from 103.233.11.57
0	10:44:44.224	'5002952': login on RoboForex-Pro-2 through DataCenter Russia (ping: 235.43 ms)
0	10:44:46.271	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Russia (ping: 235.43 ms)
0	10:44:47.005	'5002952': previous successful authorization performed from 103.233.11.57
0	10:44:59.131	'5002952': auto connecting to a better access point DataCenter Hong Kong (ping is 196.36 ms)
0	10:45:00.100	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.36 ms)
0	10:45:01.569	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.36 ms)
0	10:45:02.037	'5002952': previous successful authorization performed from 103.233.11.57
1	11:10:43.407	'5002952': ping failed
0	11:11:08.455	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.36 ms)
0	11:11:09.955	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.36 ms)
0	11:11:10.424	'5002952': previous successful authorization performed from 103.233.11.57
1	11:37:11.826	'5002952': ping failed
0	11:37:36.827	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.36 ms)
0	11:37:38.265	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.36 ms)
0	11:37:38.827	'5002952': previous successful authorization performed from 103.233.11.57
1	12:30:00.773	'5002952': ping failed
1	12:30:00.788	'5002952': datacenter connecting failed [6]
0	12:30:22.899	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 202.25 ms)
0	12:30:29.790	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 202.25 ms)
0	12:30:30.462	'5002952': previous successful authorization performed from 103.233.11.57
0	12:30:42.665	'5002952': auto connecting to a better access point DataCenter Hong Kong (ping is 196.63 ms)
0	12:30:43.618	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.63 ms)
0	12:30:45.103	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.63 ms)
0	12:30:45.619	'5002952': previous successful authorization performed from 103.233.11.57
1	12:56:26.301	'5002952': ping failed
1	12:56:26.316	'5002952': datacenter connecting failed [6]
0	12:56:31.535	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 211.97 ms)
0	12:57:38.289	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 213.19 ms)
0	12:57:40.148	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 213.19 ms)
0	12:57:40.836	'5002952': previous successful authorization performed from 103.233.11.57
0	13:49:59.375	'5002952': login on RoboForex-Pro-2 through DataCenter Russia (ping: 231.37 ms)
0	13:50:01.453	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Russia (ping: 231.37 ms)
0	13:50:02.172	'5002952': previous successful authorization performed from 103.233.11.57
0	13:50:14.313	'5002952': auto connecting to a better access point DataCenter Hong Kong (ping is 196.60 ms)
0	13:50:15.235	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.60 ms)
0	13:50:16.750	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.60 ms)
0	13:50:17.266	'5002952': previous successful authorization performed from 103.233.11.57
1	14:16:17.980	'5002952': ping failed
1	14:16:17.996	'5002952': datacenter connecting failed [6]
0	14:16:25.168	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 213.75 ms)
0	14:16:27.637	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 213.75 ms)
0	14:16:28.340	'5002952': previous successful authorization performed from 103.233.11.57
1	15:08:50.989	'5002952': ping failed
0	15:09:22.053	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 205.68 ms)
0	15:09:24.522	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 205.68 ms)
0	15:09:26.069	'5002952': previous successful authorization performed from 103.233.11.57
0	15:09:42.257	'5002952': auto connecting to a better access point DataCenter Hong Kong (ping is 196.56 ms)
0	15:09:43.273	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.56 ms)
0	15:09:44.757	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.56 ms)
0	15:09:45.273	'5002952': previous successful authorization performed from 103.233.11.57
1	15:35:25.955	'5002952': ping failed
1	15:35:25.970	'5002952': datacenter connecting failed [6]
0	15:35:48.143	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 202.44 ms)
0	15:35:50.081	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 202.44 ms)
0	15:35:51.362	'5002952': previous successful authorization performed from 103.233.11.57
1	16:02:11.515	'5002952': ping failed
1	16:02:11.593	'5002952': datacenter connecting failed [6]
0	16:02:15.656	'5002952': login on RoboForex-Pro-2 through DataCenter Russia (ping: 231.41 ms)
0	16:02:17.734	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Russia (ping: 231.41 ms)
0	16:02:18.453	'5002952': previous successful authorization performed from 103.233.11.57
0	16:28:54.966	'5002952': login on RoboForex-Pro-2 through DataCenter India (ping: 227.31 ms)
0	16:28:56.607	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter India (ping: 227.31 ms)
0	16:28:57.232	'5002952': previous successful authorization performed from 103.233.11.57
0	16:29:09.607	'5002952': auto connecting to a better access point DataCenter Hong Kong (ping is 196.47 ms)
0	16:29:10.623	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.47 ms)
0	16:29:12.060	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.47 ms)
0	16:29:12.529	'5002952': previous successful authorization performed from 103.233.11.57