When Your Video Call Freezes, the Problem Is Not What You Think | CapyToolkit Skip to main content

Guides & How-Tos When Your Video Call Freezes, the Problem Is Not What You Think<br>July 12, 2026 Updated July 19, 2026 21 min read

DISCLOSURE<br>This post contains affiliate links. If you make a purchase through one of these links, I may earn a small commission at no extra cost to you. For more details, read the full Affiliate & Advertising Disclosure policy.

Your Zoom call dies mid-sentence. Your Slack huddle drops the moment someone shares their screen. Meet cuts to audio-only for no obvious reason. You restart the app, reboot your router, even switch to mobile data, and nothing improves. The real problem sits on the specific path your call data travels between two browsers, invisible to any speed test you run. After reading this, you will know how to run a browser-based P2P connectivity test, read each metric it outputs, and pinpoint whether the culprit is your NAT type, packet loss, jitter, or relay routing before you file another support ticket.

How Peer-to-Peer Video Calls Travel Over Your Network

Rather than traveling over a single pipeline, a video call weaves its data through a complex chain of local adapters, intermediate routers, and competing ISPs before reaching your partner’s screen. Because every single hop along this path presents a potential bottleneck, any delay compounds instantly. By sending continuous probe packets across this exact route, your browser captures the latency added by each physical connection point. Depending on your router’s security policies, NAT traversal decides whether those packets travel directly or through a slower relay.

Tracing through each connection stage reveals exactly how your call data behaves under pressure. First, your browser contacts a STUN server to discover its public IP, then shares those gathered credentials with its remote peer over a pre-arranged signaling channel. Once both engines possess these handshake tokens, they initiate direct ICE connectivity checks. When those direct paths fail to punch through local firewalls, the browsers fall back to a TURN relay server to bridge traffic. Each transition point surfaces a different failure mode.

Browser contacts STUN server to discover its public IP and port.1

Signaling exchange shares offer and answer SDP blobs between peers.

Both sides run ICE connectivity checks against all gathered candidate addresses.2

Failed direct checks fall back to a TURN relay server that bridges traffic.2

A server-based ping test measures only the first hop of this journey, from your browser to a datacenter much closer than the remote peer. The result looks clean while the actual four-hop P2P path drops packets and introduces jitter. This gap explains the most confusing symptom: an 8-millisecond ping to your ISP’s speed-test server at the same time a 220-millisecond jitter metric appears on a video call. The two numbers are not contradictory because they measure two completely different paths. While this structured handshake works perfectly under ideal network conditions, standard server diagnostics often mask the bottlenecks that occur during live WebRTC sessions.

What a speed test does not measure

Speed tests measure the path from your device to a nearby datacenter, typically over a direct backbone route with no NAT traversal required. A result of 8 milliseconds round-trip to that server tells you nothing about what happens when your call data must punch through your router’s NAT, cross both ISPs, and arrive at a peer on a different network. Because standard browser-based speed tests utilize TCP or WebSocket handshakes over a structured server backbone, they bypass the raw UDP path that WebRTC uses for real-time media streams, leaving local firewall rules and packet jitter completely invisible. Consequently, you can run a perfect speed test and still experience significant jitter on a video call because the problem sits on the P2P leg of the journey, not the datacenter leg.

CapyToolkit’s test for peer-to-peer latency, jitter, and packet loss between two browsers opens a real WebRTC data channel and measures every hop your call data takes. Every millisecond it records includes NAT traversal, both ISP routes, and any relay overhead. That measurement is what matters when you press the call button. browser-based tools that process everything locally remove the need to grant diagnostic software network-level permissions you would rather not hand out.

A router that lets you actually control NAT traversal, UPnP, and QoS is the hardware change most likely to stop a call from falling back to a relay. The table below compares routers that expose that control, from a budget multi-WAN box to Wi-Fi 7, sorted by price and wireless standard.

Routers That Give You NAT Control, Compared

Product<br>Price<br>Wi-Fi standard

TP-Link ER605 (Omada Multi-WAN VPN Router)<br>$59.99<br>Wired (multi-WAN)<br>Best Value

Details

ASUS RT-AX57...