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 failed
Last updated Applies tortcstats-enrichmentrtcstats.com
The ICE agent's last connection state was failed, and the peer connection never reached connected.
Description
The ICE agent moves to the failed state once every candidate pair's connectivity checks have been exhausted without a single pair succeeding. This is ICE's terminal negative outcome: unlike checking, which can in principle continue indefinitely while candidates keep trickling in, reaching failed means the candidate exchange had already completed and no path worked.
Is it a problem?
Yes. Per RFC 8445, ICE reaching the failed state means every candidate pair's connectivity checks were exhausted without success. No usable network path was found between peers.
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 failed, we mark an observation.
