Why packet loss feels so much worse than slow speed
TCP automatically retransmits lost packets, which masks loss on web browsing — pages still load, just slowly. But UDP-based traffic (Zoom, Discord, gaming, livestreaming) can't retransmit fast enough; the player or codec just skips ahead. That's what you hear as “robot voice” and see as freeze-frames or warping.
Diagnose where the loss is happening
- Run the packet loss analyzer on Wi-Fi.
- Plug into the router with ethernet, run it again.
- If loss disappears wired, your Wi-Fi is the culprit — try 5 GHz, move closer, change channels.
- If wired is still lossy, run from a second device. Same loss = router or ISP. Clean on one device = a NIC driver or cable issue.
- Power-cycle the modem; if loss returns within hours, escalate to your ISP with the test results.
Fixes ranked by likelihood
- Replace the ethernet cable. Cracked Cat5e cables are an absurdly common cause.
- Update Wi-Fi adapter drivers — especially on older laptops.
- Change the Wi-Fi channel (Wi-Fi analyzer apps make this easy).
- Disable router QoS or Smart Connect features temporarily; some firmwares drop packets under their own QoS logic.
- Replace the modem if it's more than 5 years old or running an old DOCSIS spec.
- If everything points upstream, share the timed analyzer report with your ISP.
When you need proof for support
ISPs and IT teams take recurring evidence far more seriously than a single bad test. Scheduling a recurring packet loss check (Pro feature) builds a timestamped log that's hard to dismiss — and surfaces the daily patterns (peak hours, weather, neighbor activity) that explain when and why loss appears.