For about four months, every video call I made after 6 PM looked like a slideshow. My ISP speed tests came back fine — 180 Mbps down, 40 Mbps up. But Zoom and Google Meet were unusable. I blamed the ISP. I was wrong.
How I Started Measuring Instead of Guessing
The turning point was running a proper packet loss test instead of a speed test. Speed tests measure throughput at one moment. Packet loss tests measure reliability over time, which is what video conferencing actually needs. I used mtr — a free command-line tool that combines ping and traceroute — and ran it for 10 minutes while on a call.
The results were clear: zero packet loss to my router, zero loss to the first ISP hop, but 12% loss between hops three and four inside the ISP's network. That ruled out my home hardware completely. But then I ran the same test from my phone on mobile data — and the call quality was perfect.
The Real Problem Was Not the ISP
That contrast forced me to look more carefully at my local network. I connected my laptop directly to the modem with an Ethernet cable, bypassing the router entirely. The packet loss disappeared. The router was the culprit — specifically, its QoS settings were mishandling UDP traffic, which is what video conferencing uses.
The router was a mid-range consumer unit about four years old. Its QoS feature, marketed as optimizing traffic, was actually deprioritizing UDP packets during periods of mixed traffic. Disabling QoS entirely solved the problem in under two minutes. No new hardware, no technician, no subscription service.
What I Learned About Diagnostic Order
The standard troubleshooting sequence most people follow — restart router, call ISP, pay someone — skips the most useful step: isolating variables methodically. The correct order is roughly this:
Recommended diagnostic sequence for video call issues
| Step | Action | What It Rules Out |
|---|---|---|
| 1 | Run mtr for 10 minutes | Identifies which network hop is dropping packets |
| 2 | Test on mobile data | Confirms if issue is local or external |
| 3 | Connect directly to modem | Isolates router from equation |
| 4 | Check QoS and firewall settings | Finds misconfigurations causing UDP issues |
Following that sequence takes about 30 minutes. It would have saved me four months of frustration if I had done it in week one.
The Cost Breakdown
I spent nothing. mtr is free. The fix was disabling one router setting. The only real cost was time I wasted assuming the problem was outside my control. That assumption is the most expensive mistake in home network troubleshooting — it keeps you passive when the solution might be two menu clicks away.
Video calls have been clean for three months since. Same router, same ISP, different configuration.