How we run network tests across carrier networks

WebRTC succeeds or fails on the network — not the code. So when we deliver a build, the network test is the part the customer's engineering team should care about most.

What we test

We run a battery against every delivered build:

• STUN binding — host vs srflx vs relay candidate distribution
• Jitter, RTT, packet loss under simulated 100 ms / 2% / 50 Mbps profiles
• Reconnection when the network drops mid-call
• Multi-region failover (only if the build is multi-region)

Where we test from

• Office wifi (the baseline — should always pass)
• A real cell network (4G, throttled to 1.5 Mbps)
• Behind a corporate proxy that blocks UDP (forces TURN/TCP fallback)
• Cross-continent path (US ↔ EU)

What goes in the report

A PDF with the raw data, a chart per metric, the recommended SDK based on the results, and any TURN configuration changes we suggest.

Every plan includes this, even the smallest one. Without it, you are shipping blind.