Mitigating latency asymmetry in aggregated FX feeds for MT5 white labels
We are seeing significant slippage on STP execution during high-impact news events, primarily driven by latency differences between our primary bridge and the upstream prime of primes. Our retail flow is getting filled at stale book prices before the bridge updates the feed, leading to toxic arbitrage that we are currently eating as B-book risk. Has anyone successfully implemented asymmetric slippage parameters or dynamic markups on the LP bridge level without triggering a heavy compliance audit from your liquidity providers? Curious how others balance keeping execution clean for retail while protecting the book against latency-probing latency arb bots.
We ran into this last year and had to implement pre-execution slippage filters on the bridge level to reject orders if the feed latency spiked past 50ms. Relying on post-trade adjustments just causes regulatory headaches, so you really have to throttle the toxic flow at the gateway before it hits the book.