1	01:52:07.192	'5002952': ping failed
1	01:52:07.208	'5002952': datacenter connecting failed [6]
0	01:52:07.974	'5002952': login on RoboForex-Pro-2 through Netherlands (ping: 179.08 ms)
0	01:52:09.802	'5002952': login datacenter on RoboForex-Pro-2 through Netherlands (ping: 179.08 ms)
0	01:52:10.286	'5002952': previous successful authorization performed from 101.36.110.43
0	01:52:22.505	'5002952': auto connecting to a better access point Germany (ping is 209.96 ms)
0	01:52:23.302	'5002952': login on RoboForex-Pro-2 through Germany (ping: 209.96 ms)
0	01:52:25.286	'5002952': login datacenter on RoboForex-Pro-2 through Germany (ping: 209.96 ms)
0	01:52:25.833	'5002952': previous successful authorization performed from 101.36.110.43
1	07:40:33.007	'5002952': ping failed
1	07:40:33.023	'5002952': datacenter connecting failed [6]
0	07:40:33.835	'5002952': login on RoboForex-Pro-2 through Czech Republic (ping: 202.90 ms)
0	07:40:35.913	'5002952': login datacenter on RoboForex-Pro-2 through Czech Republic (ping: 202.90 ms)
0	07:40:36.491	'5002952': previous successful authorization performed from 101.36.110.43
0	07:40:48.819	'5002952': auto connecting to a better access point Singapore (ping is 195.43 ms)
0	07:40:49.585	'5002952': login on RoboForex-Pro-2 through Singapore (ping: 195.43 ms)
0	07:40:51.132	'5002952': login datacenter on RoboForex-Pro-2 through Singapore (ping: 195.43 ms)
0	07:40:51.491	'5002952': previous successful authorization performed from 101.36.110.43