June Updates v1.6.0: Analysis Page Revamp, Rich API Filters & PC Security
Version 1.6.0 revamps the Analysis page with new stat cards and filters, brings rich filters to the public API and MCP, and adds deeper peer connection security visibility.
Posted by
Olivier AnguenotRelated reading
May Updates v1.5.0: Geolocation, Website Revamp & New Observations
Version 1.5.0 brings server geolocation in connectivity diagrams (rtcstats), a refreshed website with Open Source and Resources pages, and new observations.
April Updates v1.4.0: Embeddable Viewer, Compute Pressure, and a Brand New Trial
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.
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.
Welcome to v1.6.0 of rtcStats! This release sharpens the way you triage sessions: the Analysis page now leads with at-a-glance stats and smarter filters, the public API gains the same expressive filtering on top of richer session abstracts, and the Peer Connection pane finally answers "is this call actually encrypted, and how?"
A bit of dashboard polish, a lot more API power, and some long-awaited security visibility - let's dive in! 🔐
🚀 Major Improvements
> A Revamped Analysis Page 📊
The Analysis page (dashboard sessions list) gets a serious facelift. At the top, five new stat cards summarize your account at a glance: total Sessions, average Score, Observations by severity, Clients (browser + version), and OS breakdown. This gives you an immediate understanding of the files you've uploaded.
Below the cards, the sessions table now exposes a Score column and three new facet-aware filters: OS, Clients, and Tags.
A Revamped Analysis Page
> Rich API & MCP Filters (Paid Plans) 🔎
The public REST and MCP surfaces gain a much richer filter set on GET /api/rtcstats/v1.0/sessions and on the MCP list_sessions tool. You can now filter by observations, os, browser, userId, name, observationTags, browserVersion, conferenceId, sessionId, severity flags (hasCritical, hasHigh, hasMedium), and experience-score bands (hasLowScore, hasMediumScore, hasHighScore).
Each session returned by the list endpoint now carries an abstract field: a denormalized summary that bundles browser / OS, observation flags and tags, severity counts, and the experience-score band.
To make life easier for AI agents, the API reference is also available at api-docs.md.
Rich API & MCP Filters
> Deeper Peer-Connection Visibility 🔐
The Peer Connection pane now includes a dedicated Security section. For every peer connection, you can see the negotiated TLS version, which side sent the DTLS ClientHello (so you can tell who initiated the handshake), the negotiated dtlsCipher, and the srtpCipher protecting the media. It is finally easy to answer questions like "is this connection on DTLS 1.2 or 1.3?" or "are we landing on a strong SRTP profile?" without digging into raw SDP.
On the Connectivity side, the diagram now shows an IPv4/IPv6 indicator on each candidate pair, making it obvious when a call is happily flowing over IPv6 (or, more often, why it just refused to).
Deeper Peer-Connection Visibility
🛠️ Other Enhancements
> SDP Munging Detection 🧬
Two new observations flag SDP munging on the local description: mungedReorderedLinesInLocalSDP fires when m-lines or attributes have been reordered before setLocalDescription, and mungedModifiedLinesInLocalSDP fires when individual lines were edited. Both are common sources of "it works on my machine" interop bugs and were previously invisible from dump analysis alone.
> Overview Enhancements 🗺️
The Overview page gets two welcome upgrades:
- Areas treemap: the old tag strip is replaced with a treemap, so the visual weight of each area now matches its share of the session - much easier to spot where the noise is concentrated
- Session geolocation in "From": building on the v1.5 geolocation work, the session "From" field at the top of Overview now resolves directly to a location, so you do not have to jump to the Connectivity diagram to know where the call came from
> Free-Plan & Marketing Tweaks ✨
Two small but visible changes:
- Logged-in users can easily browse the public site: the homepage and other static marketing pages no longer redirect signed-in users straight to the dashboard - useful when you want to share a page with a colleague without logging out
- "Notes" is now "Feedbacks": the column on the Analysis sessions table is renamed to better match what teams actually put in there
📦 Ecosystem Updates
> @rtcstats/rtcstats-js v2.2.0 → v2.2.3 📡
computePressure/getStatsintegration: CPU-pressure samples are now traced alongsidegetStats, so the cloud's Compute Pressure observation lines up cleanly with the client-side timelinereloadCountshipped: the SDK now reports how many times the page reloaded mid-call, surfacing a previously invisible source of mid-call disruption- Cleaner connect tracing:
onicecandidatenow serializes.urland.relayProtocol, the WebSocket connect time is measured, and aclose before connectrace was fixed - flaky networks no longer produce mysterious gaps at the start of a trace - Patch series v2.2.1 → v2.2.3: corrects the trace timestamp baseline across reconnects and adds optional WebSocket error logging. If you are still on
2.2.0or2.2.1, upgrade to2.2.3- earlier 2.2.x builds were deprecated
> rtcstats-server 🛠️
No public release in this window - we'll catch up next month.
We're excited to see how you use the new Analysis page stats and the richer API filters to triage your WebRTC sessions! As always, the latest version of @rtcstats/rtcstats-js (v2.2.3) is available - make sure you're up to date to get the best out of these new features.
Happy debugging! 💎
