0	20:51:34.567	'5002952': login on RoboForex-Pro-2 through Czech Republic (ping: 198.33 ms)
0	20:52:10.755	'5002952': login datacenter on RoboForex-Pro-2 through Czech Republic (ping: 198.33 ms)
0	20:52:11.958	'5002952': previous successful authorization performed from 101.36.110.43
0	20:52:35.489	'5002952': auto connecting to a better access point Germany (ping is 199.32 ms)
0	20:52:36.286	'5002952': login on RoboForex-Pro-2 through Germany (ping: 199.32 ms)
0	20:52:39.676	'5002952': login datacenter on RoboForex-Pro-2 through Germany (ping: 199.32 ms)
0	20:52:40.192	'5002952': previous successful authorization performed from 101.36.110.43
1	21:01:40.301	'5002952': ping failed
1	21:01:40.317	'5002952': datacenter connecting failed [6]
0	21:01:41.067	'5002952': login on RoboForex-Pro-2 through Singapore (ping: 196.08 ms)
0	21:01:42.411	'5002952': login datacenter on RoboForex-Pro-2 through Singapore (ping: 196.08 ms)
0	21:01:42.739	'5002952': previous successful authorization performed from 101.36.110.43
1	23:25:29.176	'5002952': ping failed
1	23:25:29.192	'5002952': datacenter connecting failed [6]
0	23:26:06.489	'5002952': login on RoboForex-Pro-2 through Russia (ping: 227.00 ms)
0	23:26:08.192	'5002952': login datacenter on RoboForex-Pro-2 through Russia (ping: 227.00 ms)
0	23:26:08.739	'5002952': previous successful authorization performed from 101.36.110.43
0	23:27:26.192	'5002952': ping to current access point Russia is 227.43 ms
0	23:45:32.911	'5002952': login on RoboForex-Pro-2 through Netherlands (ping: 233.96 ms)
0	23:45:34.880	'5002952': login datacenter on RoboForex-Pro-2 through Netherlands (ping: 233.96 ms)
0	23:45:35.473	'5002952': previous successful authorization performed from 101.36.110.43