1	15:36:17.041	'5002952': connect failed [ûÓÐÁ¬½Ó]
0	15:40:16.525	'5002952': login on RoboForex-Pro-2 through DataCenter India (ping: n/a)
0	15:40:21.088	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter India (ping: n/a)
0	15:40:21.525	'5002952': previous successful authorization performed from 101.36.110.43
0	15:41:07.541	'5002952': auto connecting to a better access point DataCenter Russia (ping is 199.50 ms)
0	15:41:08.244	'5002952': login on RoboForex-Pro-2 through DataCenter Russia (ping: 199.50 ms)
0	15:41:10.134	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Russia (ping: 199.50 ms)
0	15:41:10.634	'5002952': previous successful authorization performed from 101.36.110.43
1	16:43:13.178	'5002952': ping failed
1	16:43:13.178	'5002952': datacenter connecting failed [6]
0	16:43:13.850	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 193.88 ms)
0	16:43:15.303	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 193.88 ms)
0	16:43:15.678	'5002952': previous successful authorization performed from 101.36.110.43
0	16:43:38.444	'5002952': ping to current access point DataCenter Hong Kong is 192.58 ms
0	23:26:15.384	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #5 (ping: 291.92 ms)
0	23:26:18.837	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #5 (ping: 291.92 ms)
0	23:26:19.697	'5002952': previous successful authorization performed from 101.36.110.43
0	23:27:31.541	'5002952': ping to current access point DataCenter Europe #5 is 288.36 ms