1 19:35:13.575 '5002952': connect failed [ûÓÐÁ¬½Ó] 0 19:35:19.341 '5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 203.03 ms) 0 19:35:20.794 '5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 203.03 ms) 0 19:35:21.169 '5002952': previous successful authorization performed from 101.36.110.43 0 19:35:34.481 '5002952': auto connecting to a better access point Czech Republic (ping is 204.16 ms) 0 19:35:35.231 '5002952': login on RoboForex-Pro-2 through Czech Republic (ping: 204.16 ms) 0 19:35:38.262 '5002952': login datacenter on RoboForex-Pro-2 through Czech Republic (ping: 204.16 ms) 0 19:35:38.966 '5002952': previous successful authorization performed from 101.36.110.43 1 22:26:00.965 '5002952': datacenter connecting failed [6] 0 22:26:01.715 '5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 202.49 ms) 0 22:26:03.215 '5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 202.49 ms) 0 22:26:03.543 '5002952': previous successful authorization performed from 101.36.110.43 0 22:26:17.528 '5002952': auto connecting to a better access point Czech Republic (ping is 196.19 ms) 0 22:26:18.278 '5002952': login on RoboForex-Pro-2 through Czech Republic (ping: 196.19 ms) 0 22:26:20.122 '5002952': login datacenter on RoboForex-Pro-2 through Czech Republic (ping: 196.19 ms) 0 22:26:20.700 '5002952': previous successful authorization performed from 101.36.110.43 1 23:24:43.293 '5002952': ping failed 1 23:24:43.309 '5002952': datacenter connecting failed [6] 0 23:24:43.918 '5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 202.33 ms) 0 23:24:45.371 '5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 202.33 ms) 0 23:24:45.746 '5002952': previous successful authorization performed from 101.36.110.43