Skip to main content
Trader problem · Diagnose

Why MT4 Keeps Disconnecting Even on a VPS

You bought a VPS, installed MetaTrader, and MT4 is still dropping the connection. The reason is straightforward: a VPS moves the app — it does not move the route.

TL;DR

MT4 needs a persistent TCP connection to your broker's server. Your VPS is in one datacenter. Your broker is in another. The internet hops between them can have packet loss, congestion, and unstable routing — none of which a VPS fixes. The fix is improving the path between the VPS and the broker, not the server the app runs on.

Fix the route — $9/moRead the latency guide
VPS
Moves where the app runs. Does not change the network path to your broker.
Route
The actual TCP path from the VPS datacenter to your broker's matching engine.
Fix
A proxy node co-located near the broker's datacenter cleans the route, not the server.

What a VPS actually does — and what it doesn't

A VPS gives you a virtual machine hosted in a datacenter somewhere in the world. When you install MT4 on it, MetaTrader runs from that machine instead of your home computer. This genuinely solves some problems:

  • Your home internet going down no longer kills the EA
  • Your laptop sleeping no longer drops the connection
  • Power cuts at home don't affect running positions
  • Your MT4 instance runs 24/7 without you

What a VPS does not do is change the quality of the network path between the VPS datacenter and your broker's matching engine. Those are two separate buildings connected by the public internet. The TCP stream that carries your orders still has to traverse that path — and if the path is congested, packet loss is present, or routing is unstable, MT4 will disconnect. The hardware you're running on is irrelevant to that problem.

Myth

"A better VPS with more RAM will fix my MT4 disconnections."

Reality

MT4 disconnects are almost never caused by VPS hardware. A Windows MT4 install uses under 200 MB RAM in steady state. Disconnections are TCP-level events caused by the network path — packet loss, route changes, or congestion between the VPS host and the broker's server. More RAM does nothing for a routing problem.

Myth

"I need a VPS in the same country as my broker."

Reality

Country is too broad. What matters is which Equinix datacenter your broker uses — NY4 (New Jersey), LD4 (London), TY3 (Tokyo), SY4 (Sydney), or SG1 (Singapore). Your VPS can be in "the US" but still 40 ms from NY4 if it's in a different facility. Datacenter-level proximity is what matters, not country.

Diagnose your specific disconnection — 4 steps

Run these from inside your VPS (Remote Desktop into it first).

  1. Find your broker's server hostname
    In MT4: Tools → Options → Server tab. The server address shown (e.g. live.icmarkets.com or ny4-mt4.pepperstone.com) is your broker's server. Note it — you need it for the next steps.
  2. Run a traceroute to the broker's server
    Open Command Prompt inside the VPS and run tracert your-broker-hostname.com. This shows every network hop between your VPS and the broker. Look for hops where latency suddenly jumps by 50+ ms, or hops marked with * * * (packet loss). That is where the problem lives.
  3. Ping the broker's server for 5 minutes
    Run ping -t your-broker-hostname.com for 5 minutes. Watch for: (a) average RTT over 100 ms, (b) high variance (e.g. swings from 20 ms to 200 ms), (c) "Request timed out" lines. Any of these indicate route instability.
  4. Check the broker's datacenter code
    The broker's server hostname often includes the datacenter: ny4 = Equinix New Jersey, ld4 or lon = Equinix London, sg = Singapore, ty = Tokyo, sy = Sydney. Compare this to where your VPS is hosted. If your VPS is in a US datacenter but your broker is on LD4 London, the transatlantic hop is structural — a proxy near LD4 is the only fix that doesn't involve changing brokers.

What actually fixes VPS MT4 disconnections

1

TradersProxy — a relay node near your broker's datacenter

TradersProxy places a proxy node in or adjacent to your broker's Equinix datacenter. MT4 on your VPS connects to the nearby proxy node (short, stable path), and the proxy handles the final hop to the broker — a sub-millisecond link inside the same facility or campus. The long, unstable internet hops are replaced with a purpose-built trading relay. Configure it in MT4 under Tools → Options → Server → Proxy.

2

Choose a VPS datacenter physically close to your broker's DC

If your broker is on Equinix NY4 (New Jersey), a VPS in the same Equinix campus or nearby Secaucus/Newark gets you sub-5 ms to the broker without any proxy. This requires knowing your broker's exact datacenter — not just "New York" but NY4 specifically. Most VPS providers that serve traders advertise this on their product pages.

3

Adjust MT4 reconnect behaviour

This doesn't fix the underlying route problem but makes MT4 recover faster after a disconnect. In MT4: Tools → Options → Server. Increase the reconnect timeout if it's set very low. Some EAs also have their own reconnect logic — review the EA settings for any configurable connection timeout values.

4

Contact your VPS provider about peering to the broker DC

Some trading-focused VPS providers (BeeksFX, ForexVPS, FXVM) specifically advertise Equinix co-location and direct peering to broker matching engines. If your current VPS provider is a generic hosting company with no broker proximity, switching to a trading-specific VPS may solve the route problem entirely — at the cost of moving your setup.

If the route is the problem, a relay node near your broker's datacenter is the fix at the infrastructure level — a relay node co-located near your broker's datacenter replaces the unstable public internet hops with a dedicated path. 7-day trial on Starter →

Why this is "Execution Quality" problem

Most traders think about two layers of infrastructure: their trading platform, and their broker. The platform executes the logic. The broker executes the order. That's the full picture in most traders' mental model.

The missing layer is the network between them. That TCP connection carries every order, every tick update, every position confirmation. If that path is unstable, disconnections happen regardless of platform quality or broker quality — and regardless of whether you're on a VPS or your home machine.

A VPS addresses layer 1 reliability (the platform staying online). TradersProxy addresses layer 3 — the path quality between wherever the platform runs and the broker's matching engine. For an EA running on a VPS with a choppy route to the broker, you need both.

The full explanation of the priority route is worth reading if this problem sounds familiar.

FAQ

Because a VPS only moves where MetaTrader runs — it does not fix the network path between the VPS host and your broker's server. If that path has packet loss, congestion, or unstable routing, MT4 will disconnect regardless of how good the VPS hardware is.

Partly. A VPS eliminates home internet issues, power cuts, and local hardware failures. But it introduces a new path: from the VPS datacenter to your broker's datacenter. If those two datacenters are far apart or poorly connected, the disconnection problem moves rather than disappears.

In MT4, go to Tools > Options > Server tab. The hostname shown (e.g. live.icmarkets.com) is your broker's server. Run a tracert to that hostname from your VPS terminal to see the full network path and where latency is being added.

Run tracert from your VPS to your broker's server hostname. If the disconnect problem is in the route (hops with high latency or packet loss deep in the path), a TradersProxy node co-located near your broker's datacenter fixes the unstable segment. If the problem is in the first 1-3 hops, it is local to the VPS provider.

Yes. TradersProxy works on any machine including a VPS. You configure the proxy settings in MT4 under Tools > Options > Server, point them to your TradersProxy credentials, and the relay handles the path from your VPS to the broker. Many traders run both: VPS for off-site execution, TradersProxy for path quality.