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 connection disconnected
Last updated Applies tortcstats-enrichmentrtcstats.com
The ICE agent's last connection state was disconnected, and the peer connection never reached connected.
Description
The ICE agent moves to the disconnected state when connectivity checks on a previously validated pair stop succeeding, without ICE ever recovering back to connected. Per the W3C WebRTC specification, disconnected is defined as a state the agent can in principle recover from on its own, unlike the terminal failed state defined by RFC 8445.
Is it a problem?
Often a real connectivity problem, though not always: per the W3C WebRTC spec's own framing, ICE disconnected is described as a state that can in principle be transient and self-recover. Here it was the connection's last observed state before the session ended without ever reaching connected, so while it usually reflects a genuine failure to connect, the state itself carries less certainty than an explicit ICE failed.
What do we do here?
We look at peer connections that never reached the connected state. If the ICE agent's last connection state was disconnected, we mark an observation.
