WebRTC Metrics
A comprehensive overview of WebRTC statistics, derived calculations, extracted features, and observable signals, to better understand call quality, connectivity, and user experience in rtcStats
On this page4 sections
ICE checking stalled
Last updated Applies tortcstats-enrichmentrtcstats.com
ICE reached the checking state but never resolved to connected, failed, or disconnected.
Description
Once both descriptions are set, the ICE agent moves to the checking state and starts testing candidate pairs. Normally this resolves within seconds to connected (a pair succeeded), failed (none did), or disconnected.
Is it a problem?
Often, though not always a fault: per RFC 8838, an ICE agent that never receives an end-of-candidates signal from the remote peer can legitimately stay in checking indefinitely while it keeps waiting for more trickled candidates. It can also mean the remote peer's page closed, crashed, or lost network mid-negotiation.
What do we do here?
We look at peer connections that never reached the connected state. If ICE reached the checking state at least once and never resolved to connected, completed, failed, or disconnected, we mark an observation.
