Meta Deploys Media Over QUIC for Instagram Live Video Ingest
Instagram Live transitions video ingest to the emerging open IETF standard protocol.
1Instagram Live Adopts MoQ
Meta deployed Media over QUIC (MoQ) for live video ingest across Instagram Live on iOS and Android. This rollout introduces the emerging open IETF transport standard to Meta's production scale. It lays a unified technical foundation to enhance interactive streaming reliability and reduce latency across live broadcast products.
2Replacing Fragmented Protocol Stacks
Modern streaming architectures maintain separate protocols for different media jobs: RTMP for ingest, HLS or DASH for playback, and WebRTC for calls. Meta previously relied on its proprietary RUSH protocol for nearly a decade. MoQ unifies these fragmented stacks across ingest, relay delivery, and playback into a single transport layer.
3Core Transport Architecture Mechanics
MoQ operates over QUIC, eliminating cross-stream head-of-line blocking and accelerating connection setup. Its core abstraction, the Track, transfers media objects across relays without decrypting payloads. Relays handle caching, native fan-out, and track-aware prioritization, enabling simultaneous subscribers to configure distinct latencies ranging from interactive to archival buffer speeds.
4Standardizing Beyond Proprietary Systems
Meta chose Instagram Live ingest as its first MoQ proving ground to establish performance parity at peak scale. Transitioning from in-house RUSH to an IETF standard allows collaborative development with Google, Cisco, Cloudflare, and Akamai. This industry alignment eliminates the overhead of Meta maintaining specialized media transports entirely alone.
5Client Integration via Moxygen
Client-side deployment across broadcast apps utilized Meta's open-source C++ library, moxygen. The library implements publisher, subscriber, and relay roles on top of Meta's mvfst QUIC stack. Broadcaster apps dynamically toggle between MoQ and RUSH via server-controlled configuration parameters without requiring distinct application binary builds for different transport setups.
6Edge Translation Decouples Downstream
Meta avoided massive downstream backend rewrites by terminating incoming MoQ streams directly at dedicated edge servers. A specialized translation shim converts incoming MoQ frames into legacy RUSH payloads before forwarding them internally. Server-side stream URL generation routes experiment cohorts dynamically, decoupling the rollout velocity from end-user mobile app updates.
7Overcoming Production Operational Hurdles
Operating an evolving draft specification required compatibility shims alongside continuous upstream IETF contributions. Because enterprise firewalls frequently throttle or block UDP port 443, race-based handshakes select TCP fallback paths immediately. Edge tracing hooks inspect object metadata to debug streaming issues, bypassing QUIC's default wire-level packet encryption visibility constraints.
8Reaching Streaming Metric Parity
Extensive testing on iOS and Android confirmed that MoQ matched legacy RUSH reliability and streaming-quality metrics without introducing creator-facing regressions. Proving parity validates production readiness for high-volume ingest workloads. This milestone establishes the operational confidence and telemetry baselines required to expand the architecture into full downstream video playback distribution.
9Future Trajectory Toward Interactive AI
Meta plans to expand MoQ across all family apps while introducing standardized QMUX fallback to retire RUSH entirely. Beyond standard live streaming, engineering teams are testing MoQ for real-time interactive AI interfaces. The protocol's low-latency bidirectional pipeline uniquely handles simultaneous user signaling, voice feeds, and generative media streams together.
Original article: Engineering at Meta — Meta Deploys Media Over QUIC for Instagram Live Video Ingest