1	02:16:55.443	'5002952': datacenter connecting failed [6]
0	02:16:56.349	'5002952': login on RoboForex-Pro-2 through Finland (ping: 218.62 ms)
0	02:16:58.583	'5002952': login datacenter on RoboForex-Pro-2 through Finland (ping: 218.62 ms)
0	02:16:59.271	'5002952': previous successful authorization performed from 101.36.110.43
0	02:17:11.490	'5002952': auto connecting to a better access point Russia (ping is 201.16 ms)
0	02:17:12.240	'5002952': login on RoboForex-Pro-2 through Russia (ping: 201.16 ms)
0	02:17:13.990	'5002952': login datacenter on RoboForex-Pro-2 through Russia (ping: 201.16 ms)
0	02:17:14.552	'5002952': previous successful authorization performed from 101.36.110.43
1	02:30:37.450	'5002952': datacenter connecting failed [6]
0	02:30:38.388	'5002952': login on RoboForex-Pro-2 through Finland (ping: 219.57 ms)
0	02:30:40.622	'5002952': login datacenter on RoboForex-Pro-2 through Finland (ping: 219.57 ms)
0	02:30:41.263	'5002952': previous successful authorization performed from 101.36.110.43
1	02:52:36.450	'5002952': datacenter connecting failed [6]
0	02:52:37.091	'5002952': login on RoboForex-Pro-2 through Germany (ping: 196.51 ms)
0	02:52:38.685	'5002952': login datacenter on RoboForex-Pro-2 through Germany (ping: 196.51 ms)
0	02:52:39.200	'5002952': previous successful authorization performed from 101.36.110.43
1	05:50:19.665	'5002952': ping failed
1	05:50:19.681	'5002952': datacenter connecting failed [6]
0	05:50:20.400	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 207.27 ms)
0	05:50:21.665	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 207.27 ms)
0	05:50:21.978	'5002952': previous successful authorization performed from 101.36.110.43
0	05:50:35.025	'5002952': auto connecting to a better access point Russia (ping is 204.96 ms)
0	05:50:35.806	'5002952': login on RoboForex-Pro-2 through Russia (ping: 204.96 ms)
0	05:50:37.384	'5002952': login datacenter on RoboForex-Pro-2 through Russia (ping: 204.96 ms)
0	05:50:37.853	'5002952': previous successful authorization performed from 101.36.110.43
1	06:08:58.751	'5002952': ping failed
0	06:08:59.439	'5002952': login on RoboForex-Pro-2 through Russia (ping: 204.96 ms)
0	06:09:01.095	'5002952': login datacenter on RoboForex-Pro-2 through Russia (ping: 204.96 ms)
0	06:09:01.595	'5002952': previous successful authorization performed from 101.36.110.43
1	06:54:23.375	'5002952': ping failed
1	06:54:44.407	'5002952': datacenter connecting failed [6]
0	06:54:45.094	'5002952': login on RoboForex-Pro-2 through Singapore (ping: 197.42 ms)
0	06:54:46.360	'5002952': login datacenter on RoboForex-Pro-2 through Singapore (ping: 197.42 ms)
0	06:54:46.750	'5002952': previous successful authorization performed from 101.36.110.43
0	06:55:11.407	'5002952': auto connecting to a better access point Russia (ping is 205.54 ms)
0	06:55:12.141	'5002952': login on RoboForex-Pro-2 through Russia (ping: 205.54 ms)
0	06:55:13.828	'5002952': login datacenter on RoboForex-Pro-2 through Russia (ping: 205.54 ms)
0	06:55:14.328	'5002952': previous successful authorization performed from 101.36.110.43
0	07:08:46.241	'5002952': login on RoboForex-Pro-2 through Russia (ping: 205.54 ms)
0	07:08:47.835	'5002952': login datacenter on RoboForex-Pro-2 through Russia (ping: 205.54 ms)
0	07:08:48.320	'5002952': previous successful authorization performed from 101.36.110.43
1	07:25:28.788	'5002952': ping failed
1	07:25:28.788	'5002952': datacenter connecting failed [6]
0	07:25:29.538	'5002952': login on RoboForex-Pro-2 through Singapore (ping: 198.41 ms)
0	07:25:30.960	'5002952': login datacenter on RoboForex-Pro-2 through Singapore (ping: 198.41 ms)
0	07:25:31.320	'5002952': previous successful authorization performed from 101.36.110.43