Bandwidth, latency and ping explained
People often say "my internet is fast, so why is my game laggy?" The answer is that speed is not one number. Bandwidth, latency, jitter and packet loss are different things, and games and servers care about them in different ways. Once you can tell them apart, you can work out whether a problem lies with your connection, the route to the server or the server itself.
Bandwidth: how much
Bandwidth is how much data a connection can carry per second, measured in megabits per second (Mbps). Think of the width of a pipe. A wide pipe lets a lot through at once, which matters for downloading large files and streaming video.
Multiplayer games use surprisingly little. Most send a few tens of kilobits to a few megabits per second per player. A fast connection will not make a game feel more responsive if the problem is something else.
Bandwidth matters more on the server side. A server sends data to every connected player, so traffic grows with the player count and with how much the game sends. A busy community server needs a decent allowance, which is why plans list network limits. A web server that serves large files or video needs much more.
Latency: how long
Latency is the time a message takes to travel to the server and back, measured in milliseconds (ms). This round trip time is what games call ping. It is the length of the pipe, not the width. Even a very wide pipe has delay.
Latency has a physical floor set by distance and the speed of light in fibre, plus extra time for each router along the way. That is why server location matters. See How to choose a server location.
You can measure it from your computer:
ping server-address
Look at the time= value. Try it several times, since a single result can mislead.
Jitter: how steady
Jitter is the variation in latency from one packet to the next. A connection averaging 40 ms that swings between 20 and 120 ms feels worse than a steady 60 ms. Games predict movement based on regular updates, so uneven timing causes stuttering and rubber-banding.
Common causes include Wi-Fi interference, a busy home network, and congestion on the route. The ping summary shows the min, average, max and deviation. A big gap between min and max is a hint.
Packet loss: how reliable
Data travels as small packets. Packet loss is the percentage that never arrive. Even 1 to 2 percent can cause visible problems in real-time games, because the missing updates leave gaps. Web pages tolerate loss better, because the missing parts are simply resent, only slower.
Loss usually points to a faulty cable, weak Wi-Fi, an overloaded router or a congested link somewhere on the path.
Putting them together
| Term | Plain meaning | Matters most for |
|---|---|---|
| Bandwidth | Size of the pipe | Downloads, streaming, busy servers |
| Latency (ping) | Delay of a round trip | Fast games, voice calls |
| Jitter | Unevenness of delay | Smooth movement, voice quality |
| Packet loss | Data that goes missing | Real-time games, calls |
A connection can be strong in one and poor in another. A satellite link may have great bandwidth and awful latency. A busy shared line may have good latency at midnight and terrible jitter at 8 pm.
Server lag is different
Network problems are not the only source of lag. A server can be overloaded and slow to process the game, even when the network is perfect. The symptoms differ:
- Network lag: your own actions are delayed, and other players may look fine. Ping is high or unstable.
- Server lag: everyone sees the same stutter, mobs or objects freeze for all, and chat is delayed together. Ping may be low while the server's tick rate drops.
To check for server lag in Minecraft, see Understanding TPS and MSPT. For general fixes, read How to fix server lag.
How to improve your side
- Use a wired connection instead of Wi-Fi when you can.
- Close heavy downloads and streams on the same network while playing.
- Restart your router now and then, and keep its firmware current.
- Move closer to the router or use a better channel if you must use Wi-Fi.
- Check with your internet provider if you see steady packet loss.
- Pick a closer server if the route itself is long.
How to diagnose the route
A trace shows each hop between you and the server, and where delay or loss starts:
tracert server-address (Windows)
traceroute server-address (macOS and Linux)
For a continuous view, mtr combines ping and traceroute. A single hop with high loss that disappears at later hops is usually harmless, because some routers ignore these probes. Loss that continues to the end is the real problem. Fix high ping and packet loss goes through the steps in order.
Servers and the network
If you run a server, the network pieces to watch are your plan's bandwidth, the data centre's connection to major providers and your location. Heavy attacks can saturate a link, which looks like extreme loss for everyone. See DDoS attacks explained.
Rule of thumb
If speed tests look fine but a game feels bad, suspect latency, jitter or loss before bandwidth. Measure ping over time, test with a wired connection and compare with other players. That evidence also makes a support request far more useful. See How to write a support request.
Still stuck? Open a ticket on Discord - run /ticket in any channel, pick a department, and include your Server ID or Invoice ID so we can jump straight in.