
Your homegrown getStats() collector is already out of date
A homegrown getStats() collector gets built once and patched when it breaks. Why that happens, and how to build on maintained open source.
Learn how to troubleshoot WebRTC applications, monitor real-time communication performance, and get the latest insights on WebRTC development and debugging. Here we'll also share the latest improvements delivered in the new releases of rtcStats.

A homegrown getStats() collector gets built once and patched when it breaks. Why that happens, and how to build on maintained open source.

rtcStats v2.1 rebuilds the Analysis page for large accounts, hardens security across the platform, and adds bulk export and import of sessions.

How we split our WebRTC stats API for AI agents: a 2 KB enrich answer next to the full analyze record, and which endpoint to call.

rtcStats v2.0 redesigns the Connections, Streams and Devices tables, adds a Negotiations section and enriches every session summary for a sharper AI analysis.

Self-hosting rtcStats used to mean hosted analysis. Since v1.9, the rtcstats-enrichment server runs the analysis engine inside your own network.

rtcStats v1.10 rebuilds the session charts for calls that run for hours, adds 11 new connectivity and audio observations, and expands the documentation area.

WebRTC observability is not dashboards or getStats() access. Here are the six things a system has to capture before it can tell you why a call went bad.

Voice AI evals score the STT-LLM-TTS pipeline. Two transport failures leave no mark in a transcript, and full duplex removed the slack that hid them.

rtcStats v1.9 brings self-hosted enrichment via the rtcstats-enrichment server, four new observations, and a new Open Source section in the Knowledge Base.

rtcStats collects WebRTC session data inside your infrastructure. Forwarding to rtcstats.com is off by default. You choose what leaves your VPC.

You pull the webrtc-internals dump and scroll thousands of getStats() lines. rtcStats reads it for you and lets your data stay yours.

rtcStats v1.8: Dark and Light themes, a redesigned Overview with min/max, P95 and standard deviation, and Streams timelines anchored to call start.

Upload a webrtc-internals dump to rtcStats and AI tells you what went wrong on the call in under 30 seconds. Or query it from Claude Code and Cursor over MCP.

rtcStats v1.7: a client-focused Devices page with summary widgets, a dedicated api.rtcstats.com host with an observations catalog, and smoother onboarding.

Compare Chrome's webrtc-internals with rtcStats. See when browser-level debugging is enough and when production WebRTC monitoring gives you the missing data.

Version 1.6.0 revamps the Analysis page, adds rich filters to the public API and MCP, and shows deeper peer connection security details.

Version 1.5.0 brings server geolocation in connectivity diagrams (rtcstats), a refreshed website with Open Source and Resources pages, and new observations.

Compute Pressure is the browser's privacy-preserving CPU load signal. What it means, how to use it, and how rtcstats-js collects it with your WebRTC metrics.

Version 1.4.0 adds an embeddable viewer, compute pressure insights, new API endpoints, a broader knowledge base, and a revamped trial for all new accounts.

Version 1.3.0 introduces the Experience Score, six new connectivity observations, observation tag clouds, a richer overview and visual quality timelines.

Version 1.2.0 adds API access with Application Tokens, a revamped Knowledge Base, session tags and descriptions, new observations and smarter AI summaries.

Version 1.1.0 introduces the Showcase with YouTube integration, 5 Gold Credits for new accounts, and new connectivity observations.

Stop asking users to capture webrtc-internals manually. Use rtcstats-js with IndexedDB to store WebRTC stats locally and get dumps only when you need them.

Version 1.0 introduces AI call summaries, expanded observations, infrastructure detection, UI polish, core fixes, and rtcStats-js 2.1.0.

Advanced CPU observations, enhanced video & network transparency, uniform design across all screens, and improved upload monitoring.

Public sharing feature, three essential network observations, comprehensive Knowledge Base overhaul, improved chart tooltips, and UserAgent consistency fixes.

Redesigned Streams and Connections pages with deeper insights, integrated Knowledge Base, enhanced pair timelines, and new network observations.

Meet Observations: a set of best practices that see WebRTC issues before you do, saving you time so you can focus on what matters most.

Complete revamp of charts component with themed grouping, expanded connectivity observations, and new audio MOS aggregation.

Discover the 'less is more' approach to WebRTC monitoring: collect everything but focus on what matters most for faster troubleshooting.

Complete redesign of the Internals page into focused panes, new connection setup observations, and improved user experience.

Learn how to build your own WebRTC monitoring solution with rtcstats. Control costs, own your data, and customize your metrics collection.

New audio troubleshooting features, enhanced connection analysis, and team collaboration tools to improve your WebRTC debugging experience.

A field guide to chrome://webrtc-internals: how to open it, what every section shows, which metrics explain a bad call, and how to save a dump file.

Stay up to date with the latest rtcStats releases and discover new features designed to enhance your WebRTC debugging experience.

Discover why server-side monitoring isn't enough for WebRTC and how device-side statistics collection can transform your user experience.
Browse articles by category