1	17:31:34.890	'5002952': datacenter connecting failed [6]
1	17:31:34.937	'5002952': connect failed [Ò»°ã´íÎó]
0	17:32:29.374	'5002952': login on RoboForex-Pro-2 through Singapore (ping: n/a)
0	17:32:37.062	'5002952': login datacenter on RoboForex-Pro-2 through Singapore (ping: n/a)
0	17:32:37.640	'5002952': previous successful authorization performed from 101.36.110.43
0	17:32:51.984	'5002952': auto connecting to a better access point Hong Kong (ping is 177.84 ms)
0	17:32:52.702	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 177.84 ms)
0	17:32:54.062	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 177.84 ms)
0	17:32:54.530	'5002952': previous successful authorization performed from 101.36.110.43
0	23:26:30.174	'5002952': login on RoboForex-Pro-2 through Russia (ping: 221.23 ms)
0	23:26:32.111	'5002952': login datacenter on RoboForex-Pro-2 through Russia (ping: 221.23 ms)
0	23:26:32.877	'5002952': previous successful authorization performed from 101.36.110.43
0	23:27:44.440	'5002952': auto connecting to a better access point Hong Kong (ping is 177.75 ms)
1	23:27:44.502	'5002952': connect failed [Ò»°ã´íÎó]
0	23:27:50.268	'5002952': login on RoboForex-Pro-2 through Russia (ping: 222.29 ms)
0	23:27:52.065	'5002952': login datacenter on RoboForex-Pro-2 through Russia (ping: 222.29 ms)
0	23:27:52.783	'5002952': previous successful authorization performed from 101.36.110.43
0	23:45:32.533	'5002952': login on RoboForex-Pro-2 through Netherlands (ping: 209.50 ms)
0	23:45:34.393	'5002952': login datacenter on RoboForex-Pro-2 through Netherlands (ping: 209.50 ms)
0	23:45:35.190	'5002952': previous successful authorization performed from 101.36.110.43