1	17:49:35.165	'5002952': datacenter connecting failed [6]
0	17:49:57.588	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 265.06 ms)
0	17:50:00.557	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 265.06 ms)
0	17:50:01.432	'5002952': previous successful authorization performed from 103.233.11.58
0	17:50:25.371	'5002952': auto connecting to a better access point DataCenter Singapore (ping is 199.87 ms)
0	17:50:26.339	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 199.87 ms)
0	17:50:28.386	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 199.87 ms)
0	17:50:29.043	'5002952': previous successful authorization performed from 103.233.11.58
1	18:09:38.425	'5002952': datacenter connecting failed [6]
0	18:09:55.972	'5002952': login on RoboForex-Pro-2 through DataCenter India (ping: 214.09 ms)
0	18:11:53.837	'5002952': login on RoboForex-Pro-2 through DataCenter Russia (ping: 275.78 ms)
0	18:13:01.216	'5002952': login datacenter on RoboForex-Pro-2
0	18:13:46.499	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #5 (ping: 294.52 ms)
0	18:14:54.268	'5002952': login on RoboForex-Pro-2 through Europe DNS (ping: 203.58 ms)
0	18:15:08.409	'5002952': ping to current access point Europe DNS is n/a
1	18:16:15.412	'5002952': datacenter connecting failed [6]
0	18:17:10.540	'5002952': login on RoboForex-Pro-2 through DataCenter Russia (ping: 314.02 ms)
0	18:17:46.401	'5002952': ping to current access point DataCenter Russia is n/a
0	18:18:20.496	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 200.11 ms)
1	18:19:42.422	'5002952': datacenter connecting failed [6]
0	18:19:50.907	'5002952': login on RoboForex-Pro-2 through DataCenter India (ping: 209.79 ms)
0	18:20:54.925	'5002952': login datacenter on RoboForex-Pro-2
1	18:21:19.380	'5002952': connect failed [没有连接]
0	18:21:33.396	'5002952': ping to current access point DataCenter Hong Kong is n/a
0	18:22:26.211	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 257.39 ms)
0	18:22:28.102	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 257.39 ms)
0	18:22:28.664	'5002952': previous successful authorization performed from 103.233.11.58
1	20:42:14.698	'5002952': ping failed
1	20:42:14.714	'5002952': datacenter connecting failed [6]
0	20:42:18.980	'5002952': login on RoboForex-Pro-2 through DataCenter India (ping: 267.75 ms)
0	20:43:20.092	'5002952': login datacenter on RoboForex-Pro-2
0	20:43:27.061	'5002952': login on RoboForex-Pro-2 through DataCenter Russia (ping: 323.92 ms)
0	20:44:31.408	'5002952': auto connecting to a better access point DataCenter India (ping is 268.14 ms)
1	20:44:31.533	'5002952': datacenter connecting failed [6]
0	20:45:23.535	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 277.42 ms)
0	20:46:24.929	'5002952': login datacenter on RoboForex-Pro-2
0	20:47:21.760	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #5 (ping: 357.51 ms)
0	20:48:20.403	'5002952': ping to current access point DataCenter Europe #5 is n/a
0	20:48:28.560	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 254.97 ms)
0	20:48:35.154	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 254.97 ms)
0	20:48:43.217	'5002952': previous successful authorization performed from 103.233.11.58
1	20:50:36.378	'5002952': ping failed
1	20:50:36.394	'5002952': datacenter connecting failed [6]
0	20:50:37.581	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 274.36 ms)
0	20:50:40.488	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 274.36 ms)
0	20:50:41.269	'5002952': previous successful authorization performed from 103.233.11.58
1	21:58:04.678	'5002952': ping failed
1	21:58:05.459	'5002952': connect failed [没有连接]
0	21:58:17.663	'5002952': login on RoboForex-Pro-2 through DataCenter Russia (ping: 314.90 ms)
0	21:58:20.335	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Russia (ping: 314.90 ms)
0	21:58:21.257	'5002952': previous successful authorization performed from 103.233.11.58
0	21:59:15.150	'5002952': auto connecting to a better access point DataCenter India (ping is 210.62 ms)
0	21:59:16.087	'5002952': login on RoboForex-Pro-2 through DataCenter India (ping: 210.62 ms)
0	21:59:18.134	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter India (ping: 210.62 ms)
0	21:59:18.837	'5002952': previous successful authorization performed from 103.233.11.58
1	23:38:57.540	'5002952': datacenter connecting failed [6]
0	23:38:58.650	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 213.54 ms)
0	23:40:23.966	'5002952': login datacenter on RoboForex-Pro-2
0	23:40:51.702	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 267.60 ms)
0	23:42:08.533	'5002952': auto connecting to a better access point DataCenter Europe #4 (ping is 270.57 ms)
1	23:42:08.658	'5002952': datacenter connecting failed [6]
0	23:43:03.458	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 270.57 ms)
1	23:45:09.526	'5002952': connect failed [没有连接]
0	23:46:57.688	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: n/a)
1	23:48:19.535	'5002952': datacenter connecting failed [6]
1	23:48:25.864	'5002952': connect failed [没有连接]
0	23:48:35.083	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #5 (ping: n/a)
0	23:50:03.103	'5002952': login on RoboForex-Pro-2 through DataCenter India (ping: n/a)
0	23:50:14.525	'5002952': ping to current access point DataCenter India is n/a
1	23:51:24.544	'5002952': datacenter connecting failed [6]
1	23:52:30.531	'5002952': connect failed [没有连接]
0	23:53:27.534	'5002952': ping to current access point DataCenter Russia is 316.89 ms
0	23:53:42.582	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 267.21 ms)
0	23:53:44.504	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 267.21 ms)
0	23:53:45.129	'5002952': previous successful authorization performed from 103.233.11.58