Network reliability

How to Reduce Packet Loss: Diagnose and Fix

Packet loss is the silent killer of video calls, gaming sessions, and remote work. Use this guide to confirm loss is real, isolate where it happens, and apply the fix that matches the root cause.

Quick summary

  • Confirm packet loss with a sustained ping, not a single test.
  • Use traceroute to find the hop where loss starts.
  • Loss on the first hop = your LAN. Loss past hop 3 = upstream.
  • Wi-Fi retransmissions look like loss to applications.

What packet loss actually is

Every connection sends data as packets. When a packet doesn't arrive (or arrives corrupted), it has to be retransmitted. Real-time protocols like UDP can't wait, so the missing data is simply gone — that's what causes audio dropouts, blocky video, and rubber-banding in games.

Where loss typically originates

  • Wi-Fi — interference, distance, channel congestion.
  • Cable / DSL line — physical signal issues to the modem.
  • ISP aggregation — oversubscribed links during peak hours.
  • Transit / peering — congestion between ISPs.
  • Destination server — overloaded host dropping inbound packets.

Practical fixes by location

  • LAN: Switch to 5 GHz, move closer, or use ethernet.
  • Modem: Check coax/DSL signal levels; replace bad cables.
  • ISP: Submit a ticket with timestamped traceroute output.
  • Application: Use a server closer to you (region selection).

Troubleshooting workflow

Run through these steps in order. Each step links to the right diagnostic tool.

  1. 1

    Measure loss to a known-good host

    Sustained ping to 1.1.1.1 or 8.8.8.8 to baseline.

    Open HTTP Ping
  2. 2

    Trace the path

    Find the first hop where loss appears.

    Open Traceroute
  3. 3

    Compare to the destination

    Run the same test against the host you actually care about.

    Open HTTP Ping
  4. 4

    Check overall throughput

    Loss often shows up as 'fast but laggy' — speed test confirms.

    Open Speed Test
  5. 5

    Monitor over time

    Save the target and alert when loss exceeds your threshold.

    Open Dashboard

Frequently asked questions

What counts as bad packet loss?

Anything sustained above 1% degrades real-time apps. Above 5% breaks them. Bursty loss can be worse than steady loss.

Can my ISP fix packet loss?

If the loss starts inside the ISP's network (traceroute will show), yes — open a ticket with the traceroute output.

Does Wi-Fi cause packet loss?

Frequently. Retransmissions on the wireless link present as packet loss to apps. Try ethernet to confirm.

Is packet loss the same as latency?

No. Latency is delay; loss is dropped data. They often happen together when a link is congested, but they're independent problems.

Monitor it continuously

Save this check, get alerts on changes, and track multiple domains in one dashboard.

Learn about monitoring