“London server” is one of the most repeated phrases in forex marketing, and one of the least explained. Brokers advertise it. VPS providers advertise it. Almost none of them tell you what it actually means, and the phrase gets used loosely enough that two providers both claiming “London” can sit tens of kilometers apart with a meaningfully different latency profile to your broker. This guide breaks down what “London” really refers to in this industry, why it usually means one specific postcode rather than the city itself, and how to confirm you are actually getting what was advertised.
”London” Usually Means One Building in Slough
When a forex broker or VPS provider says “London datacenter,” they are very rarely talking about a facility inside Greater London. The overwhelming majority of European forex infrastructure sits in Equinix LD4, a data center campus in Slough — a town about 20 miles west of central London, near Heathrow Airport. LD4’s sister facility, LD5, sits on the same campus and hosts a substantial share of the same broker and liquidity-provider infrastructure.
📊 Key Stat: The LD4/LD5 campus in Slough houses matching engines and trade servers for the majority of UK- and Europe-regulated retail forex brokers, along with major liquidity providers and prime brokers. When a broker says “London server,” this campus is what they almost always mean — not a building inside the M25.
This matters because “London” as a city covers roughly 600 square miles. If your VPS is genuinely somewhere in London but not inside Slough’s Equinix campus (or directly interconnected to it), your latency to a broker hosted in LD4 can be materially worse than a VPS that is honest about being in Slough but is physically inside the same building as the broker’s servers.
LD4 vs LD5: Does It Matter Which One?
For most practical purposes, no. LD4 and LD5 are cross-connected campus facilities — traffic between the two travels over dedicated fiber within the same physical site, adding a fraction of a millisecond at most. A broker in LD5 and a VPS in LD4 (or vice versa) will still see latency in the low single-digit milliseconds, effectively indistinguishable from being in the exact same building.
What does matter is whether your VPS provider is inside the Equinix campus at all, versus claiming “London” while actually running infrastructure elsewhere in the region and relying on standard internet routing to reach LD4/LD5. That distinction is the entire ballgame.
⚠️ Warning: A VPS provider advertising “London” from a facility outside the Equinix LD4/LD5 campus can still show reasonable-looking ping times in isolation — but “reasonable” (10-20ms) is not the same as colocated (1-3ms), and the gap compounds under load, during news volatility, and on every single trade over the life of your account.
How to Verify What You’re Actually Getting
Marketing copy is not proof. Here is how to confirm your VPS location claim independently.
1. Check the IP’s registered location. Run a WHOIS lookup or an IP geolocation check on your VPS’s public IP address. Legitimate Equinix LD4/LD5 infrastructure typically resolves to netblocks registered to Equinix or a colocation tenant with a London/Slough address.
2. Run a traceroute to your broker’s trade server. From your VPS, run tracert (Windows) to your broker’s server address. A genuinely colocated VPS shows 1-3 hops to a broker in the same facility. A VPS elsewhere in the region, routing over the public internet, typically shows significantly more hops and higher latency.
3. Compare the ping your platform reports against independent numbers. MT4 and MT5 both display a latency reading in the terminal’s status bar. Cross-check that number against your own ping test to the same server address — they should be close. A large, persistent gap between platform-reported latency and your own network-level ping can indicate a data-quality or routing issue worth investigating with your provider.
💡 Tip: FXVPS publishes real-time, measured latency data for 195+ brokers from each of our datacenter locations on our broker latency page. Check your specific broker before signing up rather than relying on either party’s marketing claim.
The Same Pattern Applies to Every “City” Claim
London is the clearest example because the Slough/London naming gap is so large, but the same logic applies everywhere:
- “New York” almost always means Equinix NY4 in Secaucus, New Jersey — not Manhattan.
- “Tokyo” typically means Equinix TY3, in the greater Tokyo metro area.
- “Chicago” for futures traders means the Equinix campus at 350 East Cermak Road, not just anywhere within city limits — and the actual CME matching engine sits further out, in Aurora, Illinois. Our Why Chicago Matters for Futures Traders guide covers that distinction in detail.
Every one of these city names is industry shorthand for a specific building or campus, not a metro-area guarantee. Treat any location claim as a starting point to verify, not a fact to accept.
Why This Gap Costs Real Money
The difference between genuine colocation and “in the general region” is not academic. A VPS inside LD4 reaching a broker in the same facility sees round-trip latency in the 1-5ms range. A VPS elsewhere in the London area, routing over standard internet paths back into LD4, commonly sees 10-30ms or more, with worse consistency (jitter) under load.
📊 Key Stat: On a scalping strategy targeting a few pips per trade, the difference between 3ms and 20ms of latency can account for a meaningful share of your edge per trade — see our VPS vs Local PC latency benchmarks for measured numbers on how latency translates into slippage.
For EA traders and scalpers, that gap shows up as worse fills on every single trade, all month, every month. For swing traders holding positions for days, the gap matters far less — which is worth factoring into how much you should pay for guaranteed colocation versus a cheaper regional alternative.
Where FXVPS Actually Sits
FXVPS operates dedicated servers physically inside Equinix LD4 for our London location, alongside NY4 in New York, TY3 in Tokyo, and HK1 in Hong Kong — 15+ locations in total. When we say London, we mean the same Slough campus that hosts the trade servers for the majority of UK and European forex brokers, not a datacenter somewhere in the wider region.
✅ Best Practice: Don’t take any provider’s location claim, including ours, purely on faith. Run the verification steps above on a trial before committing to a monthly plan — it takes ten minutes and removes all doubt.
Recommended Next Step
If you are unsure whether your current VPS is genuinely colocated with your broker, the fastest way to find out is to compare it directly against a known-colocated alternative. Spin up a $1.99 seven-day trial in the location matching your broker, run the traceroute and ping tests above, and compare the numbers side by side with what you currently get.
Frequently Asked Questions
Is Equinix LD4 actually in London?
No. LD4 is in Slough, roughly 20 miles west of central London. “London server” is industry shorthand for this campus, not a literal claim about being inside the city.
Does it matter if my VPS is in LD4 and my broker is in LD5?
Not meaningfully. LD4 and LD5 are cross-connected facilities on the same campus, and latency between them is a fraction of a millisecond — effectively the same as being in the identical building.
How do I find out which datacenter my broker actually uses?
Check your broker’s own disclosures first, then verify independently with a traceroute to your broker’s trade server address once connected. Our broker latency page also publishes measured data for 195+ brokers.
Can a VPS outside LD4 still be “good enough” for London-routed brokers?
For swing and position traders, possibly. For EA traders, scalpers, and news traders, the latency gap between genuine colocation and “somewhere in the region” is large enough to affect fill quality on every trade — verification is worth the ten minutes it takes.
Related Reading
- Tips for Choosing the Best VPS Location for Trading — the broader framework for matching VPS location to broker
- VPS vs Local PC: Real Latency Benchmarks — measured latency numbers and their real cost in slippage
- Why Chicago Matters for Futures Traders — the same “city name vs actual facility” distinction for futures
- Low Latency FX VPS — a broader look at what drives latency beyond just datacenter choice