1	00:48:37.008	'5002952': ping failed
1	00:48:37.024	'5002952': datacenter connecting failed [6]
0	00:48:37.774	'5002952': login on RoboForex-Pro-2 through Russia (ping: 207.87 ms)
0	00:48:39.368	'5002952': login datacenter on RoboForex-Pro-2 through Russia (ping: 207.87 ms)
0	00:48:39.836	'5002952': previous successful authorization performed from 101.36.110.43
0	00:48:52.571	'5002952': ping to current access point Russia is 200.05 ms
0	01:00:09.257	'5002952': login on RoboForex-Pro-2 through Russia (ping: 200.05 ms)
0	01:00:10.851	'5002952': login datacenter on RoboForex-Pro-2 through Russia (ping: 200.05 ms)
0	01:00:11.335	'5002952': previous successful authorization performed from 101.36.110.43
0	01:44:39.609	'5002952': login on RoboForex-Pro-2 through Russia (ping: 200.05 ms)
0	01:44:41.234	'5002952': login datacenter on RoboForex-Pro-2 through Russia (ping: 200.05 ms)
0	01:44:41.703	'5002952': previous successful authorization performed from 101.36.110.43
1	01:53:43.890	'5002952': datacenter connecting failed [6]
0	01:53:56.828	'5002952': login on RoboForex-Pro-2 through Russia (ping: 200.05 ms)
0	01:54:43.953	'5002952': login datacenter on RoboForex-Pro-2 through Russia (ping: 200.05 ms)
0	01:54:44.437	'5002952': previous successful authorization performed from 101.36.110.43
0	01:54:56.687	'5002952': ping to current access point Russia is 200.46 ms
0	02:06:23.437	'5002952': login on RoboForex-Pro-2 through Russia (ping: 200.46 ms)
0	02:06:25.015	'5002952': login datacenter on RoboForex-Pro-2 through Russia (ping: 200.46 ms)
0	02:06:25.500	'5002952': previous successful authorization performed from 101.36.110.43
1	02:21:45.890	'5002952': ping failed
1	02:21:45.906	'5002952': datacenter connecting failed [6]
0	02:21:46.609	'5002952': login on RoboForex-Pro-2 through Germany (ping: 193.34 ms)
0	02:21:48.093	'5002952': login datacenter on RoboForex-Pro-2 through Germany (ping: 193.34 ms)
0	02:21:48.578	'5002952': previous successful authorization performed from 101.36.110.43
1	02:43:00.427	'5002952': datacenter connecting failed [6]
0	02:43:01.146	'5002952': login on RoboForex-Pro-2 through Germany (ping: 193.34 ms)
0	02:43:02.599	'5002952': login datacenter on RoboForex-Pro-2 through Germany (ping: 193.34 ms)
0	02:43:03.068	'5002952': previous successful authorization performed from 101.36.110.43
0	03:52:34.572	'5002952': login on RoboForex-Pro-2 through Germany (ping: 193.34 ms)
0	03:52:36.275	'5002952': login datacenter on RoboForex-Pro-2 through Germany (ping: 193.34 ms)
0	03:52:36.806	'5002952': previous successful authorization performed from 101.36.110.43
0	03:52:49.509	'5002952': auto connecting to a better access point Singapore (ping is 197.70 ms)
0	03:52:50.228	'5002952': login on RoboForex-Pro-2 through Singapore (ping: 197.70 ms)
0	03:52:51.572	'5002952': login datacenter on RoboForex-Pro-2 through Singapore (ping: 197.70 ms)
0	03:52:51.900	'5002952': previous successful authorization performed from 101.36.110.43
0	23:25:29.899	'5002952': login on RoboForex-Pro-2 through Russia (ping: 207.07 ms)
0	23:25:31.509	'5002952': login datacenter on RoboForex-Pro-2 through Russia (ping: 207.07 ms)
0	23:25:31.962	'5002952': previous successful authorization performed from 101.36.110.43
0	23:26:42.431	'5002952': ping to current access point Russia is 197.36 ms
1	23:30:51.934	'5002952': ping failed
1	23:30:51.934	'5002952': datacenter connecting failed [6]
0	23:30:52.637	'5002952': login on RoboForex-Pro-2 through Netherlands (ping: 201.27 ms)
0	23:30:54.309	'5002952': login datacenter on RoboForex-Pro-2 through Netherlands (ping: 201.27 ms)
0	23:30:54.840	'5002952': previous successful authorization performed from 101.36.110.43