1	04:51:13.831	'5002952': ping failed
1	04:51:13.847	'5002952': datacenter connecting failed [6]
0	04:51:14.487	'5002952': login on RoboForex-Pro-2 through Russia (ping: 219.18 ms)
1	04:51:37.003	'5002952': datacenter connecting failed [6]
0	04:51:37.362	'5002952': previous successful authorization performed from 101.36.110.43
0	04:51:48.956	'5002952': auto connecting to a better access point Hong Kong (ping is 187.87 ms)
0	04:51:49.644	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 187.87 ms)
0	04:51:51.081	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 187.87 ms)
0	04:51:51.425	'5002952': previous successful authorization performed from 101.36.110.43
1	12:10:40.706	'5002952': datacenter connecting failed [6]
0	12:10:41.487	'5002952': login on RoboForex-Pro-2 through Czech Republic (ping: 209.96 ms)
0	12:10:43.393	'5002952': login datacenter on RoboForex-Pro-2 through Czech Republic (ping: 209.96 ms)
0	12:10:43.925	'5002952': previous successful authorization performed from 101.36.110.43
0	12:11:07.518	'5002952': ping to current access point Czech Republic is 205.13 ms
0	19:30:57.993	'5002952': login on RoboForex-Pro-2 through Czech Republic (ping: 205.13 ms)
0	19:30:59.821	'5002952': login datacenter on RoboForex-Pro-2 through Czech Republic (ping: 205.13 ms)
0	19:31:00.352	'5002952': previous successful authorization performed from 101.36.110.43
0	19:31:16.149	'5002952': auto connecting to a better access point Hong Kong (ping is 187.35 ms)
0	19:31:16.790	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 187.35 ms)
0	19:31:18.274	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 187.35 ms)
0	19:31:18.884	'5002952': previous successful authorization performed from 101.36.110.43