What is latency (ping) and why it matters for your server
Learn what latency is, how distance and routing affect it, how to measure ping on Windows, Mac and Linux, and when it matters for websites, games, trading and RDP.
- Beginner
- All
- 4 min read
Latency is the delay between sending something over the network and getting a reply. You usually see it as a ping time in milliseconds. Low latency makes a server feel instant; high latency makes every click wait. This guide explains what causes latency, how to measure it, and when it really matters.
Before you start
You need a computer with a terminal or PowerShell and the IP address of a server to test. For your RunRacks server, the IP address is on the service page in your Dashboard. The examples use 203.0.113.10.
What latency is
Latency is usually measured as round-trip time (RTT): how long a small packet takes to reach the server and for the reply to come back. It is different from bandwidth, which is how much data can move per second. A connection can have plenty of bandwidth and still feel slow if latency is high, because many actions need several round trips before anything appears.
Two related terms:
- Jitter: how much latency varies from one packet to the next. Steady is better than fast-but-jumpy for calls, games and RDP.
- Packet loss: packets that never arrive and must be resent, which adds more delay.
What causes latency
- Distance. Signals in fibre are fast but not instant. Crossing a continent or an ocean adds tens of milliseconds or more.
- Routing. Traffic passes through many routers between networks. An indirect route adds distance and hops.
- Your local connection. Wi-Fi, a busy home network or a mobile connection add delay and jitter.
- Congestion. Busy links queue packets at peak times.
- Server load. A heavily loaded server answers more slowly, though this shows up more in app response time than in ping.
How to measure it
Windows
In PowerShell or Command Prompt:
ping -n 10 203.0.113.10macOS and Linux
ping -c 10 203.0.113.10Read the summary at the end. Windows shows Minimum, Maximum and Average. macOS and Linux show min/avg/max/mdev, where mdev is a measure of jitter. Ten or more pings give a fairer picture than one.
See where the delay comes from
To see each hop on the route:
tracert 203.0.113.10On Linux, mtr combines ping and traceroute into a live report:
mtr -rw -c 20 203.0.113.10Some servers and routers do not answer ping. A missing reply does not always mean the server is down.
When latency matters
Websites
Each page load needs several round trips: DNS lookup, connection setup, TLS handshake and the requests themselves. Higher latency adds up across all of them. Caching and a CDN help visitors far from the server.
Remote Desktop
Every keystroke and screen update crosses the network. Low latency makes RDP feel like a local desktop; high latency makes typing and scrolling lag. Choose a location near you.
Trading
The time between your terminal sending an order and the broker receiving it is partly network latency. A VPS near the broker's server keeps that short. MetaTrader shows its ping to the broker in the bottom-right status bar.
Games
Players feel latency directly as lag. Pick a location near most players.
Bots and background jobs
Usually not critical, unless the bot must react in real time.
Check it works
Ping your server from the place that matters, ten times or more, at a normal time and at a busy time. If the average is steady and fits your use, the location is right. If it is high, compare with another location before you build on it. See how to choose a server location.
Troubleshooting
- High ping only on Wi-Fi: test on a cable. Wi-Fi adds delay and jitter.
- Ping fine, but the website is slow: the delay is in the app, database or page size, not the network. Measure server response time instead.
- Ping jumps at certain hours: congestion on your ISP or a busy route. Run
mtrat those times and share the report with support if the problem seems to be near the server. - "Request timed out" on every ping: the server may block ping, be stopped, or be unreachable. Check its status in the Dashboard and test a known open port.
Next steps
- Deeper testing: the ping command guide.
- Trace routing problems: diagnose the network with mtr.
- For traders: reduce latency to your broker.
Was this guide helpful?
Still stuck?
Ask RunRacks AI for a quick answer, or open a ticket and our team will take a look at your server.
Related guides
Networking & DNS
Set your server hostname and reverse DNS
Change the server's hostname, point DNS records at your IP, set reverse DNS in the control panel and check that forward and reverse lookups match.
- Intermediate
- Linux VPS
- 2 min read
Networking & DNS
Reduce latency to your broker: location and ping checks
Find where your broker's trade servers are, choose the nearest location, and measure latency from the VPS with MetaTrader, ping and tracert.
- Beginner
- Admin RDP · Windows VPS
- 3 min read
Networking & DNS
Port speed vs bandwidth: what network specs mean
Learn what port speed in Mbps or Gbps, monthly transfer and real-world throughput mean, so you can read the network specs on any hosting plan with confidence.
- Beginner
- All
- 4 min read