Packet Loss, Jitter & Latency: The Three Network Problems That Aren’t “Slow Internet”

Sam Watanuki / Updated Jun 26, 2026 | Pub. Jun 01, 2026

Home - Blog - Packet Loss, Jitter & Latency: The Three Network Problems That Aren’t “Slow Internet”

Table of Contents

Your speed test says 300 Mbps. Everything looks fine. And yet your game is rubber banding, your voice keeps cutting out on Zoom, and your video call freezes before lurching forward. The culprit isn’t your download speed, though. It’s packet loss, jitter, or latency: three separate network problems that most speed tests don’t accurately measure, and that most “slow internet" guides never address.

Here’s how to tell them apart, test for each one, and fix what’s actually broken.

[search_block]

What Is Latency?

Latency is the time it takes for a single packet to travel from your device to a server and back, measured in milliseconds (ms). Think of it like shouting across a canyon and waiting for the echo. That delay is latency. The further the canyon, the longer the wait.

Latency	Experience
Under 20ms	Excellent — imperceptible delay
20–50ms	Good — fine for gaming and calls
50–100ms	Noticeable — slight delay on voice
100ms+	Problematic — real-time apps suffer

High latency makes games feel sluggish. You press a button and watch it happen a half-second later. A high latency fix typically means connecting via ethernet, choosing game servers geographically closer to you, or switching to a provider with better routing infrastructure.

What Is Packet Loss?

Packet loss is the percentage of data packets sent that never arrive at their destination. Imagine mailing 100 letters and having five go missing/. The post office (your ISP) lost them. That 5% disappearance rate is catastrophic for real-time applications.

What causes packet loss? The most common culprits are faulty or aging cables, failing modems, WiFi interference, and congestion on your ISP’s infrastructure [1]. When a TCP-based app loses a packet, it retransmits, adding delay. When a UDP-based app (like most online games) loses a packet, it simply skips it, which is why you see rubber banding internet gameplay and teleporting characters.

Industry standards recommend a packet loss rate below 0.5% for gaming and below 1% for VoIP. Even at 1–2%, packet loss produces choppy audio and frozen video [2]. Understanding packet loss vs latency is important: high latency is a consistent delay, while packet loss creates random gaps. You can have low latency and high packet loss simultaneously, but each requires a different fix.

What Is Jitter?

Jitter is the variability in latency between successive packets. If latency is your average commute time, network jitter is how wildly that time varies day to day. If one packet takes 15ms and the next takes 120ms, that 105ms swing is jitter [3].

Jitter vs latency: You can have low average latency, but severe jitter. Packets are generally fast, but arrive bunched or out of order. Real-time apps depend on consistent timing, so even moderate jitter causes the voice cutouts internet users describe as “choppy" or “robotic."

Jitter	Experience
0–10ms	Excellent
10–30ms	Acceptable for most use cases
30ms+	Noticeable voice cutouts and video stuttering

Symptom-to-Problem Mapping

Symptom	Most Likely Cause
Rubber banding / teleporting in games	Packet loss or latency spikes
Voice cutting out on calls	Jitter or packet loss
Video call freezes then jumps forward	Jitter
Game feels delayed but smooth	High latency (not packet loss)
Lag spikes at random intervals	Packet loss or intermittent jitter
Download speeds fine, calls still bad	Jitter or upload-side packet loss
Only bad at night / peak hours	Congestion-based latency or ISP throttling

How to Test: Ping, Packet Loss Test, and MTR

The simplest packet loss test is a sustained ping. Open a command prompt or terminal and run:

Windows: ping -n 100 8.8.8.8
Mac/Linux: ping -c 100 8.8.8.8

This sends 100 packets to Google’s DNS server and reports how many were lost, along with min/avg/max round-trip times. Any packet loss above 0% is worth investigating. Always also ping the specific server you’re having trouble with. Problems can be path-specific and won’t always appear against a general endpoint.

The MTR Test: The Complete Picture

The MTR test (My Traceroute) is the gold standard for diagnosing network path issues. It combines ping and traceroute, showing every hop between your device and a destination, along with latency and packet loss at each hop, updating in real time [4].

Windows: Download WinMTR from winmtr.net (free, no installation) [5]. Enter your target IP, run for at least 5–10 minutes, and copy results as text to share with ISP support.
Mac: brew install mtr, then sudo mtr –report-cycles 100 8.8.8.8
Linux: sudo apt install mtr, then sudo mtr –report-cycles 100 8.8.8.8

Packet loss that starts at a specific hop and persists through all subsequent hops indicates the problem originates there. If the trouble appears at hops 2–5, that’s within your ISP’s own infrastructure. That’s their problem to fix. Some routers do deprioritize ICMP packets without dropping real traffic, so loss that only appears at an intermediate hop and clears by the final destination is usually a false positive.

Testing Jitter Specifically

Ookla’s Speedtest at speedtest.net includes a jitter measurement [6]. Run it during the problem period and note the figure. For more precision, run a 200-packet ping and compare the minimum vs. maximum round-trip times. PingPlotter (free tier at pingplotter.com) provides a visual graph over time that makes jitter patterns immediately visible [7].

How to Fix Each Problem

Problem	Common Causes	Fixes
High latency	Distance to server, WiFi overhead, congestion	Use ethernet, choose closer servers, upgrade provider
Packet loss	Faulty cables, WiFi interference, ISP congestion	Replace cables, switch to ethernet, restart modem, contact ISP
Jitter	WiFi instability, congestion, ISP peering issues	Use ethernet, enable QoS on router, schedule downloads off-peak

How to fix packet loss starts with the simplest step: swap WiFi for a wired ethernet connection. A surprising percentage of reported packet loss disappears immediately. If it persists on a wired connection, test each cable individually, power-cycle your modem, and check for firmware updates. If the issue only appears at certain times, document it with MTR results before calling your ISP.

man frustrated with bad internet call connection

Bufferbloat: The Hidden Jitter Culprit

Bufferbloat is a form of self-inflicted jitter caused by your router’s upload buffer filling up during heavy transfers (a large upload in the background, for example), causing real-time traffic like voice and gaming packets to queue behind it. Your speed looks normal, but latency balloons unpredictably.

The fix is enabling SQM (Smart Queue Management) or the CAKE algorithm on your router, which keeps queue sizes short and prioritizes real-time traffic [8]. Routers running OpenWrt, ASUS Merlin firmware, or pfSense support SQM natively. Basic QoS prioritization available in most consumer routers is a worthwhile fallback.

When to Call Your ISP (or Switch Providers)

If your MTR test shows consistent packet loss within your ISP’s own network (hops 2–6 from your modem), you have documented evidence. The most effective framing when you call is to say, “I ran an MTR test and I’m seeing X% packet loss at hop 3, which is within your network." That’s far more actionable than “my internet is slow."

That said, some packet loss and jitter are symptoms of an oversubscribed cable node or aging DSL copper that troubleshooting won’t fix. If issues persist after engaging your ISP, it may be time to compare internet providers in your area. Among the best internet providers for low-latency performance, fiber consistently outperforms cable and DSL because it doesn’t degrade with distance or suffer from shared-node congestion.

Use the zip code tool below to compare internet plans, evaluate internet prices, and do a full internet comparison of the best internet in your area.

[search_block]

FAQs

Can I have packet loss even when my speed test shows normal speeds?

Yes. Speed tests measure sustained throughput, which tolerates small amounts of packet loss. A standard test won’t flag 1–3% loss, but that same rate causes noticeable rubber banding and choppy calls. Use a sustained ping or MTR test for an accurate picture.

Is packet loss or jitter worse for online gaming?

Both are damaging but in different ways. Packet loss causes sudden teleportation or desync because a critical update was never received. Jitter causes an unstable, stuttering feel with inconsistent hit registration. Most competitive players find packet loss more disruptive, since even 1% can produce visible in-game errors.

Does WiFi cause jitter?

Yes — WiFi is one of the leading causes of home network jitter. Wireless signals share spectrum with neighboring networks and household devices, introducing variable delays. Switching to wired ethernet almost always reduces jitter significantly.

Will upgrading my internet speed fix packet loss or jitter?

Not necessarily. These problems are usually caused by congestion, faulty hardware, or routing issues — not raw speed. However, upgrading to a different type of connection, particularly fiber, often resolves them, since fiber is far less susceptible to the congestion-related problems that plague shared cable networks.