Tsahi Levent-Levi

rtcStats - WebRTC monitoring & observability from your users' browsers

rtcStats is a WebRTC monitoring, observability, and troubleshooting platform. Drop in our open source SDK to capture real-time quality metrics from your users' browsers, use our open source server and own your data. Automatically detect 100+ quality issues, pinpoint root causes (network, browser, or media server), and get actionable troubleshooting guidance. Built by three WebRTC veterans - Tsahi, Olivier, and Philipp. Free tier included. Start monitoring in minutes.

Add a comment

Replies

Best
Tsahi Levent-Levi
Hey Product Hunt! 👋 I'm Tsahi, and I've spent 15+ years in WebRTC - running bloggeek.me, consulting for companies you've definitely heard of, and answering the same question over and over: "Why is this call bad?" Along with Olivier and Philipp, both WebRTC OGs who've collectively spent decades building, breaking, and fixing real-time communication systems... we've built rtcStats 🚀 WebRTC monitoring and troubleshooting shouldn't require developing server-side probes or parsing raw getStats() dumps manually. rtcStats gives you full WebRTC observability by collecting metrics straight from the browser, then automatically flags 100+ quality issues - from packet loss patterns to subtle codec misconfigurations. When something goes wrong, you get the root cause, not just a red dot on a dashboard. The SDK is open source. You integrate it in minutes. You OWN the data. In our visualization tool there's a free tier so you can use without commitment. The platform does the heavy lifting - analysis, visualization, alerting, and troubleshooting guidance. We also built the most complete WebRTC getStats() reference on the web (280+ metrics, plain English). It's free for everyone, even if you never use the product. Would love your feedback - especially if you've ever stared at webrtc-internals and wondered what you're looking at. That's literally why we built this.
Philipp Hancke

Hey Product Hunt! 👋

I'm Philipp - one of the three WebRTC veterans behind rtcStats. I've spent 15+ years debugging why real-time calls break, and webrtc-internals has been both my best friend and my biggest frustration.

rtcStats is my attempt to fix that: drop in the SDK, get full observability straight from the browser, and actually understand what went wrong - not just that something did.

My personal favorite feature: upload a dump, share a link. Tsahi can send me a link instead of emailing a file I have to import myself. Simple, but it changes everything.

Would love to hear from anyone who's ever lost an hour staring at a webrtc-internals dump. 🙌