Meta moves Instagram Live ingest on iOS and Android to Media over QUIC
Meta says Instagram Live video ingest on iOS and Android now runs on Media over QUIC, an IETF standard still in development. Its case for folding separate streaming stacks into one is stated as intent, and ingest is the piece the post reports as shipped.
The Engineer · Build desk
What happened
- MoQ is an emerging IETF standard, developed with participation from Meta, Google, Akamai, Cisco, Cloudflare and academia.
- MoQ's core abstraction is a Track that publishers push and subscribers receive through relays, which cache and forward objects without parsing the media payload.
- Two subscribers to one track can run at different latencies at once, for example about 100 ms for an interactive participant and several seconds for an archival service.
Why it matters
- decision Meta's payoff is fewer transports to operate across ingest, delivery and playback. An adopter has to decide whether it is migrating one leg or all three, because ingest alone leaves the other stacks running.
- capability Meta says relays that drop, prioritize or replay objects from metadata give better congestion behavior under loss than byte-stream protocols. Loss policy then lives in the relay tier the operator runs.
- cost Adopting means running or buying relays that speak MoQ framing. Meta credits its RUSH production experience for shaping the bet, and a team without that history starts further back.
Meta's post is specific about what shipped and forward-looking about the rest. The consolidation case is written as intent. Meta says MoQ "will help simplify our protocol stack for live streaming video" [12], and that it gives the company "the foundation to build toward an architecture that is lower-latency, more resilient on unreliable networks, and more responsive for creators and viewers" [13].
The stack count it wants to cut is concrete. In Meta's example, a user who starts a live stream and then makes a voice call in the same app touches three protocol stacks, each with its own serving infrastructure, monitoring and operational expertise [5]. The post argues that a common protocol across ingest, delivery and playback "can reduce the number of custom transports and operating models that engineering teams need to maintain and improve over time" [14]. Those savings depend on playback and calls moving too, and the post describes that as something to "build toward" [13].
The RTMP framing needs care. The post lists RTMP as the ingest protocol, next to HLS and DASH for playback and WebRTC for calls [6]. Meta's own live video, though, has run for nearly a decade on RUSH, which was built to move past RTMP and was already QUIC-based [3]. Meta calls RUSH a predecessor to MoQ and says lessons from running it in production shaped the bet [4]. In our view the deployment shows that an emerging standard [2] can carry Meta's ingest on QUIC. It does not show an RTMP stack being swapped out. The portion of the post we have does not name the protocol Instagram Live ingest used immediately before, and it includes no MoQ-specific latency, stall or rollout-share figures.
The one performance claim in that portion is older. Meta says its earlier QUIC rollout achieved lower request errors, tail latency and video stalls than HTTP/2 [10]. That is a result on Meta's traffic, from before MoQ.
For it to transfer, an operator would need clients on paths where QUIC works and a relay tier that understands MoQ framing and delivery metadata [7]. The post lists a standards-based TCP fallback among MoQ's properties [11], which matters on any network where QUIC does not get through. Meta had nearly a decade of RUSH operations to draw on [3]. We'd expect a team starting from RTMP ingest to have more to build.
What to watch
- Whether Meta publishes MoQ-specific ingest numbers (latency, stalls, share of Instagram Live traffic) that can be compared with its earlier QUIC results.
- Whether Meta moves playback or voice calls onto MoQ, which is where the three-stack consolidation would show up.
- Whether the CDNs named in the IETF effort ship production MoQ relays that an RTMP-based operator can buy instead of build.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence35
- Adoption30
- Hype gap+10
- Incentives40
- Confidence55
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
Instagram Live now uses the open standard transport protocol Media over QUIC (MoQ) for live video ingest on iOS and Android.
- [2]
MoQ is an emerging IETF standard for low-latency, scalable media delivery over QUIC, developed with active participation from Meta, Google, Akamai, Cisco, Cloudflare and academia.
- [3]
For nearly a decade, Meta's live streaming video has run on Reliable Ultra-low-latency Streaming over HTTP (RUSH), an in-house QUIC-based protocol built to move past RTMP.
- [4]
Meta says RUSH was a predecessor to MoQ and that lessons learned from running RUSH in production shaped its bet on MoQ.
- [5]
In Meta's example, someone who starts a live stream and then makes a voice call on the same app touches three different protocol stacks, each with its own serving infrastructure, monitoring, and operational expertise.
- [6]
Meta's post lists RTMP for ingestion, HLS and DASH for playback, and WebRTC for real-time calls among the existing media protocols.
- [7]
The core abstraction in MoQ is a Track, an addressable stream of media objects that publishers push and subscribers receive through a network of relays; relays cache and forward objects without parsing the media payload and only need to understand the MoQ framing and delivery metadata.
- [8]
Two subscribers to the same MoQ track can run at different latencies at the same time, for example about 100 ms for an interactive participant and several seconds for an archival or buffered service, based on tunable per-subscription delivery properties.
- [9]
MoQ relays can drop, prioritize, or replay objects based on metadata, which Meta says gives better congestion behavior under loss than byte-stream protocols.
- [10]
Meta says its earlier QUIC rollout achieved lower request errors, tail latency, and video stalls than HTTP/2.
- [11]
Meta's post lists a standards-based TCP fallback among the properties of MoQ.
- [12]
Meta's post says MoQ "will help simplify our protocol stack for live streaming video".
- [13]
Meta says MoQ gives it "the foundation to build toward an architecture that is lower-latency, more resilient on unreliable networks, and more responsive for creators and viewers".
- [14]
Meta says a common protocol across ingest, delivery, and playback "can reduce the number of custom transports and operating models that engineering teams need to maintain and improve over time".
Get this ledger inside ChatGPT. Ask about any of our stories and the answer brings its figure, each claim’s verdict and the sources. Free, no account.
Sources
1 independent publisher whose own reporting we read for this story.
- engineering.fb.comShipping Media Over QUIC at Meta Scale for Instagram Live Ingest
1 article · October 12, 2026
Topics and entities
Follow any of these and your For You feed starts watching them — no settings page required.