Ping, Latency and Packet Loss Explained: Why Calls and Games Lag

Originally published on CodingCush.

Your video call freezes, your game character teleports, and someone says "my ping is bad". Here is the simple truth: ping measures how long a tiny message takes to travel to a server and back, latency is that travel time, and packet loss means some messages never arrive at all. A fast download speed cannot fix high latency or packet loss, because they are about the quality of the trip, not the size of the road. This guide explains all three in plain words, shows the numbers that are actually good, and lists the fixes that really work when calls and games lag.

Imagine sending letters. Download speed is how many letters fit in the truck. Latency is how long one letter takes to arrive. Packet loss is letters falling off the truck on the way. A bigger truck does not help if the road is long or the letters keep falling off.

Latency: The Travel Time of Your Data

Latency is the time, in milliseconds (ms), for data to go from your device to a server and back — the round trip. Light itself sets a hard limit: a server on another continent simply cannot answer as fast as one in your own city. Cloudflare's learning centre gives a clear technical walkthrough in its guide on what latency is and what causes it. For everyday use, remember these rough bands: under 30 ms feels instant, 30–60 ms is fine for almost everything, 60–100 ms is noticeable in fast games, and above 150 ms video calls start talking over each other and games feel like they are ignoring you on purpose.

Latency comes from distance, from every router your data hops through, from busy networks queuing your packets like cars at a toll booth, and from Wi-Fi retransmitting data that got garbled in the air. You cannot beat physics, but you can remove the avoidable delays — which is what the fixes below do.

Ping: The Tool That Measures Latency

Ping is both the test and the number it reports. When you run ping google.com in a terminal, your computer sends small ICMP echo requests and times each reply. Games and call apps show "ping" as a live score for the same round-trip idea. One odd high reading means nothing; what matters is the pattern. If your ping sits at 25 ms and suddenly jumps to 400 ms every few seconds, that jumping — called jitter — is often worse than a steady 80 ms, because calls and games can adapt to steady delay but not to surprises. The history and details of the ping utility are on Wikipedia if you enjoy knowing where your tools came from.

Cloudflare's Learning Centre explains latency — the round-trip travel time of your data.

Packet Loss: The Messages That Never Arrive

Data travels in small chunks called packets. Packet loss means some chunks never reach the other side. At 1–2% loss a call sounds robotic and a game stutters; at 5% or more, everything feels broken. The Wikipedia article on packet loss lists the main causes: congested links dropping packets, faulty hardware, weak Wi-Fi signals and overloaded routers. Here is where protocol choice matters: some traffic resends lost packets and some does not. Our comparison of TCP vs UDP explains this in simple words — TCP resends, so a lost packet becomes a delay; live calls and games mostly use UDP-style delivery, so a lost packet becomes a glitch you can hear and see.

That is also why a speed test can look perfect while your call is awful. Speed tests measure big downloads over TCP, which patiently resends everything. They politely hide the packet loss that is ruining your live traffic.

Why Calls and Games Suffer First

Streaming video survives bad networks because it buffers — it downloads the next 30 seconds while you watch the current ones. Calls and games cannot buffer the future. A game must know where you moved now, and a call must play your voice now. So they expose every network flaw instantly: high latency makes actions feel late, jitter makes speech chop in and out, and packet loss erases syllables and teleports players. If Netflix is smooth but your meeting is not, your network is not "fine" — it is fine for buffered things only. The journey your data takes before any of this, by the way, starts the moment you open the app — our guide to what happens when you type a URL covers that first trip in friendly detail.

How to Check Your Own Numbers

Run ping 8.8.8.8 in a terminal for a minute. Read three things: the average time (latency), the spread between lowest and highest (jitter, roughly), and the "packet loss" percentage at the end. Then run the same test plugged into the router with a cable. If the cable numbers are dramatically better, your Wi-Fi is the problem, not your internet plan. Test at different times of day too — a connection that is perfect at 10 am and terrible at 8 pm is suffering from neighbourhood congestion, which no router setting can fully cure.

Fixes That Actually Help

Use a wired connection for calls and games whenever possible — this single change fixes more lag than every other tip combined. If Wi-Fi is unavoidable, move closer to the router, use the 5 GHz band, and keep the router out of cupboards and away from thick walls. Restart the router occasionally. Close heavy background uploads and cloud backups during calls — one phone backing up photos can eat the whole upload side of a home connection. In games, choose the nearest server region, even if your friends picked another one; geography is not negotiable. And if your router offers SQM or QoS settings, enabling them stops one big download from making everyone else's packets queue behind it — the famous "bufferbloat" fix.

Quick Reference: Good and Bad Numbers

Keep this little table in mind when you test. One number alone rarely tells the whole story — a 40 ms ping with 8% packet loss feels far worse than a steady 90 ms ping with zero loss. Games and call apps quietly agree: they would rather have your data arrive slightly late than not arrive at all, which is exactly why wired connections, with almost no loss, feel so much better than their speed numbers suggest.

Frequently Asked Questions

What is a good ping for gaming?

Under 30 ms is excellent, 30–60 ms is good, and up to 100 ms is playable for most games. Fast competitive shooters feel best below 50 ms. Consistency matters as much as the average.

Why is my ping high but my download speed is fast?

Because speed and latency are different things. Speed is bandwidth — how much data fits per second. Latency is travel time. A wide, long road moves many cars slowly; a narrow, short road moves fewer cars quickly.

How much packet loss is acceptable?

Zero is ideal. Under 1% is usually unnoticeable, 1–2% causes small glitches in calls, and anything above 5% makes calls and games clearly broken.

Does a VPN increase ping?

Almost always, yes. Your data takes a detour through the VPN server, which adds distance and processing. A nearby VPN server adds a little; a far one adds a lot.

Why does my ping spike at night?

Evening congestion. Everyone in your area streams and downloads at once, queues grow at your provider's equipment, and latency plus jitter climb until traffic calms down.

Conclusion

Ping is the measurement, latency is the travel time, and packet loss is data that never arrives. When calls and games lag, do not ask "is my speed fast?" — ask "what are my ping, jitter and loss, on Wi-Fi versus cable?" Test, wire up if you can, pick nearby servers, and tame background uploads. Your future self, mid-meeting and mid-match, will notice the difference immediately.