What Is VPS Latency? How to Test It and What’s Good (2026 Guide)
VPS latency is the round-trip time, measured in milliseconds, for a small packet to travel from your VPS to another server and back. You measure VPS latency with two free commands that ship on every operating system: ping for the raw number and traceroute for the path behind it. As a rough guide, under 5 ms is excellent, 5 to 20 ms is very good, and anything past 100 ms starts to feel slow in real-time work like trading or gaming.
That is the short version. Below, you get the test commands, the numbers that actually matter, and the one factor that decides most of your result before you tune a single setting: where your server sits.
What VPS latency actually measures
VPS latency measures delay, not volume. When you click “buy” in MetaTrader or fire a shot in Rust, a tiny packet leaves your VPS, reaches the target server, and comes back. That round trip is your latency. The lower it is, the faster the server hears you.
Latency and bandwidth are not the same thing
People mix these up constantly, so it is worth being clear. Bandwidth is how much data you can move per second. Latency is how long each packet takes to arrive. A trading order or a game input is a tiny packet, so bandwidth barely touches it. Instead, latency does the heavy lifting.
Here is the practical version. A big 10 Gbps connection will not lower your ping, because latency and bandwidth are independent measurements. As a result, buying a bigger plan rarely fixes a lag problem. You need a shorter, cleaner path instead.
How to test VPS latency with ping and traceroute
You do not need paid tools to measure VPS latency. Two commands do the job, and they behave almost identically across Windows, macOS, and Linux.
The ping test gives you the round-trip number
Ping is the fastest check. It sends an ICMP Echo Request to the target, waits for the reply, and reports the round-trip time in milliseconds. Run it from your VPS toward the server you care about, whether that is your broker, your game host, or an API.
- Windows:
ping your-target.com - macOS or Linux:
ping your-target.com
Watch two things, not one. First, the average time tells you the typical delay. Second, the spread between the lowest and highest reply tells you the jitter. A steady 30 ms usually beats a jumpy 15 ms, because consistency is what real-time apps depend on.
The traceroute test shows where the delay hides
Ping gives you a number, but traceroute explains it. It maps the route hop by hop, listing every router the data passes through and the response time at each one. So when a ping looks high, traceroute tells you which leg of the journey is to blame.
- Windows:
tracert your-target.com - macOS or Linux:
traceroute your-target.com
One caveat is worth knowing. Windows uses the shortened command tracert, while Linux and macOS use the full word traceroute, but they do the same job. Firewalls also block these probes sometimes, so a single timed-out hop is not always a real fault.
What counts as good VPS latency
Now for the number everyone wants. Good VPS latency depends on what the server is doing, but the ranges below hold up well across both gaming and trading.
| Round-trip latency | Verdict | What it feels like |
|---|---|---|
| Under 5 ms | Excellent | Co-located trading and top-tier esports. Effectively local. |
| 5 to 20 ms | Very good | Same-region VPS. Smooth for almost every workload. |
| 20 to 50 ms | Solid | Typical fibre. Fluid for most online gaming. |
| 50 to 100 ms | Playable | Casual play is fine, but fast reactions start to slip. |
| 100 ms and up | Noticeable | Real-time apps feel sluggish and inputs lag. |
These bands are not arbitrary. In competitive gaming, industry consensus puts excellent play under 20 ms, with real-time apps starting to feel sluggish past 150 ms. Trading is even stricter, because prices move in milliseconds: a forex VPS in the same city as its broker can reach single-digit latency, while a home line routing across continents commonly sits at 100 to 200 ms. For interactive quality more broadly, the ITU-T G.114 telecom standard names 150 ms one-way as the preferred maximum before delay becomes obvious.
Which VPS latency numbers matter most?
Three numbers, in order. First, the average round-trip time sets your baseline. Second, jitter, the variation between pings, decides how stable that baseline feels. Third, packet loss tells you whether data is arriving at all. A good result stays low on all three, not just the headline ping.
Why your region choice changes VPS latency
Here is the part most guides skip. Before you touch a config file, your VPS latency is mostly decided by distance. That is physics, and no plan can beat it.
Distance sets a hard floor
Light in fibre travels at roughly two-thirds of its vacuum speed. In practice, that works out to about 1 ms of round-trip time per 100 km, and roughly 10 ms per 1,000 km, before a single router is added. So a server 5,000 km from its target cannot dip below about 50 ms of pure travel time, however fast the hardware is. Because of this floor, geography is the first lever you pull, not the last.
Routing and proximity are the part you control
Distance sets the floor, but routing decides how far above it you land. Real fibre does not run in straight lines, and every router adds a little delay. As a result, live latency usually runs higher than the physics floor. The fix is simple to state: put the VPS near whatever it talks to. For a trader, the closer the server is to the broker’s matching engine, the shorter the data path, which is how a same-city VPS reaches single digits while a distant one stalls in the hundreds.
The lesson holds for every use case. A Minecraft server should sit near its players. A forex VPS should sit near the broker. A SaaS backend should sit near its users. In short, region choice is the single biggest latency decision you make, and it costs nothing to get right.
How to reduce VPS latency: a checklist you can run
You do not have to trust any of this on faith. Test it, then act on what you see.
- Ping and traceroute your target from your current setup, and note the average, the jitter, and the hop where time jumps.
- Find where your target actually lives, whether that is your broker’s server city, your players’ region, or your users’ countries.
- Pick a VPS location near that target instead of near yourself, because proximity to the target wins.
- Re-run ping and traceroute from the new region and compare. The improvement should show up immediately.
- If two regions look close, choose the one with fewer hops and steadier times, not just the lowest single ping.
That is the whole method. Because the tools are free and the test takes minutes, anyone can verify a latency claim rather than take it on trust.
Why Rabisu
Rabisu runs VPS locations across multiple regions, so you can place your server near the thing it needs to reach instead of settling for whatever is closest to home. That matters because, as this guide shows, proximity is what moves the ping. Our focus stays on price-to-performance, which means low-latency placement without the enterprise markup. If you want to see the effect yourself, run the ping and traceroute tests above, then try them again from a Rabisu region near your target. Explore our VPS locations to find the closest match, and if you trade, our forex VPS guide walks through broker proximity in detail.
Quick answers
For forex, aim for under 5 ms to your broker, which is the level same-city and co-located servers reach. Between 5 and 20 ms still works well for most strategies. Once you pass 100 ms, slippage risk climbs, especially for scalping and automated Expert Advisors.
Open Command Prompt and run ping your-target.com for the round-trip number, then tracert your-target.com to see each hop. Note the average time and the jitter, and look for the hop where latency suddenly spikes.
No, because bandwidth and latency are separate. A bigger plan moves more data per second, but it does not shorten the distance a packet travels, so your ping stays roughly the same. Shortening the path is what lowers latency.
Under 20 ms is excellent and feels almost local. Between 20 and 50 ms is solid for nearly all online games. Above 100 ms, fast-paced shooters start to feel unresponsive, though slower and turn-based games tolerate more.
Yes, often. A VPS placed near the target server can take a shorter, cleaner route than your home line, which may bounce through several distant hops first. That is exactly why traders and game-server admins run workloads on a well-placed VPS.
Sources and further reading
- Fortinet, “What Is Traceroute: What Does It Do and How Does It Work?” (ping vs traceroute, ICMP behaviour).
- Red Hat, “Ping, traceroute, and netstat: The network troubleshooting trifecta” (round-trip time, TTL, hop-by-hop delay).
- ITU-T Recommendation G.114, “One-way transmission time” (150 ms one-way guidance for interactive quality).
- Speed-of-light-in-fibre propagation is standard optical engineering: about 200,000 km/s, giving roughly 1 ms round-trip per 100 km.