I'm having to back my 40 mile PtP that are using Nstreme back to 5.9 until this gets fixed. Signal is -61/-61 and 270/270 data rates everything is absolutely perfect but something changed sometime after 5.14 or maybe even earlier that is causing these problems.

Rolling back firmware fixes this issue.

please contact support@mikrotik.com to get a new test release of v5.17.
After upgrade, we suggest to reset the wireless configuration on that wireless interface by clicking on the Reset configuration button in winbox wireless interface menu.
Try to increase the hw-retries count to 15 on both ends for the wireless interface.
Also we suggest to try out Nv2 wireless protocol instead of Nstreme wireless protocol.
If you still see problems, make a support output files from both ends and send them to support@mikrotik.com

Hi Uldis, I cannot use NV2, as this is a part of a 6 link PtP stretching over 100's of miles. NV2 increases latency and I need that 1-2ms that Nstreme has.

Any plan to divide:
NV2 for P2P with lower latency
and NV2 for P2MP ?

Any plan to divide:
NV2 for P2P with lower latency
and NV2 for P2MP ?

NStreme doesn't work well any more so NV2 with P2P mode would be great!

Also, as usual, which I'm greatly surprised nobody else is complaining about:

1. Nstreme PThroughput never exceeds 50,000kbps even when data rates are 300/300Mbps!
2. The problems I see are with Nstreme and DUAL-CHAIN only. PThroughput still remains under 60,000

NV2 is great, but for all of us using Mikrotik for PtP we NEED Nstreme improvements with dual chain. NV2 throws erratic latency spikes, and an additional 3-4ms latency. If I do that on all my links, it will be 60ms at the end point of my network and with Nstreme is a solid 10-12ms.

GET US THAT 1ms LATENCY WITH NV2, PLEASE!!!!!!!