1	00:21:33.595	'5002952': ping failed
1	00:21:33.611	'5002952': datacenter connecting failed [6]
0	00:21:34.814	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 217.96 ms)
0	00:21:36.486	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 217.96 ms)
0	00:21:37.314	'5002952': previous successful authorization performed from 103.17.92.221
0	00:22:02.018	'5002952': auto connecting to a better access point DataCenter Hong Kong (ping is 193.88 ms)
0	00:22:03.034	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 193.88 ms)
0	00:22:04.346	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 193.88 ms)
0	00:22:04.909	'5002952': previous successful authorization performed from 103.17.92.221
0	01:59:50.001	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 193.88 ms)
0	01:59:51.344	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 193.88 ms)
0	01:59:51.844	'5002952': previous successful authorization performed from 103.17.92.221
0	02:00:17.236	'5002952': ping to current access point DataCenter Hong Kong is 194.02 ms
1	02:35:13.039	'5002952': ping failed
1	02:35:13.055	'5002952': datacenter connecting failed [6]
0	02:35:14.070	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 213.79 ms)
0	02:35:15.758	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 213.79 ms)
0	02:35:16.602	'5002952': previous successful authorization performed from 103.17.92.221
1	12:07:11.552	'5002952': ping failed
1	12:07:11.568	'5002952': datacenter connecting failed [6]
0	12:07:12.552	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 214.62 ms)
0	12:07:14.271	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 214.62 ms)
0	12:07:14.943	'5002952': previous successful authorization performed from 103.17.92.221
0	12:07:38.585	'5002952': auto connecting to a better access point DataCenter Hong Kong (ping is 194.20 ms)
0	12:07:39.460	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 194.20 ms)
0	12:07:40.741	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 194.20 ms)
0	12:07:41.210	'5002952': previous successful authorization performed from 103.17.92.221
1	13:36:34.808	'5002952': datacenter connecting failed [6]
0	13:36:44.855	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 194.20 ms)
0	13:36:46.121	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 194.20 ms)
0	13:36:46.589	'5002952': previous successful authorization performed from 27.115.63.242
0	13:37:11.544	'5002952': ping to current access point DataCenter Hong Kong is 193.81 ms
0	19:11:22.513	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 193.81 ms)
0	19:11:23.810	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 193.81 ms)
0	19:11:24.279	'5002952': previous successful authorization performed from 103.17.92.221
0	19:11:49.421	'5002952': ping to current access point DataCenter Hong Kong is 193.87 ms
1	20:55:49.358	'5002952': ping failed
0	20:55:59.437	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 193.87 ms)
0	20:56:00.734	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 193.87 ms)
0	20:56:01.250	'5002952': previous successful authorization performed from 103.17.92.221
0	20:56:25.657	'5002952': ping to current access point DataCenter Hong Kong is 193.78 ms
1	21:22:21.965	'5002952': ping failed
1	21:22:21.981	'5002952': datacenter connecting failed [6]
0	21:22:31.982	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 202.17 ms)
0	21:22:33.435	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 202.17 ms)
0	21:22:34.044	'5002952': previous successful authorization performed from 103.17.92.221