1	03:55:36.648	'5002952': ping failed
1	03:55:36.663	'5002952': datacenter connecting failed [6]
0	03:55:37.382	'5002952': login on RoboForex-Pro-2 through Singapore (ping: 199.87 ms)
0	03:55:38.804	'5002952': login datacenter on RoboForex-Pro-2 through Singapore (ping: 199.87 ms)
0	03:55:39.163	'5002952': previous successful authorization performed from 101.36.110.43
0	03:56:05.976	'5002952': auto connecting to a better access point Hong Kong (ping is 195.66 ms)
0	03:56:06.726	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 195.66 ms)
0	03:56:08.429	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 195.66 ms)
0	03:56:08.773	'5002952': previous successful authorization performed from 101.36.110.43
0	23:26:13.366	'5002952': login on RoboForex-Pro-2 through Netherlands (ping: 215.64 ms)
0	23:26:15.257	'5002952': login datacenter on RoboForex-Pro-2 through Netherlands (ping: 215.64 ms)
0	23:26:15.757	'5002952': previous successful authorization performed from 101.36.110.43
0	23:27:35.929	'5002952': auto connecting to a better access point Russia (ping is 218.69 ms)
0	23:27:36.616	'5002952': login on RoboForex-Pro-2 through Russia (ping: 218.69 ms)
0	23:27:38.460	'5002952': login datacenter on RoboForex-Pro-2 through Russia (ping: 218.69 ms)
0	23:27:38.991	'5002952': previous successful authorization performed from 101.36.110.43
1	23:45:39.976	'5002952': datacenter connecting failed [6]
0	23:46:02.085	'5002952': login on RoboForex-Pro-2 through Netherlands (ping: 192.74 ms)
0	23:46:04.069	'5002952': login datacenter on RoboForex-Pro-2 through Netherlands (ping: 192.74 ms)
0	23:46:04.585	'5002952': previous successful authorization performed from 101.36.110.43