1	02:57:09.810	'5002952': ping failed
0	02:57:10.544	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 189.32 ms)
0	02:57:11.857	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 189.32 ms)
0	02:57:12.357	'5002952': previous successful authorization performed from 101.36.110.43
0	02:57:25.638	'5002952': ping to current access point Hong Kong is 189.32 ms
1	06:01:40.499	'5002952': ping failed
1	06:01:40.514	'5002952': datacenter connecting failed [2]
0	06:01:41.264	'5002952': login on RoboForex-Pro-2 through Czech Republic (ping: 207.96 ms)
0	06:01:43.077	'5002952': login datacenter on RoboForex-Pro-2 through Czech Republic (ping: 207.96 ms)
0	06:01:43.764	'5002952': previous successful authorization performed from 101.36.110.43
0	06:01:56.889	'5002952': auto connecting to a better access point Hong Kong (ping is 189.25 ms)
0	06:01:57.624	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 189.25 ms)
0	06:01:58.983	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 189.25 ms)
0	06:01:59.483	'5002952': previous successful authorization performed from 101.36.110.43
1	08:40:37.135	'5002952': datacenter connecting failed [2]
0	08:40:37.838	'5002952': login on RoboForex-Pro-2 through Czech Republic (ping: 213.68 ms)
0	08:40:39.792	'5002952': login datacenter on RoboForex-Pro-2 through Czech Republic (ping: 213.68 ms)
0	08:40:40.620	'5002952': previous successful authorization performed from 101.36.110.43
0	08:40:53.385	'5002952': auto connecting to a better access point Hong Kong (ping is 189.61 ms)
0	08:40:54.135	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 189.61 ms)
0	08:40:55.479	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 189.61 ms)
0	08:40:55.995	'5002952': previous successful authorization performed from 101.36.110.43