Why Video Calls Care About Ping More Than Speed

A video call moves surprisingly little data — a solid HD call typically needs only around 1.5-3 Mbps each way. What it cannot tolerate is delay and inconsistency. Unlike a Netflix stream, which buffers seconds of video ahead, a live call has to deliver your voice and face in near real time; there is nothing to buffer behind. That's why a 500 Mbps connection can still produce robotic audio and frozen tiles: for conferencing, latency, jitter, and packet loss decide call quality, and bandwidth is merely the entry ticket.

The Thresholds Zoom, Teams and Meet Actually Need

The major platforms use similar real-time transport under the hood, so the commonly recommended targets are close across all three:

Round-trip latency under ~100ms: conversation feels natural. Up to ~200ms is workable, but people start talking over each other; beyond ~300ms the awkward-pause effect takes over.
Jitter under ~30ms: above this, audio gets choppy as the app's playback buffer struggles to smooth out irregular packet arrival. Under 10ms is where calls feel effortless.
Packet loss under 1%: real-time audio can't wait for retransmissions, so lost packets become clipped syllables and smeared video. Above ~2%, calls degrade visibly.

Treat these as typical guidance rather than hard cutoffs — the apps adapt aggressively, but every threshold you miss costs quality somewhere.

Why Your Calls Stutter on a "Fast" Connection

The most common remote-work complaint — "my internet is fast, but Teams keeps freezing" — almost always traces to one of three things. First, upload saturation: home plans are usually asymmetric, and a cloud backup or someone streaming can consume the small upload channel your call depends on. Second, bufferbloat: when the line is busy, your call's packets wait in an oversized router queue behind bulk traffic, and latency balloons exactly while you're presenting. Third, Wi-Fi variability: retransmissions and interference create the jitter and micro-loss that real-time audio hates, even when average speed looks great.

Jitter and Packet Loss: The Call Killers

Of the three metrics, these two do the most damage per millisecond. Steady 90ms latency is fine — everyone adapts. But 20ms of jitter forces the app to choose between adding hidden buffering delay or letting audio break up, and even 0.5-1% packet loss is audible as clipped words. If your calls sound like a bad cell connection, check jitter and loss before anything else — our packet loss testing guide covers how to isolate where drops occur.

How to Test Your Connection Honestly

A browser-based ping test measures HTTPS round-trip time to nearby cloud endpoints — a realistic proxy for your general latency, though not the exact figure inside Zoom's or Teams' own transport. Used correctly, it answers the question that matters: is your connection call-ready?

Test at your actual meeting hours, from your actual workspace — a quiet-Sunday Ethernet result says nothing about a Tuesday 10 AM call from the spare room.
Check jitter and packet loss, not just the ping figure.
Run one test while a big upload or a second stream is active — if latency explodes under load, you've found why calls die when the household is busy.
Compare Wi-Fi against Ethernet from the same spot; a large gap means the problem is local.

Fixes That Help Before Your Next Meeting

Wire the work machine — Ethernet removes the biggest source of jitter in one step.
Enable QoS/SQM on your router so call traffic isn't queued behind downloads.
Pause cloud sync and backups during meeting blocks; they compete directly for your upload.
Mind the upload plan: if several people in the house stream or call at once, upload capacity is usually what runs out first — our streaming upload guide shows the numbers per quality level.

Get latency, jitter, and loss inside the thresholds above, and video calls become the least demanding thing your connection does all day.