Showcase
rtcStats reduces WebRTC debugging from hours to minutes. But don't take our word for it.
We analyze real-world WebRTC implementations from production services across the industry - from video conferencing to cloud gaming to AI voice agents. Each entry below is a real session loaded into rtcStats, showing exactly what our analysis surfaces.
21 showcase items found
Company
Title
Summary
Sessions Recaps
What we bumped into:
- Audio only; video negotiated but inactive
- 2 peer connections (one unused)
- Slow DTLS establishment
- No STUN/TURN; ICE-TCP fallback
- Opus at 32kbps outgoing, 64kbps incoming
What we bumped into:
- 4 peer connections
- 20+ transceivers
- 30fps screen sharing
- SDP munging msid attribute
What we bumped into:
- Separate PC for screen sharing
- Sub-millisecond DTLS connection time
- VP9 webcam; VP8 screen share
- Data channel per message
What we bumped into:
- LiveKit
- 2-way video
- Simulcast
- Excessive renegotiations
What we bumped into:
- LiveKit
- Single peer connection
- Custom simulcast config
What we bumped into:
- LiveKit
- Single peer connection
- Inefficient simulcast encoding
- Stereo audio
What we bumped into:
- LiveKit
- Use of DTX
- No incoming audio
- Stereo audio
What we bumped into:
- Remote TURN server
- Misconfigured TURN
- Stereo audio
What we bumped into:
- LiveKit
- 2 incoming audio channels
What we bumped into:
- Daily
- Two peer connections
- Unused video stream
- Stereo audio
What we bumped into:
- Unreal Engine Pixel Streaming
- Outgoing audio over WebSocket
- High audio bitrate
- High video resolution
What we bumped into:
- LiveKit
- Uncommon video resolution
- Low video bitrate
- Stereo audio
- SDP munging, moving things around
What we bumped into:
- Inefficient simulcast encoding
- LiveKit
- Long DTLS handshake
- Buggy webrtc-internals collection
What we bumped into:
- High ICE connection time
- Variable incoming audio bitrate
- Stereo audio
- No video FEC
- SDP video codecs preference order
What we bumped into:
- Forced TURN relay
- OpenAI voice service
- High RTT
- Exposed internal IP address
- Variable bitrate on incoming audio
What we bumped into:
- 1080@60fps using AV1
- Use of FEC on video
- Stereo audio
- High audio bitrate
What we bumped into:
- Use of FEC on video
- Stereo audio
- Short DTLS connection time
- IPv6 use
What we bumped into:
- Audio+Video AI conversational avatar
- Daily, Pipecat, Twilio
- Simulcast used on a human-to-bot call
What we bumped into:
- Audio only AI conversational avatar
- Pion, Twilio
- No TURN servers
- Slow DTLS connection time
- High target audio bitrate
What we bumped into:
- Audio conversational avatar
- Redundancy in iceServers with not TLS
- Outbound negotiated video streams
- Acoustic echo cancellation disabled
