Packet Loss and Jitter: Why They Ruin Live Streaming and How to Fix Them

Sometimes everything looks fine on paper — a fast speed test, a strong Wi-Fi icon — yet live channels still stutter, drop in quality or show blocky patches. Two measurements explain many of these cases: packet loss and jitter. This guide explains both in plain English, shows how to measure them, and how to fix the usual causes of packet loss in streaming.

What packet loss and jitter are

Everything you stream travels as small pieces of data called packets.

• Packet loss is the share of packets that never arrive. Even 1% means one in every hundred is missing.
• Jitter is variation in how long packets take to arrive. Low jitter means a steady flow; high jitter means packets arrive in uneven bursts.

Why they matter for live TV

Most internet streaming resends lost packets automatically. That keeps the picture intact, but every resend costs time. On live channels, where players keep only a small buffer, those delays add up to:

• buffering or spinning wheels,
• quality drops as adaptive players fall back to a lower bitrate,
• freezes while missing data is recovered.

Some delivery methods — such as multicast IPTV inside a broadband provider’s own network — don’t resend lost data, so loss shows up as blocky squares or green flashes instead.

Jitter causes similar symptoms: the player’s buffer drains and refills unevenly, so playback pauses even when average speed is high.

How to measure them

Use a test that reports them

Some speed tests report jitter, and some report packet loss or “loaded latency”. Run them at the TV and at busy times, as described in our guide to testing internet speed for streaming.

Use the ping command on a computer

Ping sends small test packets and reports how many come back and how long they take.

• Windows: open Command Prompt and run ping -n 100 8.8.8.8
• Mac or Linux: open Terminal and run ping -c 100 8.8.8.8

At the end, note the percentage lost and the spread between minimum and maximum times. Run it twice:

1. To your router (its address is often 192.168.0.1 or 192.168.1.1) — tests your home network.
2. To an internet address such as the example above — tests the whole path.

Router test	Internet test	Likely location of the problem
Loss	Loss	Inside your home (Wi-Fi, cables, router)
No loss	Loss	Your broadband line or provider
No loss	No loss	Not packet loss — look elsewhere

Common causes and fixes

Wi-Fi interference and weak signal

The most common cause inside the home.

• Move to 5 GHz or use Ethernet.
• Move the router to a central, open position.
• Let the router choose the least crowded channel.
• Add a mesh node or powerline adapter for distant TVs.

Faulty cables and ports

• Replace old or damaged Ethernet cables.
• Try a different port on the router.
• Check the router’s cable to the broadband socket.

An overloaded router

• Restart the router.
• Update its firmware.
• Use quality of service or smart queue management if available, to keep busy downloads from swamping streams.
• Consider replacing a very old router.

Busy network at peak times

Jitter often rises when the household is busy. Schedule big downloads and backups overnight, and see our home network checklist for streaming for planning busy evenings.

The broadband line or provider

If loss appears on wired tests from the router to the internet — and not to the router itself — contact your internet provider with your results, including dates and times.

Find where loss starts with traceroute

Traceroute lists each “hop” between you and an internet address:

• Windows: tracert 8.8.8.8
• Mac or Linux: traceroute 8.8.8.8

If delays or timeouts start at the first hop (your router), the problem is at home. If they start a few hops later and continue to the end, the issue is further along the path. Interpret it carefully: some routers on the internet deliberately respond slowly to these tests while passing normal traffic quickly, so a single slow hop in the middle isn’t proof of a problem. Look for loss that starts at one hop and continues to the destination.

Check your modem’s line statistics

Many broadband routers and modems show line statistics — error counts, signal quality and resynchronisations — in their admin pages. Frequent resyncs or rising error counts point to a line fault that your internet provider needs to investigate. Note them along with your ping results when you call.

A worked example

A viewer’s IPTV freezes every few minutes on the bedroom TV. Ping from a laptop next to the TV, over Wi-Fi, shows 4% loss to the router; the same test with a cable at the router shows none. The problem is the Wi-Fi path. Moving the TV to 5 GHz and adding a mesh node brings loss to zero, and the freezes stop. For more fixes when freezing persists, see why IPTV keeps freezing.

The bottom line

Packet loss and jitter explain many “fast but still stuttering” connections. Measure them at the TV, compare tests to the router and to the internet, and you’ll know whether to fix your Wi-Fi, cables and router — or call your provider.