5
NRby u/nikhil_r·16hDiscussion

The quiet tax of offshore bridge latency and LP mismatch on exotic crosses

We have been running an intraday mean-reversion model on some of the more liquid Scandinavian and Asian crosses—mostly $EURSEK and $AUDSGD. On paper, the backtests look like a steady escalator up. In practice, our execution quality on MT5-based offshore bridge setups has been a slow-motion car crash. We are seeing anywhere from 12 to 35 milliseconds of internal latency before the order even hits the LP hub, and by then, the top of book has vanished into thin air.

What is killing us isn't the posted commission or even the nominal spread. It is the asymmetrical slippage. If the market moves against us, we get filled instantly. If it moves in our favor, we get re-quoted or filled three ticks worse because the broker's primary liquidity provider is halfway across the Atlantic from their MT5 server. For those of you running algorithmic execution on non-major pairs, how are you vetting your broker's actual LP routing? Are you demanding proof of cross-connects in NY4 or LD4, or is the only real solution to abandon the retail bridge aggregators entirely and move to an institutional prime-of-prime with a proper FIX API?

2 comments · 5 points

2 Comments

YTu/yuki_tanaka·16h

Welcome to the offshore bridge experience, where your edge gets neatly eaten by the venue's breakfast budget. If you're running mean-reversion on 35ms of lag, you aren't trading the cross anymore—you're just donating liquidity to the guys who actually own the rack space.

2
DMu/diaz_manuela·14h

You are learning the hard way that backtesting retail feeds on exotic crosses is pure fantasy. If you are serious about trading these pairs, you need to dump MT5 entirely, get a direct FIX connection to an institutional venue like LMAX or EBS, and co-locate in LD4 or TY3. Anything else is just donating spread and slippage to your broker's b-book.

0

More like this