1
PBby u/pbernard·2hDiscussion

B-book execution latency and systematic slippage on high-impact news feeds

I have been running a legacy mean-reversion model across several MT5-based retail brokers and secondary liquidity providers. Lately, the friction during Tier-1 data releases ($USD CPI, FOMC) has drifted past what I would consider normal market impact. I am seeing execution delays of 180ms to 450ms specifically on limit fills, which makes me suspect aggressive virtual dealer plug-in settings rather than genuine upstream prime-of-prime bottlenecks.

While some slippage is a given when liquidity pools thin out, the asymmetry is becoming a drag on performance. Fills on negative slippage are consistently executed at the worst possible tick, whereas positive slippage is capped or nonexistent on the same pairs (mainly $EURUSD and $GBPUSD). For those operating automated systems through bridge providers like Gold-i or PrimeXM: are you observing similar execution degradation on 'raw spread' accounts, or is it time to bite the bullet, clear the higher capital requirements, and move entirely to a true LMAX or Saxo institutional setup? I am trying to determine if this is a systemic infrastructure decay across retail bridges or if my specific flow has just been flagged for soft-benched execution.

2 comments · 1 points

2 Comments

TOu/torThailand·27m

That latency profile is classic B-book behavior, especially since MT5 plugins can simulate queue delays during high-volatility events to protect their internal book. Have you compared the fill rates on a true prime-of-prime LMAX setup under the same millisecond timestamps? If the slippage persists there, it might just be the actual interbank liquidity pool evaporating.

3
OLu/olenastoica·1h

You are probably right on the money with the virtual dealer suspicion. A lot of those MT5 shops tweak their bridge settings during high-impact releases to protect their own books, basically turning your limit orders into market orders with synthetic slippage. Honestly, if you are running anything sensitive to milliseconds, you have got to get off the retail platforms and move to a proper prime-of-prime setup with direct FIX access.

0

More like this