Skip to main content
Strategy — home ISP routing

Home ISP routing — why your connection to your broker is probably worse than you think.

Your internet plan's download speed is not what determines your trading connection quality. The path your packets take from your router to your broker's matching engine is what matters — and residential ISPs rarely optimise that path for trading.

The priority route exists because the route between a home connection and a broker data centre is reliably inefficient. Not because ISPs are bad — because they are built for different traffic than yours.

See the plansLatency and jitter guide
Shared
Your ISP's transit network is shared with streaming, gaming, and everything else.
Variable
Route quality changes by time of day based on your ISP segment load.
Fixable
A dedicated routing layer replaces the variable hop with a clean, direct one.

What residential ISP routing actually looks like

When you submit an order from home, it travels from your router to your ISP's local exchange, then into their transit network, then across one or more peering points to the network carrying your broker's data centre. Each of those hops introduces potential variance. When your ISP segment is under load — evenings, weekends, session overlaps — some of those hops slow down and the variance increases.

Run a traceroute to your broker's MT server hostname and you will typically see 10-15 hops. Several of those hops are on shared infrastructure that your ISP does not prioritise for low-latency traffic. The result is a path that is efficient enough for streaming video and browsing but produces inconsistent timing for the persistent connections that trading platforms depend on.

Why speed tests don't show this problem

Speed tests measure bandwidth to a nearby test server. They tell you how much data per second you can move over a short burst. That is useful for knowing if your internet plan is working. It tells you nothing about the route quality to a specific server in London, Sydney, or New Jersey.

What you want to measure is the round-trip time to your broker's actual MT server hostname. Ping it for 60 seconds at three different times: quiet afternoon, London open, and London/New York overlap. Watch the min-max spread across those pings. A narrow spread means the route is stable. A wide spread means your ISP's transit is introducing jitter at the moments that matter most.

What a proxy actually changes

A proxy route does not speed up your ISP. What it does is replace the variable, multi-hop residential path with a direct, dedicated connection from a node that sits at or near your broker's data centre. Instead of your trading traffic taking whatever route your ISP's transit has chosen today, it takes a specific, uncongested path that was selected for exactly this purpose.

That is the priority route — not a VPN that routes all your traffic through a foreign server, not a VPS that moves your terminal to a remote machine. A routing layer specifically for your trading sessions that keeps the path clean regardless of what your residential ISP is doing at any moment.

How to diagnose your home route
  • Run: ping [your-broker-server-hostname] -n 100 (Windows) or ping -c 100 (Mac/Linux)
  • Note the min, max, and average values — the spread matters more than the average.
  • Run traceroute to see the full hop count and any obvious bottlenecks.
  • Repeat during London open and compare the spread to a quiet-time baseline.
The common misconception

Upgrading your internet plan does not change your route to your broker.

Moving from 100 Mbps to 1 Gbps with the same ISP leaves your route to your broker's data centre identical. The path does not change; only the bandwidth changes. For trading, bandwidth is almost never the constraint — consistency of the route is. A gigabit connection that bounces through inconsistent transit hops produces worse trading fills than a steady 50 Mbps fibre connection with a direct path.

The fix is not more bandwidth. The fix is a better path. That is what the proxy provides.

  • Measure route quality, not download speed.
  • The path to your broker changes based on ISP peering, not your plan tier.
  • A proxy replaces the path, not the bandwidth.
FAQ

Raw download speed rarely matters. A 10 Mbps connection is more than enough for MT4 or MT5. What matters is route quality — the consistency and jitter of the path from your machine to your broker's server.

A traceroute shows every network hop your packets take between your machine and your broker's server. It can reveal inefficient routing, distant hops, and the specific transit networks carrying your trading traffic.

Usually not. Upgrading from 100 Mbps to 1 Gbps does not change your route to your broker. Route quality depends on which transit networks your ISP uses, not bandwidth. A dedicated proxy route changes the path; a faster plan does not.