1	08:00:51.934	'5002952': connect failed [ûÓÐÁ¬½Ó]
0	08:01:18.981	'5002952': login on RoboForex-Pro-2 through India (ping: 221.85 ms)
0	08:01:24.575	'5002952': login datacenter on RoboForex-Pro-2 through India (ping: 221.85 ms)
0	08:01:25.278	'5002952': previous successful authorization performed from 101.36.110.43
0	08:01:42.294	'5002952': auto connecting to a better access point Hong Kong (ping is 190.18 ms)
0	08:01:42.825	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 190.18 ms)
0	08:01:46.856	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 190.18 ms)
0	08:01:47.341	'5002952': previous successful authorization performed from 101.36.110.43
1	10:16:57.632	'5002952': datacenter connecting failed [6]
0	10:16:58.288	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 190.18 ms)
0	10:16:59.616	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 190.18 ms)
0	10:17:00.100	'5002952': previous successful authorization performed from 101.36.110.43
0	10:17:13.319	'5002952': ping to current access point Hong Kong is 189.75 ms
0	23:26:26.662	'5002952': login on RoboForex-Pro-2 through Russia (ping: 221.61 ms)
0	23:26:28.474	'5002952': login datacenter on RoboForex-Pro-2 through Russia (ping: 221.61 ms)
0	23:26:29.162	'5002952': previous successful authorization performed from 101.36.110.43
0	23:27:46.974	'5002952': auto connecting to a better access point Hong Kong (ping is 189.72 ms)
0	23:27:47.599	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 189.72 ms)
0	23:27:48.943	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 189.72 ms)
0	23:27:49.427	'5002952': previous successful authorization performed from 101.36.110.43