---
title: Everyone's Talking About MoQ. Here's Where It Shows Up First. -- Uplynk Blog
description: Explore how MoQ can transform low-latency live video streaming, focusing on contribution before distribution, as broadcasters transition from satellite to IP.
image: https://connect.uplynk.com/hubfs/moq_hubspotv3.png
---

[![Uplynk](https://connect.uplynk.com/hubfs/Uplynk_LogoType_WhiteText.png)](https://www.uplynk.com/)

[Solutions](https://www.uplynk.com/solutions/live-sports-events) [Products](https://www.uplynk.com/products/ingest) [Services](https://www.uplynk.com/services/build) [Customers & Partners](https://www.uplynk.com/customer-results/) [Insights & News](https://www.uplynk.com/newsroom/press-releases/) [Company](https://www.uplynk.com/company/about) [Book a demo](https://www.uplynk.com/book-demo/)

[← Back to Blog](https://connect.uplynk.com/blog)

# Everyone's Talking About MoQ. Here's Where It Shows Up First.

Shahar Mor | November 17, 2026

![](https://connect.uplynk.com/hubfs/moq_hubspotv3.png)

I recently co-hosted a discussion on low latency and MoQ (Media over QUIC) with Igor Oreper from Bitmovin and Jon Dakss from Oracle Cloud Infrastructure. The room was full of people who build and run live video for a living, and the questions were practical. Is MoQ real? When does it matter? Where do we start?

My answer is that MoQ will show up first in contribution, where live feeds enter master control, well before it reaches viewers through distribution. Before I explain why, it's worth explaining what MoQ actually is, because much of the conversation skips that part.

## What MoQ is, in plain terms

MoQ is a new way to move live media over the internet, from one point to another or from one source to millions, with much less delay, or what engineers call latency. Today, live video forces a trade-off between speed and scale. A video call is nearly instant, but it's hard to send to a million viewers. A live stream on your TV or phone reaches millions, but it usually runs several seconds behind real time. MoQ is designed to remove that trade-off: close-to-real-time delay at streaming scale.

## How MoQ differs from HLS, DASH, and WebRTC

Most streaming today uses HLS and DASH. In their classic form, they cut video into segments a few seconds long and send them over HTTP, the same technology that loads a web page. That's reliable and scales well, because CDNs are built to hand out files. The cost is delay: players wait for whole segments and keep a few in reserve, so seconds add up. Low-latency variants send partial segments as they're produced, which helps, but adds complexity and typically still lands in the low seconds.

WebRTC takes the opposite approach. It sends media continuously, which is why video calls feel instant. The cost is scale: WebRTC relies on specialized media servers that negotiate and manage state for every session, and that gets expensive and complicated with large audiences.

One point from the discussion stuck with me - we've been hacking HTTP to deliver video for years. Now we finally have a protocol designed to move video over the internet. MoQ wasn't adapted from a protocol built for web pages. It was designed from the start for media that has to arrive fast and at scale.

It runs on QUIC, the transport that already carries HTTP/3 and a large share of today's web traffic. QUIC carries many independent streams over one connection, so a lost packet in one stream doesn't hold up the others, and a connection can survive a network change, like a phone moving from Wi-Fi to cellular. MoQ builds on that by letting senders and relays prioritize the newest media and drop stale data under congestion, instead of stalling to deliver everything late. For live video, a late frame is often worse than a missing one.

On top of QUIC, MoQ uses a pub/sub model with relays in the middle. A source publishes a feed once, relays pass it along, and anyone authorized subscribes to it. The relays are designed to be generic and cache-friendly, so they can be deployed the way CDN servers are today, rather than as specialized per-session media servers. That's what lets MoQ scale.

MoQ is being developed as an open standard at the IETF, the group behind most of the internet's core protocols. It is still a draft: the specification is evolving, and products that support it are early. That maturity level shapes where MoQ gets adopted first.

## Why contribution comes first

When people talk about "moving video," they usually mean one of two jobs. Contribution is getting video in: the feed from a camera at a stadium, a production truck, a local affiliate, or a remote studio, sent to master control to be switched, branded, scheduled, and prepared for air. On our platform, that's how live sources reach Cloud MCR, our cloud-based master control. Distribution is getting video out: the finished product reaching viewers through OTT apps, linear channels, VOD libraries, FAST channels, and social platforms.

Two differences put contribution first. The first is control. A contribution path connects a known sender to a known receiver, and the broadcaster or its partners run the equipment at both ends, so they can trial a new protocol on a handful of feeds. Distribution is the opposite: every player, app, browser, smart TV, and CDN has to support MoQ first, and that takes years. The second is sensitivity to delay. A viewer rarely notices a couple of seconds. An operator cutting between live sources and lining up ad breaks notices every frame. The same logic applies to some of what leaves our platform. When a finished channel is handed to a FAST platform or a partner, both ends of that handoff are under contract, so it could adopt MoQ long before every viewer's device does.

Latency alone isn't the whole argument, though. SRT, RIST, and Zixi already deliver low-latency contribution, and do it well. What MoQ adds is a different delivery model, which matters most once master control moves to the cloud.

When I say contribution comes first, I don't mean MoQ is ready for broadcast-grade contribution today. It isn't. I mean contribution is where the first real trials and first production use will happen, because it's the part of the chain where a new protocol can actually be adopted.

## Why now: the move off satellite

The reason to think about this now, rather than in a few years, is satellite. The FCC is auctioning part of the upper C-band in 2027, and satellite services in that spectrum have to move by 2030 or 2031, depending on the market. Many broadcasters still send and receive feeds over satellite, and they're planning what replaces it. Most won't flip one switch. They'll move feed by feed and site by site, mixing satellite, fiber, and IP transport for a while. That mixed transition is the situation our team designed for in the IP Convergence Framework, which we built with Zixi, Grass Valley, and BroadView and which is running in production today on proven IP transport.

MoQ won't replace today's proven IP transport overnight. The point is that the satellite-to-IP plans broadcasters make now should leave room for it.

## What it changes for master control

As an engineer, this is the part I find most interesting. Once feeds reach the cloud over IP with low enough delay for operators to switch sources and line up ad breaks in real time, the control room no longer needs to be in a single building. Operators can work from the main facility, a backup site, or home. If weather or an outage takes out one location, the channels keep running. The broadcaster behind the IP Convergence Framework already runs channels this way, from its new facility and from home.

This is where MoQ's pub/sub model matters more than its latency. Today, sending a feed to a primary and a backup control room means sending it twice, or adding a router in the middle to split it. With MoQ, a venue publishes a feed once, and relays deliver it only to the places that subscribe. A backup site can stay subscribed and ready, or join only when it's needed. Splitting a feed across sites, and failing over between them, becomes a property of the protocol instead of extra infrastructure, which makes resilience simpler and cheaper.

## Where Uplynk fits

At Uplynk, we're building MoQ support into our platform and working with partners to make sure it fits within broadcasters' satellite-to-IP plans. We're deliberate about the order: contribution first, distribution once players, devices, and delivery networks catch up. We're staying close to the distribution discussions too, because that's where our traditional strengths in personalization and control come in. Ad insertion, blackouts, and per-viewer experiences largely run on HLS and DASH manifests today, and MoQ will need new approaches for them. We intend to help shape those. It will just happen a little later.

MoQ is still maturing, and anyone claiming it's ready to replace your entire delivery chain tomorrow is overstating it. The practical step now is to decide where it fits in your plan. For most broadcasters, that means getting feeds in.

If you're planning your own move off satellite, three questions are worth asking now. Can your IP transport and cloud master control add new protocols without a rebuild? Which contribution links, where you control both ends, would make a good first MoQ trial? And which partner handoffs, such as channels delivered to FAST platforms, could follow? Answering those keeps MoQ in your plan without betting your delivery chain on a draft standard.

**Want the full technical detail on how we're moving broadcasters from satellite to IP?** [Download the IP Convergence Framework →](https://www.uplynk.com/ip-convergence/)

## Let's talk about your streaming goals.

[Talk to a Streaming Expert](https://www.uplynk.com/book-demo/)

[![Uplynk](https://connect.uplynk.com/hubfs/Uplynk_LogoType_WhiteText.png)](https://www.uplynk.com/)

Helping organizations run streaming.

#### Solutions

- [Live Sports & Events](https://www.uplynk.com/solutions/live-sports-events)
- [Broadcast & Linear TV](https://www.uplynk.com/solutions/broadcast-linear-tv)
- [Launch FAST Channels](https://www.uplynk.com/solutions/launch-fast-channels)
- [Monetize Streaming](https://www.uplynk.com/solutions/ssai-monetization)

#### Products

- [Ingest](https://www.uplynk.com/products/ingest)
- [Studio](https://www.uplynk.com/products/studio)
- [SmartPlay](https://www.uplynk.com/products/smartplay)
- [Syndicate](https://www.uplynk.com/products/syndicate)
- [Observe](https://www.uplynk.com/products/observe)

#### Customers & Partners

- [Customer Success](https://www.uplynk.com/customer-results/)
- [Technology Partners](https://www.uplynk.com/partners)

#### Company

- [About](https://www.uplynk.com/company/about)
- [Careers](https://www.uplynk.com/company/careers)
- [Contact](https://www.uplynk.com/company/contact)

© 2026 Uplynk, Inc.

[Privacy Policy](https://www.uplynk.com/legal/privacy-policy) [Terms of Service](https://www.uplynk.com/legal/terms-of-service) [Acceptable Use Policy](https://www.uplynk.com/legal/acceptable-use-policy) Cookie Settings

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Shahar Mor",
    "url" : "https://connect.uplynk.com/blog/author/shahar-mor"
  },
  "dateModified" : "2026-11-17T19:16:57.661Z",
  "datePublished" : "2026-11-17T19:16:57.000Z",
  "headline" : "Everyone's Talking About MoQ. Here's Where It Shows Up First.",
  "image" : [ "https://connect.uplynk.com/hubfs/moq_hubspotv3.png" ],
  "mainEntityOfPage" : {
    "@id" : "https://connect.uplynk.com/blog/everyones-talking-about-moq",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://connect.uplynk.com/hubfs/Uplynk_LogoType_Color-2.png"
    },
    "name" : "Uplynk"
  }
}
```