0	05:59:09.096	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 191.55 ms)
0	05:59:10.596	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 191.55 ms)
0	05:59:10.924	'5002952': previous successful authorization performed from 101.36.110.43
0	05:59:25.987	'5002952': auto connecting to a better access point Russia (ping is 192.76 ms)
0	05:59:26.768	'5002952': login on RoboForex-Pro-2 through Russia (ping: 192.76 ms)
0	05:59:28.690	'5002952': login datacenter on RoboForex-Pro-2 through Russia (ping: 192.76 ms)
0	05:59:29.252	'5002952': previous successful authorization performed from 101.36.110.43
0	16:41:43.672	'5002952': login on RoboForex-Pro-2 through Russia (ping: 192.76 ms)
0	16:41:45.985	'5002952': login datacenter on RoboForex-Pro-2 through Russia (ping: 192.76 ms)
0	16:41:46.579	'5002952': previous successful authorization performed from 101.36.110.43
0	16:42:01.235	'5002952': auto connecting to a better access point Hong Kong (ping is 191.48 ms)
0	16:42:01.954	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 191.48 ms)
0	16:42:03.532	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 191.48 ms)
0	16:42:03.907	'5002952': previous successful authorization performed from 101.36.110.43
1	23:01:12.204	'5002952': datacenter connecting failed [6]
0	23:01:12.829	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 191.48 ms)
0	23:01:14.344	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 191.48 ms)
0	23:01:14.672	'5002952': previous successful authorization performed from 101.36.110.43
0	23:01:30.610	'5002952': auto connecting to a better access point Singapore #2 (ping is 185.16 ms)
0	23:01:30.829	'5002952': login datacenter on RoboForex-Pro-2
0	23:01:31.922	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 192.21 ms)
0	23:01:33.438	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 192.21 ms)
0	23:01:33.797	'5002952': previous successful authorization performed from 101.36.110.43