Home › Learn › Tutorials

How to Keep MetaTrader Running 24/7 on a VPS

Updated 14 July 2026 · 8 min read · PipTax education

Running MetaTrader on a VPS is the standard way to keep expert advisors and pending orders working around the clock, without leaving your home PC on and hoping your internet doesn't drop. This guide covers picking a location, measuring real latency, hardening remote access, and setting things up so MetaTrader genuinely runs unattended — plus an honest look at what "low latency" actually changes for a retail trader.

Why Run MetaTrader on a VPS at All

A Virtual Private Server is a remote Windows machine you rent, install MetaTrader on, and connect to via Remote Desktop (RDP). Once it's set up, it keeps running whether your laptop is on, asleep, or off.

Reasons traders use a VPS:

• Uptime — an EA or pending order stays live 24/5 without depending on your home broadband or power supply.
• Fewer disconnects — data centres have redundant power and network links that a home router doesn't.
• Consistent execution timing — a server that's always awake and always connected removes the "my laptop was asleep" failure mode.
• Location control — you can choose a VPS physically closer to your broker's trade servers than your home connection ever could be.

What a VPS does not do is improve your spread, commission, or the price your broker fills you at. Those are commercial terms — check them properly using the cost tool at /audit.html rather than assuming a fast VPS buys you a better deal.

Choosing a VPS Location: Proximity Matters

Latency is mostly a function of physical distance and network hops, so where your VPS sits matters more than its CPU spec for most retail EA use cases.

Many FX liquidity venues and broker infrastructure cluster around a handful of major data centre hubs — Equinix LD4 in Slough is one of the best known, hosting infrastructure for numerous London-linked trading venues and brokers. If your broker's trade servers are hosted in or near London (common for UK-regulated firms), a VPS in or very near London is usually the sensible default.

Practical steps:

1. Ask your broker (or check their platform/server list) roughly where their trade servers are hosted — Pepperstone's MetaTrader server list and IG's platform documentation both give you server names you can look up. 2. Choose a VPS provider with a data centre in that same city or region. 3. Avoid picking a VPS location based on price alone — a cheap VPS on another continent from your broker's servers can add far more delay than it saves. 4. If you trade with brokers in multiple locations, consider whether you need separate VPS instances near each.

Measuring Real VPS-to-Broker Latency

Don't trust a VPS provider's marketing latency figures — measure it yourself once MetaTrader is installed and connected.

In MetaTrader (MT4/MT5):

• Open the Journal tab and look at the ping value shown next to your connection status (usually in milliseconds).
• Right-click the account in the Navigator, choose properties or check the terminal's connection status bar — MT5 typically shows ping directly.
• Watch this over a session, not just once — a single low reading can be a fluke.

From Windows, inside the VPS:

• Use ping against your broker's trade server hostname (found in your account/server settings) to check average round-trip time and packet loss.
• Use tracert (tracert servername) to see the network hops between your VPS and the broker, which helps explain why latency might be higher than expected — extra hops through unrelated regions is a red flag.

What to look for:

| Reading | What it suggests | |---|---| | Consistent low ping, few hops | VPS is well-placed relative to broker infrastructure | | High ping, many hops | VPS location or provider routing is working against you | | Variable/spiky ping | Network congestion — worth trying a different VPS provider or plan |

Hardening Remote Access Before You Leave It Running

A VPS running MetaTrader unattended, reachable over the open internet via RDP, is a target if you don't lock it down.

• Use a strong, unique password — not the one you use anywhere else.
• Change the default RDP port (3389) to reduce automated scanning hits, and note the new port for your own connection setup.
• Restrict RDP access by IP where your provider's firewall allows it, so only your own connections are accepted.
• Enable your VPS provider's firewall and close every port you don't explicitly need.
• Keep Windows updated — apply security patches on a schedule rather than never.
• Use two-factor authentication on your VPS provider account itself, separate from the Windows login.

None of this is exotic — it's the same basic hygiene as securing any remote machine, but it's easy to skip when you're focused on getting an EA running.

Setting Up MetaTrader for True 24/7 Operation

Getting MetaTrader onto the VPS is the easy part; making it survive reboots and reconnect automatically is what actually delivers "24/7."

• Enable auto-login on the VPS so Windows doesn't sit at a login screen after a restart waiting for you.
• Add MetaTrader to the Windows Startup folder (or Task Scheduler) so the terminal launches automatically after any reboot.
• Enable "Allow automated trading" and any relevant EA settings so your expert advisor resumes without manual re-ticking of boxes.
• Turn off Windows automatic reboots for updates on an unpredictable schedule — schedule your own update window instead.
• Test a full reboot deliberately — restart the VPS yourself and confirm MetaTrader and your EA come back up cleanly, rather than assuming it will work.
• Keep a note of your login details somewhere secure but accessible, since 3am reconnects do happen.

What Low Latency Does and Doesn't Buy You

This is the part worth being honest about. A well-placed VPS can shave meaningful milliseconds off the trip between your terminal and your broker's server. But "sub-millisecond" marketing language usually describes the distance between servers inside a data centre, not what a retail trader experiences end to end.

For most retail accounts, the bigger factors in your actual trading outcome are:

• Your broker's spread and commission — see live comparisons via /audit.html.
• Order handling and bridge technology — how your broker routes retail orders to liquidity, which varies by execution model.
• Slippage during news or thin liquidity — often dwarfs any latency saving from VPS placement.

A VPS near Equinix LD4 helps you get a clean, fast, reliable connection to brokers like Pepperstone or IG — it does not turn a retail account into an institutional co-located one. Treat MetaTrader on a VPS as an uptime and reliability tool first, and a minor latency improvement second.

Conclusion

Setting up MetaTrader on a VPS properly means choosing a location close to your broker's servers, measuring latency yourself with the Journal and ping/tracert rather than trusting marketing claims, locking down RDP before leaving it unattended, and configuring auto-start so a reboot doesn't quietly kill your EA. Do that, and you get a genuinely reliable 24/7 setup — just don't expect it to replace checking your actual trading costs, which is what the cost tool at /audit.html and the broker pages at /brokers/index.html are for.

Keep going: Audit Index Methodology Index