1	12:01:41.154	'5002952': datacenter connecting failed [6]
1	12:01:41.466	'5002952': connect failed [ûÓÐÁ¬½Ó]
0	12:01:47.325	'5002952': login on RoboForex-Pro-2 through Czech Republic (ping: 241.63 ms)
0	12:01:49.310	'5002952': login datacenter on RoboForex-Pro-2 through Czech Republic (ping: 241.63 ms)
0	12:01:50.341	'5002952': previous successful authorization performed from 101.36.110.43
0	12:02:05.622	'5002952': auto connecting to a better access point Hong Kong (ping is 229.46 ms)
0	12:02:06.513	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 229.46 ms)
0	12:02:11.904	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 229.46 ms)
0	12:02:13.263	'5002952': previous successful authorization performed from 101.36.110.43
1	20:31:32.777	'5002952': datacenter connecting failed [6]
0	20:31:33.542	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 229.46 ms)
0	20:31:36.027	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 229.46 ms)
0	20:31:36.605	'5002952': previous successful authorization performed from 101.36.110.43
0	20:31:52.808	'5002952': auto connecting to a better access point India (ping is 238.81 ms)
0	20:31:53.698	'5002952': login on RoboForex-Pro-2 through India (ping: 238.81 ms)
0	20:31:55.527	'5002952': login datacenter on RoboForex-Pro-2 through India (ping: 238.81 ms)
0	20:31:56.230	'5002952': previous successful authorization performed from 101.36.110.43