1	04:18:29.704	'5002952': datacenter connecting failed [6]
1	04:18:29.751	'5002952': connect failed [Ò»°ã´íÎó]
0	04:24:16.375	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: n/a)
0	04:24:20.625	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: n/a)
0	04:24:21.109	'5002952': previous successful authorization performed from 101.36.110.43
0	04:24:34.125	'5002952': auto connecting to a better access point Germany (ping is 198.85 ms)
0	04:24:34.719	'5002952': login on RoboForex-Pro-2 through Germany (ping: 198.85 ms)
0	04:24:36.422	'5002952': login datacenter on RoboForex-Pro-2 through Germany (ping: 198.85 ms)
0	04:24:37.063	'5002952': previous successful authorization performed from 101.36.110.43
1	23:25:22.191	'5002952': datacenter connecting failed [6]
0	23:26:23.613	'5002952': login on RoboForex-Pro-2 through Russia (ping: 218.88 ms)
0	23:26:25.300	'5002952': login datacenter on RoboForex-Pro-2 through Russia (ping: 218.88 ms)
0	23:26:25.972	'5002952': previous successful authorization performed from 101.36.110.43
0	23:27:45.863	'5002952': ping to current access point Russia is 219.43 ms
1	23:45:10.910	'5002952': datacenter connecting failed [6]
0	23:45:32.691	'5002952': login on RoboForex-Pro-2 through Netherlands (ping: 211.96 ms)
0	23:45:34.425	'5002952': login datacenter on RoboForex-Pro-2 through Netherlands (ping: 211.96 ms)
0	23:45:35.113	'5002952': previous successful authorization performed from 101.36.110.43