1	04:20:09.487	'5002952': datacenter connecting failed [6]
0	04:20:31.473	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 207.09 ms)
0	04:20:33.395	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 207.09 ms)
0	04:20:33.973	'5002952': previous successful authorization performed from 103.233.11.58
0	04:21:07.209	'5002952': auto connecting to a better access point DataCenter India (ping is 228.38 ms)
0	04:21:08.100	'5002952': login on RoboForex-Pro-2 through DataCenter India (ping: 228.38 ms)
0	04:21:09.975	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter India (ping: 228.38 ms)
0	04:21:10.600	'5002952': previous successful authorization performed from 103.233.11.58
0	12:08:31.941	'5002952': login on RoboForex-Pro-2 through DataCenter India (ping: 228.38 ms)
0	12:08:34.535	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter India (ping: 228.38 ms)
0	12:08:35.207	'5002952': previous successful authorization performed from 103.233.11.58
0	12:09:05.958	'5002952': ping to current access point DataCenter India is 227.24 ms
0	12:46:35.752	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 265.79 ms)
0	12:46:40.955	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 265.79 ms)
0	12:46:41.690	'5002952': previous successful authorization performed from 103.233.11.58
0	13:33:35.166	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 265.79 ms)
0	13:33:40.120	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 265.79 ms)
0	13:33:40.870	'5002952': previous successful authorization performed from 103.233.11.58
0	13:34:08.965	'5002952': auto connecting to a better access point DataCenter India (ping is 227.21 ms)
0	13:34:10.074	'5002952': login on RoboForex-Pro-2 through DataCenter India (ping: 227.21 ms)
0	13:34:12.028	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter India (ping: 227.21 ms)
0	13:34:12.700	'5002952': previous successful authorization performed from 103.233.11.58
0	13:56:47.842	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 281.59 ms)
0	13:56:52.639	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 281.59 ms)
0	13:56:53.483	'5002952': previous successful authorization performed from 103.233.11.58
0	14:12:33.918	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 281.59 ms)
0	14:12:38.293	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 281.59 ms)
0	14:12:39.137	'5002952': previous successful authorization performed from 103.233.11.58
1	14:17:56.370	'5002952': datacenter connecting failed [6]
0	14:17:57.667	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 281.59 ms)
0	14:18:02.027	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 281.59 ms)
0	14:18:02.980	'5002952': previous successful authorization performed from 103.233.11.58
1	14:24:42.608	'5002952': ping failed
1	14:24:42.624	'5002952': datacenter connecting failed [6]
0	14:25:04.859	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 285.16 ms)
0	14:25:09.578	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 285.16 ms)
0	14:25:10.485	'5002952': previous successful authorization performed from 103.233.11.58
1	14:27:10.772	'5002952': ping failed
1	14:28:13.462	'5002952': connect failed [没有连接]
0	14:29:25.590	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: n/a)
0	14:29:30.263	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: n/a)
0	14:29:31.169	'5002952': previous successful authorization performed from 103.233.11.58
0	14:30:25.468	'5002952': ping to current access point DataCenter Europe #3 is 295.42 ms
0	14:30:50.219	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 295.42 ms)
0	14:30:55.501	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 295.42 ms)
0	14:30:58.689	'5002952': previous successful authorization performed from 103.233.11.58
0	14:34:26.308	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 295.42 ms)
0	14:34:30.980	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 295.42 ms)
0	14:34:31.871	'5002952': previous successful authorization performed from 103.233.11.58
1	14:35:31.311	'5002952': ping failed
1	14:35:31.327	'5002952': datacenter connecting failed [6]
0	14:35:41.311	'5002952': login on RoboForex-Pro-2 through DataCenter India (ping: 226.38 ms)
0	14:35:44.108	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter India (ping: 226.38 ms)
0	14:35:44.780	'5002952': previous successful authorization performed from 103.233.11.58
0	14:36:40.049	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 262.43 ms)
0	14:36:45.080	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 262.43 ms)
0	14:36:45.986	'5002952': previous successful authorization performed from 103.233.11.58
1	14:37:25.144	'5002952': ping failed
1	14:37:25.160	'5002952': datacenter connecting failed [6]
0	14:38:17.475	'5002952': login on RoboForex-Pro-2 through DataCenter Russia (ping: 324.15 ms)
0	14:38:20.194	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Russia (ping: 324.15 ms)
0	14:38:21.210	'5002952': previous successful authorization performed from 103.233.11.58
1	14:38:53.649	'5002952': datacenter connecting failed [6]
1	14:39:03.524	MQL5.community: authorization failed
1	14:39:54.589	'5002952': connect failed [没有连接]
0	14:40:09.183	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: n/a)
0	14:40:12.277	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: n/a)
0	14:40:14.012	'5002952': previous successful authorization performed from 103.233.11.58
0	14:40:52.029	'5002952': ping to current access point DataCenter Europe #3 is 285.68 ms
1	14:42:13.377	'5002952': ping failed
1	14:42:13.392	'5002952': datacenter connecting failed [6]
0	14:42:14.549	'5002952': login on RoboForex-Pro-2 through DataCenter India (ping: 226.61 ms)
0	14:42:16.486	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter India (ping: 226.61 ms)
0	14:42:17.158	'5002952': previous successful authorization performed from 103.233.11.58
1	14:43:16.630	'5002952': ping failed
1	14:43:16.645	'5002952': datacenter connecting failed [6]
0	14:43:17.911	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 275.90 ms)
0	14:43:21.021	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 275.90 ms)
0	14:43:21.896	'5002952': previous successful authorization performed from 103.233.11.58
1	14:44:41.368	'5002952': ping failed
1	14:44:41.384	'5002952': datacenter connecting failed [6]
0	14:45:03.729	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #5 (ping: 353.16 ms)
0	14:45:07.041	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #5 (ping: 353.16 ms)
0	14:45:08.166	'5002952': previous successful authorization performed from 103.233.11.58
1	14:48:46.442	'5002952': datacenter connecting failed [6]
0	14:49:08.537	'5002952': login on RoboForex-Pro-2 through Europe DNS (ping: 265.20 ms)
0	14:49:11.115	'5002952': login datacenter on RoboForex-Pro-2 through Europe DNS (ping: 265.20 ms)
0	14:49:12.459	'5002952': previous successful authorization performed from 103.233.11.58