1	04:20:20.739	'5002952': datacenter connecting failed [6]
0	04:20:42.552	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 198.02 ms)
0	04:20:44.083	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 198.02 ms)
0	04:20:44.880	'5002952': previous successful authorization performed from 101.36.110.43
0	04:21:07.958	'5002952': ping to current access point Hong Kong is 194.85 ms
1	08:01:16.708	'5002952': connect failed [ûÓÐÁ¬½Ó]
0	08:01:44.552	'5002952': login on RoboForex-Pro-2 through Netherlands (ping: 193.59 ms)
0	08:01:46.333	'5002952': login datacenter on RoboForex-Pro-2 through Netherlands (ping: 193.59 ms)
0	08:01:47.255	'5002952': previous successful authorization performed from 101.36.110.43
0	08:02:04.427	'5002952': auto connecting to a better access point Singapore (ping is 195.65 ms)
0	08:02:05.271	'5002952': login on RoboForex-Pro-2 through Singapore (ping: 195.65 ms)
0	08:02:06.911	'5002952': login datacenter on RoboForex-Pro-2 through Singapore (ping: 195.65 ms)
0	08:02:07.849	'5002952': previous successful authorization performed from 101.36.110.43
0	23:26:10.193	'5002952': login on RoboForex-Pro-2 through Russia (ping: 287.57 ms)
0	23:26:11.927	'5002952': login datacenter on RoboForex-Pro-2 through Russia (ping: 287.57 ms)
0	23:26:12.896	'5002952': previous successful authorization performed from 101.36.110.43
0	23:27:22.583	'5002952': ping to current access point Russia is 307.45 ms
1	23:45:12.364	'5002952': datacenter connecting failed [6]
0	23:45:34.068	'5002952': login on RoboForex-Pro-2 through Netherlands (ping: 190.75 ms)
0	23:45:35.568	'5002952': login datacenter on RoboForex-Pro-2 through Netherlands (ping: 190.75 ms)
0	23:45:36.583	'5002952': previous successful authorization performed from 101.36.110.43