1 02:41:01.183 '5002952': datacenter connecting failed [6] 1 02:41:01.229 '5002952': connect failed [一般错误] 0 02:43:22.386 '5002952': login on RoboForex-Pro-2 through Singapore (ping: n/a) 0 02:43:27.292 '5002952': login datacenter on RoboForex-Pro-2 through Singapore (ping: n/a) 0 02:43:27.901 '5002952': previous successful authorization performed from 101.36.110.43 0 02:43:41.745 '5002952': auto connecting to a better access point Germany (ping is 202.73 ms) 0 02:43:42.292 '5002952': login on RoboForex-Pro-2 through Germany (ping: 202.73 ms) 0 02:43:43.964 '5002952': login datacenter on RoboForex-Pro-2 through Germany (ping: 202.73 ms) 0 02:43:44.604 '5002952': previous successful authorization performed from 101.36.110.43 1 05:26:25.230 '5002952': connect failed [没有连接] 0 05:28:18.746 '5002952': login on RoboForex-Pro-2 through Germany (ping: n/a) 0 05:28:22.152 '5002952': login datacenter on RoboForex-Pro-2 through Germany (ping: n/a) 0 05:28:22.824 '5002952': previous successful authorization performed from 101.36.110.43 0 05:28:39.387 '5002952': ping to current access point Germany is 203.29 ms 1 14:25:07.642 '5002952': ping failed 1 14:25:07.658 '5002952': datacenter connecting failed [6] 0 14:25:08.283 '5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 190.14 ms) 0 14:25:09.689 '5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 190.14 ms) 0 14:25:10.158 '5002952': previous successful authorization performed from 101.36.110.43 0 14:25:24.424 '5002952': auto connecting to a better access point Germany (ping is 199.57 ms) 0 14:25:25.096 '5002952': login on RoboForex-Pro-2 through Germany (ping: 199.57 ms) 0 14:25:26.689 '5002952': login datacenter on RoboForex-Pro-2 through Germany (ping: 199.57 ms) 0 14:25:27.439 '5002952': previous successful authorization performed from 101.36.110.43 0 15:31:14.388 '5002952': login on RoboForex-Pro-2 through Germany (ping: 199.57 ms) 0 15:31:16.076 '5002952': login datacenter on RoboForex-Pro-2 through Germany (ping: 199.57 ms) 0 15:31:16.920 '5002952': previous successful authorization performed from 101.36.110.43 0 15:31:33.467 '5002952': ping to current access point Germany is 202.01 ms 1 16:04:17.829 '5002952': ping failed 1 16:04:17.829 '5002952': datacenter connecting failed [6] 0 16:04:18.860 '5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 190.50 ms) 0 16:04:20.313 '5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 190.50 ms) 0 16:04:20.907 '5002952': previous successful authorization performed from 101.36.110.43 1 17:58:25.652 '5002952': ping failed 1 17:58:25.667 '5002952': datacenter connecting failed [6] 1 17:59:30.214 '5002952': connect failed [没有连接] 0 18:25:30.036 '5002952': login on RoboForex-Pro-2 through Czech Republic (ping: n/a) 0 18:25:32.036 '5002952': login datacenter on RoboForex-Pro-2 through Czech Republic (ping: n/a) 0 18:25:32.958 '5002952': previous successful authorization performed from 101.36.110.43 0 18:25:54.380 '5002952': auto connecting to a better access point Hong Kong (ping is 190.26 ms) 0 18:25:55.099 '5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 190.26 ms) 0 18:25:56.474 '5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 190.26 ms) 0 18:25:57.099 '5002952': previous successful authorization performed from 101.36.110.43 1 19:50:01.097 '5002952': ping failed 0 19:50:02.831 '5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 190.26 ms) 0 19:50:40.191 '5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 190.26 ms) 0 19:50:40.987 '5002952': previous successful authorization performed from 101.36.110.43 0 19:50:58.644 '5002952': auto connecting to a better access point India (ping is 252.35 ms) 0 19:50:59.409 '5002952': login on RoboForex-Pro-2 through India (ping: 252.35 ms) 0 19:51:01.097 '5002952': login datacenter on RoboForex-Pro-2 through India (ping: 252.35 ms) 0 19:51:01.878 '5002952': previous successful authorization performed from 101.36.110.43 1 19:58:21.504 '5002952': ping failed 1 19:58:21.504 '5002952': datacenter connecting failed [6] 0 19:59:10.942 '5002952': login on RoboForex-Pro-2 through Germany (ping: 278.96 ms) 0 20:00:17.113 '5002952': login on RoboForex-Pro-2 through Russia (ping: 278.25 ms) 0 20:00:20.113 '5002952': login datacenter on RoboForex-Pro-2 through Russia (ping: 278.25 ms) 0 20:00:20.988 '5002952': previous successful authorization performed from 101.36.110.43 1 20:14:01.035 '5002952': ping failed 1 20:14:01.051 '5002952': datacenter connecting failed [6] 0 20:14:11.457 '5002952': login on RoboForex-Pro-2 through Finland (ping: 306.77 ms) 0 20:14:14.082 '5002952': login datacenter on RoboForex-Pro-2 through Finland (ping: 306.77 ms) 0 20:14:15.160 '5002952': previous successful authorization performed from 101.36.110.43 1 20:23:39.463 '5002952': datacenter connecting failed [6] 0 20:24:01.104 '5002952': login on RoboForex-Pro-2 through Singapore (ping: 277.56 ms) 0 20:24:02.526 '5002952': login datacenter on RoboForex-Pro-2 through Singapore (ping: 277.56 ms) 0 20:24:03.010 '5002952': previous successful authorization performed from 101.36.110.43 1 20:25:42.666 '5002952': ping failed 1 20:25:42.682 '5002952': datacenter connecting failed [6] 0 20:25:55.822 '5002952': login on RoboForex-Pro-2 through Finland (ping: 306.77 ms) 0 20:26:01.744 '5002952': login datacenter on RoboForex-Pro-2 through Finland (ping: 306.77 ms) 0 20:26:02.885 '5002952': previous successful authorization performed from 101.36.110.43 1 20:29:28.229 '5002952': datacenter connecting failed [6] 0 20:29:28.885 '5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 278.46 ms) 0 20:29:30.213 '5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 278.46 ms) 0 20:29:30.854 '5002952': previous successful authorization performed from 101.36.110.43 1 20:31:30.307 '5002952': ping failed 1 20:31:30.322 '5002952': datacenter connecting failed [6] 0 20:31:40.463 '5002952': login on RoboForex-Pro-2 through Czech Republic (ping: 300.49 ms) 0 20:31:43.604 '5002952': login datacenter on RoboForex-Pro-2 through Czech Republic (ping: 300.49 ms) 0 20:31:46.010 '5002952': previous successful authorization performed from 101.36.110.43 0 20:37:24.369 '5002952': login on RoboForex-Pro-2 through Czech Republic (ping: 300.49 ms) 0 20:37:26.213 '5002952': login datacenter on RoboForex-Pro-2 through Czech Republic (ping: 300.49 ms) 0 20:37:27.119 '5002952': previous successful authorization performed from 101.36.110.43 1 21:12:43.313 '5002952': datacenter connecting failed [6] 0 21:12:47.345 '5002952': login on RoboForex-Pro-2 through Czech Republic (ping: 300.49 ms) 0 21:12:52.970 '5002952': login datacenter on RoboForex-Pro-2 through Czech Republic (ping: 300.49 ms) 0 21:12:53.907 '5002952': previous successful authorization performed from 101.36.110.43 0 21:14:30.095 '5002952': auto connecting to a better access point Hong Kong (ping is 220.88 ms) 0 21:14:30.907 '5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 220.88 ms) 0 21:14:32.345 '5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 220.88 ms) 0 21:14:33.532 '5002952': previous successful authorization performed from 101.36.110.43 0 21:44:45.310 '5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 220.88 ms) 0 21:44:46.732 '5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 220.88 ms) 0 21:44:47.419 '5002952': previous successful authorization performed from 101.36.110.43 0 22:07:48.916 '5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 220.88 ms) 1 22:08:12.478 '5002952': datacenter connecting failed [6] 0 22:08:13.119 '5002952': previous successful authorization performed from 101.36.110.43 1 22:09:53.228 '5002952': ping failed 0 22:09:54.244 '5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 220.88 ms) 0 22:09:55.666 '5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 220.88 ms) 0 22:09:56.244 '5002952': previous successful authorization performed from 101.36.110.43 0 22:52:30.603 '5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 220.88 ms) 0 22:52:32.056 '5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 220.88 ms) 0 22:52:32.760 '5002952': previous successful authorization performed from 101.36.110.43 0 22:54:24.250 '5002952': auto connecting to a better access point Singapore (ping is 211.15 ms) 0 22:54:24.984 '5002952': login on RoboForex-Pro-2 through Singapore (ping: 211.15 ms) 0 22:54:26.390 '5002952': login datacenter on RoboForex-Pro-2 through Singapore (ping: 211.15 ms) 0 22:54:27.094 '5002952': previous successful authorization performed from 101.36.110.43