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.
Posted by
Related reading
rtcStats v2.0: Redesigned Tables, Negotiations & Sharper Analysis
rtcStats v2.0 redesigns the Connections, Streams and Devices tables, adds a Negotiations section and enriches every session summary for a sharper AI analysis.
September Updates v1.10: Long-Call Charts, New Observations and Trust Center
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.
August Updates v1.9: Self-Hosted Enrichment, New Observations & Open-Source Guides
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.

Welcome to v1.5.0 of rtcStats! This release zooms out from raw stats and onto the map: you can now see where TURN, STUN, and candidate pairs actually live, browse a freshly revamped website, and lean on a new batch of observations to catch issues that used to stay hidden.
A bit of cartography, a bit of spring cleaning, and a few sharper signals - let's dive in! πΊοΈ
π Major Improvements
> Geolocation in Connectivity Diagrams π (rtcstats-server)
Connectivity issues are often a story of distance. In this release, we now surface the geolocation of TURN/STUN servers and any IP from the candidate pairs, directly inside the connection diagrams.
One glance is enough to spot a TURN server on the wrong continent, a relay path that takes a detour, or a remote peer much further away than expected. Best part: this works for every account type.
On the integration side, geolocation requires rtcstats-server wired up to a MaxMind database. The server enriches each rtcstats file with IP-to-location data at ingestion time, and rtcStats then picks it up to draw the diagrams and decorate the logs.
Read more about geolocation enrichment in rtcstats-server.
Geolocation in Connectivity Diagrams
> A Refreshed rtcStats Website β¨
The public side of rtcStats got a serious makeover. We've rewritten large chunks of the marketing copy, redesigned the layout for a cleaner reading experience, and reorganized the top navigation to make it easier to find what you're looking for.
Two new entry points stand out:
- Open Source page: a dedicated home for the open-source bits of the rtcStats ecosystem - what we've put out there, why, and how to contribute
- Resources entry in the top navigation: a single jump-off point that gathers the blog, the Knowledge Base, the Showcase, and the API documentation - so you don't have to hunt through menus anymore
Refreshed rtcStats Website
> New Observations: Audio Processing & Capture (Developer Plan) π
The Observations engine keeps growing. This release brings a fresh batch of signals around audio processing and media capture, the two places where a call can sound wrong without a single packet going missing. They used to be buried in the raw logs, when they showed up at all. The original browser errors are still there in the Logs pane when you want the detail.
New Observations: Audio Processing & Capture
π οΈ Other Enhancements
> Logs and Devices Improvements ποΈ
The logs panel got several quality-of-life improvements that make it easier to follow what's actually happening during a session:
- New transceiver layout: transceiver-related entries are now grouped and rendered with a cleaner layout, so you can scan direction changes and codec negotiations at a glance.
- Device change events: the browser's
devicechangeevent is now captured in logs, perfect to spot a hot-unplugged microphone or a freshly added camera mid-call. - Inline geolocation for candidates: beyond the diagram view, geolocation is now shown directly on candidate log lines - so you don't have to switch panels to know where a given candidate resolves to.
> More Knowledge Base Articles & Mermaid Diagrams π
The Knowledge Base keeps growing. This release adds a brand new reference statistics article that lays out the WebRTC stats surface in one place - a handy companion when you're trying to figure out which metric tells which story.
On top of that, KB markdown now renders Mermaid diagrams natively. Flows, timelines, and state machines no longer have to hide in screenshots - they're drawn live, stay readable, and can be updated alongside the prose.
π Bug Fixes
> Security updates
We've added a new set of HTTP security headers including a strict Content Security Policy and X-Frame-Options: DENY to prevent header injection, hijacking, and clickjacking attempts.
We're excited to see how you use the new geolocation insights and the refreshed website to share your WebRTC findings! As always, the latest version of rtcstats-js is available - make sure you're up to date to get the best out of these new features.
Happy debugging! π