Back to Blog

March Updates (2): One Score to Rule Them All, Tag Clouds, and Connectivity Deep-Dives

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

Posted by

March Release (v1.3.0): Experience Score, Tag Clouds, and Connectivity Deep-Dives

We're "marching" forward into 2026 with a release that's all about making your WebRTC data more human-readable. Let's be honest: digging through thousands of telemetry lines to find out why a call dropped is like looking for a needle in a haystack — except the haystack is made of JSON and your boss is waiting for an answer.

With v1.3.0, we're introducing the Experience Score, giving you a single number to judge call quality instantly, along with new visualization tools to help you fix what's broken faster.

🚀 Major Improvements

The New Experience Score (Paid Plans)

Ever wish you could just see a "8.5/10" and move on with your day? Now you can. The Experience Score is a weighted metric that aggregates the health of an entire session into one easy-to-compare number. It's calculated using four key pillars:

Experience Score

The New Experience Score

  • Video Score (New): A fresh look at bitrate stability and frame consistency
  • Connectivity Score (New):How "healthy" was the underlying network path?
  • Observations: Deductions based on the severity of issues detected by our engine
  • Audio MOS: Our classic, industry-standard Mean Opinion Score for voice quality

Learn more about scores in rtcStats.

6 New Connectivity Observations (Paid Plans)

Connectivity issues are often the "black box" of WebRTC. They take an awful lot of time to troubleshoot and require a high level of expertise in WebRTC. We've added six new specific observations to shine a light on why connections fail before they even start:

  • Aborted Connection: When a user gives up before the handshake finishes
  • Dropped Connection: Sudden losses of signal
  • Failed Connection: ICE failures and signaling dead-ends
  • Short-lived Connection:For those "blink and you missed it" sessions
  • Empty Sessions: When the signaling works, but no media flows
  • Excessive Disconnections:For when the connection is more "on-and-off" than a bad sitcom romance
6 New Connectivity Observations

A Failed Connection

Observation Tag Clouds (Paid Plans)

Data is powerful, but visual patterns are faster. We've introduced Tag Clouds that categorize session observations into high-level Areas—such as Network, Connectivity, Audio, and Peripherals.

If call quality drops, the Tag Cloud immediately surfaces the primary culprit in a larger font. Instead of digging through logs, you'll know instantly whether to focus your investigation on "Inbound" traffic or "Peripheral" hardware.

✨ Other Enhancements

The "One Shot" Overview

We've beefed up the overview section. You can now see every critical session metric in a single view. No more clicking between tabs to piece together the story.

Visual Quality Timelines

Media Table: Redesigned to show exactly when quality dipped. Instead of just seeing an average, you can pinpoint the moment the video froze.

Connectivity Table:Now displays Connectivity Duration. You can immediately spot which peers took too long to connect or which ones stayed in "connecting" limbo forever.

Visual Quality Timelines

Visual Quality Timelines

Expanded Showcase

We've added new video walkthroughs to our showcase, focusing on more Voice AI services.

🛠️ Bug Fixes & Technical Points

Chrome 146 Compatibility:Starting with Chrome 146, a new priority for TURN over DTLS was introduced. This change could cause some sessions to be misidentified in previous rtcStats versions. We've updated our logic to ensure these are identified perfectly.

Ready to see your new Experience Scores? Log in to your dashboard to check out the redesigned tables and overview.