1	01:29:39.522	'5002952': ping failed
1	01:29:39.522	'5002952': datacenter connecting failed [6]
0	01:29:40.318	'5002952': login on RoboForex-Pro-2 through Russia (ping: 222.29 ms)
0	01:29:42.115	'5002952': login datacenter on RoboForex-Pro-2 through Russia (ping: 222.29 ms)
0	01:29:42.818	'5002952': previous successful authorization performed from 101.36.110.43
0	01:30:02.381	'5002952': auto connecting to a better access point Hong Kong (ping is 177.55 ms)
0	01:30:03.084	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 177.55 ms)
0	01:30:04.412	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 177.55 ms)
0	01:30:04.943	'5002952': previous successful authorization performed from 101.36.110.43
1	03:07:49.206	'5002952': connect failed [Ò»°ã´íÎó]
0	03:13:44.753	'5002952': login on RoboForex-Pro-2 through Brazil (ping: n/a)
0	03:13:52.034	'5002952': login datacenter on RoboForex-Pro-2 through Brazil (ping: n/a)
0	03:13:53.097	'5002952': previous successful authorization performed from 101.36.110.43
0	03:14:05.550	'5002952': auto connecting to a better access point Hong Kong (ping is 177.40 ms)
0	03:14:06.300	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 177.40 ms)
0	03:14:07.581	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 177.40 ms)
0	03:14:08.065	'5002952': previous successful authorization performed from 101.36.110.43
0	19:54:05.853	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 177.40 ms)
0	19:54:07.153	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 177.40 ms)
0	19:54:07.638	'5002952': previous successful authorization performed from 101.36.110.43
0	19:54:21.653	'5002952': ping to current access point Hong Kong is 180.06 ms