1	03:10:26.134	'5002952': ping failed
1	03:10:26.384	'5002952': connect failed [ûÓÐÁ¬½Ó]
0	03:10:32.666	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 206.60 ms)
0	03:10:34.384	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 206.60 ms)
0	03:10:35.025	'5002952': previous successful authorization performed from 103.233.11.57
0	03:11:13.558	'5002952': auto connecting to a better access point DataCenter Europe #3 (ping is 209.85 ms)
0	03:11:14.480	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 209.85 ms)
0	03:11:16.089	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 209.85 ms)
0	03:11:16.730	'5002952': previous successful authorization performed from 103.233.11.57
1	19:25:41.918	'5002952': ping failed
1	19:25:41.934	'5002952': datacenter connecting failed [6]
0	19:25:42.715	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.35 ms)
0	19:25:43.965	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.35 ms)
0	19:25:44.434	'5002952': previous successful authorization performed from 103.233.11.57
0	19:26:18.279	'5002952': ping to current access point DataCenter Hong Kong is 198.59 ms
0	23:31:58.887	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 198.59 ms)
0	23:32:00.528	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 198.59 ms)
0	23:32:01.043	'5002952': previous successful authorization performed from 103.233.11.57
0	23:32:35.514	'5002952': auto connecting to a better access point DataCenter India (ping is 221.90 ms)
0	23:32:36.483	'5002952': login on RoboForex-Pro-2 through DataCenter India (ping: 221.90 ms)
0	23:32:38.029	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter India (ping: 221.90 ms)
0	23:32:38.608	'5002952': previous successful authorization performed from 103.233.11.57