1	03:38:00.977	'5002952': ping failed
0	03:38:10.868	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 193.91 ms)
0	03:38:12.259	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 193.91 ms)
0	03:38:12.806	'5002952': previous successful authorization performed from 103.17.92.221
0	03:38:38.870	'5002952': ping to current access point DataCenter Hong Kong is 193.78 ms
0	05:18:35.686	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 193.78 ms)
0	05:18:37.046	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 193.78 ms)
0	05:18:37.655	'5002952': previous successful authorization performed from 103.17.92.221
0	05:19:02.250	'5002952': ping to current access point DataCenter Hong Kong is 193.89 ms
0	09:22:39.570	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 193.89 ms)
0	09:22:40.867	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 193.89 ms)
0	09:22:41.383	'5002952': previous successful authorization performed from 103.17.92.221
0	09:23:07.181	'5002952': ping to current access point DataCenter Hong Kong is 193.77 ms
1	17:11:03.272	'5002952': ping failed
1	17:11:03.288	'5002952': datacenter connecting failed [6]
0	17:11:04.303	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 213.37 ms)
0	17:11:06.069	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 213.37 ms)
0	17:11:06.788	'5002952': previous successful authorization performed from 27.115.63.242
0	17:11:31.148	'5002952': auto connecting to a better access point DataCenter Hong Kong (ping is 193.75 ms)
0	17:11:32.149	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 193.75 ms)
0	17:11:33.445	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 193.75 ms)
0	17:11:33.961	'5002952': previous successful authorization performed from 103.17.92.221