Evaluating B-Book slippage and execution latency under LP failover scenarios
I'm looking for feedback from anyone who has run automated execution setups across multiple prime-of-prime bridges, specifically regarding how brokers handle feed handovers when their primary LP goes thin.
We've been running a latency-sensitive arbitrage/mean-reversion strategy on $EURUSD and $GBPUSD. Over the last quarter, we noticed a sharp increase in execution delay—sometimes up to 180ms—during the London-New York crossover. On paper, our broker claims a sub-30ms execution loop. However, under the hood, it looks like their bridge is failing over to secondary B-book pools when the primary tier-1 LP spreads widen.
This isn't just about the spread widening itself; it's the queue rejection and the subsequent re-routing latency that is killing our fill rate. For those who have gone through the due diligence of demanding raw FIX log audits from your brokers, how cooperative have they been? Did you find that switching to a pure STP setup with a dedicated prime brokerage clearing account resolved the routing latency, or is the bottleneck ultimately just the broker's MT5 gateway middleware? I'd prefer to avoid the overhead of moving to a full institutional Prime-of-Prime if we can optimize the current setup, but we cannot absorb these asymmetric slippage costs much longer.
We ran into the exact same issue last year during high-volatility events, and it turned out our broker's bridge was queuing orders instead of immediately rejecting them during the LP failover window. We ended up having to hardcode a maximum latency threshold on our side to auto-cancel any fills that took longer than 45ms to process. Have you checked if your bridge provider allows you to configure aggressive execution timeouts to prevent getting filled at stale off-market prices?