1	08:01:27.072	'5002952': connect failed [ûÓÐÁ¬½Ó]
0	08:02:04.463	'5002952': login on RoboForex-Pro-2 through Germany #2 (ping: 305.40 ms)
0	08:02:09.369	'5002952': login datacenter on RoboForex-Pro-2 through Germany (ping: 305.40 ms)
0	08:02:10.088	'5002952': previous successful authorization performed from 101.36.110.43
0	08:02:46.978	'5002952': auto connecting to a better access point Russia (ping is 200.45 ms)
0	08:02:47.931	'5002952': login on RoboForex-Pro-2 through Russia (ping: 200.45 ms)
0	08:02:50.619	'5002952': login datacenter on RoboForex-Pro-2 through Russia (ping: 200.45 ms)
0	08:02:51.213	'5002952': previous successful authorization performed from 101.36.110.43
1	17:24:38.627	'5002952': ping failed
0	17:24:39.361	'5002952': login on RoboForex-Pro-2 through Russia (ping: 200.45 ms)
0	17:24:41.298	'5002952': login datacenter on RoboForex-Pro-2 through Russia (ping: 200.45 ms)
0	17:24:41.861	'5002952': previous successful authorization performed from 101.36.110.43
0	17:24:56.923	'5002952': ping to current access point Russia is 196.12 ms
1	23:25:14.712	'5002952': datacenter connecting failed [6]
0	23:26:19.931	'5002952': login on RoboForex-Pro-2 through Netherlands (ping: 206.35 ms)
0	23:26:22.056	'5002952': login datacenter on RoboForex-Pro-2 through Netherlands (ping: 206.35 ms)
0	23:26:22.587	'5002952': previous successful authorization performed from 101.36.110.43
0	23:27:51.947	'5002952': auto connecting to a better access point Hong Kong (ping is 191.55 ms)
0	23:27:52.494	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 191.55 ms)
0	23:27:53.947	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 191.55 ms)
0	23:27:54.275	'5002952': previous successful authorization performed from 101.36.110.43