1	02:01:55.240	'5002952': ping failed
1	02:01:55.240	'5002952': datacenter connecting failed [6]
0	02:02:17.772	'5002952': login on RoboForex-Pro-2 through Czech Republic (ping: 168.43 ms)
0	02:02:49.631	'5002952': login datacenter on RoboForex-Pro-2 through Czech Republic (ping: 168.43 ms)
0	02:02:50.709	'5002952': previous successful authorization performed from 101.36.110.43
0	02:04:04.131	'5002952': auto connecting to a better access point Finland (ping is 164.33 ms)
0	02:04:26.068	'5002952': login on RoboForex-Pro-2 through Russia (ping: 154.95 ms)
0	02:04:36.303	'5002952': login datacenter on RoboForex-Pro-2 through Russia (ping: 154.95 ms)
0	02:04:37.334	'5002952': previous successful authorization performed from 101.36.110.43
1	02:13:57.693	'5002952': ping failed
1	02:13:57.709	'5002952': datacenter connecting failed [6]
0	02:13:59.678	'5002952': login on RoboForex-Pro-2 through Finland (ping: 164.33 ms)
0	02:14:08.443	'5002952': login datacenter on RoboForex-Pro-2 through Finland (ping: 164.33 ms)
0	02:14:12.443	'5002952': previous successful authorization performed from 101.36.110.43
1	02:15:51.522	'5002952': ping failed
1	02:15:51.537	'5002952': datacenter connecting failed [6]
0	02:15:52.209	'5002952': login on RoboForex-Pro-2 through Czech Republic (ping: 163.75 ms)
1	02:16:15.412	'5002952': datacenter connecting failed [6]
0	02:16:16.037	'5002952': previous successful authorization performed from 101.36.110.43
0	02:24:37.050	'5002952': login on RoboForex-Pro-2 through Czech Republic (ping: 163.75 ms)
0	02:24:38.659	'5002952': login datacenter on RoboForex-Pro-2 through Czech Republic (ping: 163.75 ms)
0	02:24:39.409	'5002952': previous successful authorization performed from 101.36.110.43
1	15:13:59.690	'5002952': ping failed
1	15:13:59.690	'5002952': datacenter connecting failed [6]
0	15:14:00.503	'5002952': login on RoboForex-Pro-2 through Germany (ping: 198.67 ms)
0	15:14:02.300	'5002952': login datacenter on RoboForex-Pro-2 through Germany (ping: 198.67 ms)
0	15:14:03.190	'5002952': previous successful authorization performed from 101.36.110.43
0	15:14:16.659	'5002952': auto connecting to a better access point Hong Kong (ping is 192.76 ms)
0	15:14:17.378	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 192.76 ms)
0	15:14:18.628	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 192.76 ms)
0	15:14:19.206	'5002952': previous successful authorization performed from 101.36.110.43
0	17:34:07.723	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 192.76 ms)
0	17:34:09.019	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 192.76 ms)
0	17:34:09.629	'5002952': previous successful authorization performed from 101.36.110.43
0	17:34:23.894	'5002952': ping to current access point Hong Kong is 195.16 ms
1	19:57:19.758	'5002952': connect failed [ûÓÐÁ¬½Ó]
0	19:58:14.898	'5002952': login on RoboForex-Pro-2 through Singapore (ping: n/a)
0	19:58:20.336	'5002952': login datacenter on RoboForex-Pro-2 through Singapore (ping: n/a)
0	19:58:21.117	'5002952': previous successful authorization performed from 101.36.110.43
0	19:58:34.617	'5002952': auto connecting to a better access point Germany (ping is 201.56 ms)
0	19:58:35.305	'5002952': login on RoboForex-Pro-2 through Germany (ping: 201.56 ms)
0	19:58:36.898	'5002952': login datacenter on RoboForex-Pro-2 through Germany (ping: 201.56 ms)
0	19:58:37.617	'5002952': previous successful authorization performed from 101.36.110.43