Mux Internal CDN Router Achieves Sub-10ms Selection Latency for Video
Mux has transitioned to an internal CDN routing system that utilizes independent health probes and pre-calculated availability scores to manage traffic. By shifting from third-party real-user monitoring to this proprietary architecture, the company achieved a p99 selection latency of 9.9ms.
Key Takeaways
- Proprietary router delivers a p99 selection latency of 9.9ms, significantly faster than the 700ms spikes seen in earlier internal iterations.
- System utilizes independent health probes every 60 seconds to bypass the 'snowball effect' where logs only provide data for currently active CDNs.
- Availability scores are pre-calculated by a 'leader mode' process and stored in CockroachDB, rather than being computed on the fly for each viewer request.
- Redundant stream support has been transitioned from an opt-in to an opt-out feature to ensure mid-stream resilience during provider-specific outages.
Why It Matters
Mux’s shift to a high-speed, pre-calculated routing model addresses a critical bottleneck in multi-CDN architectures: the trade-off between decision granularity and startup latency. In an ecosystem where a 1% increase in buffering reduces viewing time by three minutes, shaving 100ms off the selection process directly improves Quality of Experience (QoE) and conversion. This internal move highlights a growing trend among mature video platforms to reclaim control from third-party Real User Monitoring (RUM) services, which often lack the visibility into CDN-to-origin health required for high-availability delivery. Watch for whether Mux integrates Mux Data logs into this router to further refine geographic traffic weighting.
Additional Context
The transition to independent health probes follows a broader industry debate regarding the limitations of Real User Monitoring (RUM). While RUM captures authentic device-side performance, it is inherently reactive and relies on existing traffic to generate signals. Per ClickHouse engineering reports from July 2026, mature infrastructure teams are increasingly pairing RUM with synthetic monitoring to ensure availability data exists during zero-traffic periods and to catch CDN-to-origin failures that edge-only RUM scripts often miss.
Mux’s reliance on CockroachDB for this router builds on its established multi-cloud strategy. According to Cockroach Labs reporting in August 2026, Mux uses geo-partitioning and multi-region deployments to maintain low-latency metadata access across AWS and GCP clusters. This distributed SQL approach is critical for the 'server mode' lookups in Mux's new CDN router, enabling the system to meet its 9.9ms p99 latency target while ensuring regional compliance with regulations like GDPR.
In the competitive landscape, the emergence of multi-CDN orchestration platforms like IO River, which leads 2026 market rankings per TechNews180, suggests that many B2B video providers are seeking unified control layers to standardize delivery rules. Mux’s internal build distinguishes it by focusing on sub-10ms performance and deep integration with its proprietary POPs (CDN C), reflecting a shift toward 'content steering' where players can dynamically shift providers based on real-time capacity and health metrics.
Read full article at mux.com
Enjoy our coverage?
Add StreamingMeme as a preferred source on Google to see more of our streaming news at the top of your Search results.
Add as preferred source