1	01:35:16.512	'5002952': datacenter connecting failed [6]
0	01:35:17.324	'5002952': login on RoboForex-Pro-2 through Hong Kong (ping: 190.52 ms)
0	01:35:19.074	'5002952': login datacenter on RoboForex-Pro-2 through Hong Kong (ping: 190.52 ms)
0	01:35:19.403	'5002952': previous successful authorization performed from 101.36.110.43
0	01:35:32.981	'5002952': auto connecting to a better access point Russia (ping is 183.79 ms)
0	01:35:33.606	'5002952': login on RoboForex-Pro-2 through Russia (ping: 183.79 ms)
0	01:35:35.434	'5002952': login datacenter on RoboForex-Pro-2 through Russia (ping: 183.79 ms)
0	01:35:35.965	'5002952': previous successful authorization performed from 101.36.110.43
1	08:50:27.294	'5002952': datacenter connecting failed [6]
0	08:50:28.044	'5002952': login on RoboForex-Pro-2 through Singapore (ping: 184.28 ms)
0	08:50:29.560	'5002952': login datacenter on RoboForex-Pro-2 through Singapore (ping: 184.28 ms)
0	08:50:29.997	'5002952': previous successful authorization performed from 101.36.110.43
0	08:51:45.294	'5002952': auto connecting to a better access point Russia (ping is 193.34 ms)
0	08:51:46.747	'5002952': login on RoboForex-Pro-2 through Russia (ping: 193.34 ms)
0	08:52:47.607	'5002952': login datacenter on RoboForex-Pro-2
0	08:52:53.653	'5002952': login on RoboForex-Pro-2 through Singapore (ping: 184.20 ms)
0	08:52:55.075	'5002952': login datacenter on RoboForex-Pro-2 through Singapore (ping: 184.20 ms)
0	08:52:55.450	'5002952': previous successful authorization performed from 101.36.110.43
0	08:53:01.513	'5002952': ping to current access point Singapore is 184.07 ms