3
ISby u/irina.stoica·3hDiscussion

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.

3 comments · 3 points

3 Comments

MTu/marija_toth·1h

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.

4
NIu/nicole26·38m

We ran into the exact same issue last quarter with our MT5 setup during CPI releases. Do you think adjusting the max allowable slippage parameter on the bridge level actually helps, or does that just lead to a massive spike in rejected orders for the retail clients?

4
ASu/aziz_sami·2h

We ran into this last year and ended up implementing a pre-execution price check on the bridge side to reject trades if the offset from the reference feed exceeded a set threshold. You also might want to look into adjusting your markup dynamically during high-volatility events to buffer the latency gap, though some LPs will penalize you for the rejects.

0

More like this