The Remote Worker's Guide to Packet Loss: Why Speed Tests Are Lying to You

The Speed Test Illusion

Every remote worker has had this experience: important client call at 2 PM. You run a speed test at 1:55 PM. It shows 200 Mbps download, 20 Mbps upload. Confidence soars. You join the call.

Five minutes in, the client says: "You're breaking up." Your video freezes. Your audio sounds like you're underwater. You check your speed test result again. Still 200 Mbps. What is going on?

Here's the uncomfortable truth: your speed test was accurate, and it was also completely irrelevant.

A speed test measures bandwidth, the theoretical maximum data throughput of your connection. A Zoom call uses about 3 Mbps. You have 200 Mbps. You have 66x more bandwidth than you need. Bandwidth is not the problem.

The problem is packet loss: the percentage of data packets that are sent but never arrive at the destination. And speed tests, by design, are almost completely blind to it.

What Is Packet Loss, Really?

Your internet connection doesn't send data as a continuous stream, like water through a pipe. It sends data as discrete packets, small chunks of information, each with a source address, destination address, and a piece of your data.

When you speak on a Zoom call, your voice is captured, compressed, split into packets, and sent across the internet. Each packet contains about 20 milliseconds of audio. At the other end, the packets are reassembled into a continuous audio stream.

Packet loss happens when one or more of those packets fail to arrive. They might be dropped by an overloaded router, corrupted by Wi-Fi interference, or lost in transit through your ISP's network. The result is a gap, a missing 20ms of your sentence.

One dropped packet is a tiny click. Five in a row is a full syllable gone. Ten is an entire word erased from the conversation.

Note: These are general VoIP quality benchmarks. Zoom's connection indicator uses a composite score factoring in latency, jitter, and packet loss together, and recommends keeping packet loss under 2%.

Why 1% Packet Loss Ruins Everything

One percent sounds negligible. In most contexts, it is. If 1% of a file download is lost, the missing pieces are just re-sent. You never notice. The download takes 1% longer, fractions of a second.

But voice and video are real-time. There's no time to re-send. When you're speaking and a packet carrying the word "approved" is lost, Zoom can't pause the call, request a retransmission, and resume. By the time the missing packet could arrive, you've already said two more words. The moment is gone.

This is why speed tests and real-time apps live in fundamentally different worlds:

TCP vs. UDP: Why Speed Tests Hide the Problem

This is the technical heart of the issue, but it's worth understanding because it explains why everything you thought you knew about "fast internet" might be wrong.

TCP (Transmission Control Protocol) is what your browser, email, and most speed tests use. It guarantees delivery: if a packet is lost, it's automatically re-sent. TCP connections are reliable but have overhead. Most consumer speed tests (Speedtest by Ookla in browsers, Fast.com) run over TCP or WebSockets, so packet loss manifests as reduced throughput, often dramatically, rather than as an explicit loss metric.

TCP's retransmission mechanism masks packet loss in speed test results. The test still completes, but at lower throughput, and the impact is much worse than you'd expect. Even 2% packet loss can cut TCP throughput by 50% or more, depending on latency. At 5% packet loss, TCP performance collapses: a connection rated at 200 Mbps might only deliver single-digit throughput. But the speed test just shows a lower number. You see "45 Mbps" and think: "A bit slow today." You don't realize packets are being dropped wholesale.

UDP (User Datagram Protocol) is what Zoom, Teams, FaceTime, Discord, and online games use. It does not guarantee delivery. If a packet is lost, it's gone. This is by design; for real-time audio, a 200ms-old retransmitted packet is worse than a gap, because it arrives after the moment has passed and creates audio distortion.

So the same connection that looks "fine" on a speed test can be genuinely broken for video calls. They're measuring different things.

How to Test for Packet Loss on Mac

Method 1: Terminal Ping Test

The simplest test. Open Terminal and run:

This sends 200 packets to Cloudflare's DNS server (a reliable ICMP target) and waits for replies. At the end, you'll see a summary:

Here, 2% packet loss means 4 out of 200 packets were lost. That's enough to cause audible issues on every Zoom call.

Note: Avoid using 8.8.8.8 (Google DNS) for packet loss testing. Google de-prioritizes ICMP traffic and may rate-limit ping responses, which can show false packet loss that isn't present on your actual connection. Cloudflare's 1.1.1.1 is a more reliable target for ICMP testing.

Method 2: Extended Monitoring

Packet loss is often intermittent. A 200-packet test might miss it entirely. For a longer test:

The problem: you need to babysit a Terminal window and manually check it. Packet loss often happens during specific conditions (peak ISP hours, microwave running, Time Machine backing up) and you won't catch it unless you're actively monitoring at that moment.

Method 3: Continuous Menu Bar Monitoring

Method 4: Test Different Destinations

If you're seeing packet loss to 8.8.8.8, test a few other destinations to narrow down where the loss occurs:

• Loss to your router (192.168.1.1): The problem is your Wi-Fi or router hardware. Your ISP is not involved.
• No loss to router, but loss to external targets: The problem is between your router and the internet. This is your ISP's network.
• Loss to one destination but not others: The problem is with a specific network route, not your connection as a whole.

What Causes Packet Loss at Home

Wi-Fi Interference

The most common cause. Wi-Fi uses shared radio frequencies that compete with neighboring networks, Bluetooth devices, microwave ovens, baby monitors, and even USB 3.0 devices (which emit interference at 2.4GHz).

Signs: packet loss is worse when you're far from the router, or comes and goes unpredictably.

Router Overload

Consumer routers have limited processing power. When too many devices are connected and actively transferring data, the router's CPU can't process packets fast enough and starts dropping them.

Signs: packet loss appears when multiple family members are streaming, downloading, or gaming simultaneously.

ISP Congestion

Your ISP oversubscribes bandwidth in your area. During peak hours (7–10 PM), there isn't enough capacity for all users, and routers in the ISP's network drop packets. In some cases, your ISP may be actively throttling specific types of traffic.

Signs: packet loss follows a daily pattern. Fine in the morning, worse in the evening. Weekends may be worse than weekdays.

Upload Bandwidth Saturation

Most home connections are asymmetric: 200 Mbps down, but only 10–20 Mbps up. Background uploads (iCloud, Dropbox, Time Machine) can saturate upload capacity. When upload is full, the router starts dropping outgoing packets, including your Zoom audio.

Signs: packet loss appears during backup windows or when uploading large files. Zoom is particularly affected because it needs constant upload for your camera and microphone.

Bufferbloat

A subtle but devastating issue. When your connection is saturated, your router queues packets in a buffer instead of dropping them immediately. This creates enormous latency (500ms+) as packets wait in line. Eventually the buffer overflows and packets are dropped in bursts.

Signs: latency spikes to 500–2000ms during heavy usage, followed by sudden packet loss. Speed tests during these events may still show high bandwidth.

macOS AWDL (AirDrop)

Apple Wireless Direct Link periodically forces your Mac's Wi-Fi radio to hop channels to listen for nearby Apple devices. During channel hops, packets to your router are dropped.

Signs: brief, regular packet loss every 10–30 seconds, even when the network is otherwise idle. Unique to Apple devices.

Fixing Packet Loss: A Practical Checklist

Quick Wins (Try These First)

• Move closer to the router or remove physical obstructions. Walls, especially concrete and brick, dramatically reduce Wi-Fi signal quality.
• Switch to 5GHz Wi-Fi. If your router broadcasts both 2.4GHz and 5GHz, prefer 5GHz. It has less interference (shorter range means fewer competing networks) and more available channels.
• Pause background uploads before important calls. Quit Dropbox, pause iCloud, and defer Time Machine backups.
• Disable AWDL if you don't need AirDrop: sudo ifconfig awdl0 down

Medium Effort Fixes

• Update router firmware. Log into your router's admin page and check for updates. Firmware updates often fix bugs that cause packet dropping under load.
• Change Wi-Fi channel. Use a Wi-Fi analyzer (your Mac has one built in: hold Option and click the Wi-Fi icon → "Open Wireless Diagnostics" → Window → Scan) to find the least congested channel. Note: Apple has been deprecating some of these built-in tools in recent macOS versions, so this workflow may change in future releases.
• Enable QoS for Zoom. If your router supports Quality of Service, create a rule that prioritizes UDP traffic on ports 8801–8810 (Zoom's media ports).
• Use Ethernet for important calls. A USB-C to Ethernet adapter eliminates Wi-Fi variables entirely. If packet loss disappears on Ethernet, the problem is definitively Wi-Fi, not your ISP. See our Ethernet vs. Wi-Fi 6E latency comparison for the full data.

Bigger Fixes

• Upgrade your router. If your router is 5+ years old, a modern Wi-Fi 6 or 6E router handles congestion far better. Look for routers with SQM (Smart Queue Management) support to eliminate bufferbloat.
• Call your ISP. If packet loss occurs even on Ethernet and follows a time-of-day pattern, it's ISP congestion. Request a "line quality test" or technician visit. Come armed with data: "I'm seeing 3% packet loss to 8.8.8.8 between 7 and 10 PM, averaging over 1000 ping samples."
• Consider a mesh system. If distance is the issue and Ethernet isn't practical, a mesh Wi-Fi system (with wired backhaul between nodes) can eliminate dead zones without the instability of range extenders.

Frequently Asked Questions