1	17:16:28.249	'5002952': connect failed [ûÓÐÁ¬½Ó]
0	17:17:01.812	'5002952': login on RoboForex-Pro-2 through Netherlands (ping: 196.82 ms)
0	17:17:03.546	'5002952': login datacenter on RoboForex-Pro-2 through Netherlands (ping: 196.82 ms)
0	17:17:19.296	'5002952': login on RoboForex-Pro-2 through Netherlands (ping: 196.82 ms)
0	17:17:21.281	'5002952': login datacenter on RoboForex-Pro-2 through Netherlands (ping: 196.82 ms)
0	17:17:22.077	'5002952': previous successful authorization performed from 101.36.110.43
0	17:17:38.421	'5002952': auto connecting to a better access point Hong Kong (ping is 203.03 ms)
0	17:17:39.171	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 203.03 ms)
0	17:17:40.671	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 203.03 ms)
0	17:17:41.234	'5002952': previous successful authorization performed from 101.36.110.43
1	17:19:58.765	'5002952': datacenter connecting failed [6]
0	17:20:20.734	'5002952': login on RoboForex-Pro-2 through Czech Republic (ping: 233.28 ms)
0	17:20:23.046	'5002952': login datacenter on RoboForex-Pro-2 through Czech Republic (ping: 233.28 ms)
0	17:20:23.921	'5002952': previous successful authorization performed from 101.36.110.43
1	23:25:06.844	'5002952': datacenter connecting failed [6]
0	23:26:09.829	'5002952': login on RoboForex-Pro-2 through Russia (ping: 306.19 ms)
0	23:26:12.250	'5002952': login datacenter on RoboForex-Pro-2 through Russia (ping: 306.19 ms)
0	23:26:13.188	'5002952': previous successful authorization performed from 101.36.110.43
0	23:27:33.000	'5002952': ping to current access point Russia is 291.48 ms
0	23:45:31.797	'5002952': login on RoboForex-Pro-2 through Netherlands (ping: 199.45 ms)
0	23:45:33.532	'5002952': login datacenter on RoboForex-Pro-2 through Netherlands (ping: 199.45 ms)
0	23:45:34.438	'5002952': previous successful authorization performed from 101.36.110.43