Sign in

What MoQ relays actually do

Every publicly reachable MoQ Transport endpoint we could find, tested for what it actually supports: which drafts it speaks, which control messages it answers, and whether media gets through.

22/27
endpoints reachable
11
drafts answered across the fleet
14
delivered a published object
15
spec violations recorded

How to read this

  • This is a snapshot, not a service level. These endpoints are publicly reachable and open for interop testing; some are also commercial products. Either way, what is recorded is what one endpoint did on one occasion — not a claim about anyone's product or its availability.
  • An error reply counts as support. A relay that answers REQUEST_ERROR to a namespace it does not host has understood the message. What is recorded as missing is a message that got no answer at all, or that closed the session.

moq.dev CDN

moq.dev

cdn.moq.dev:443/anon

QUIC WT drafts 14–22 IPv4 IPv6

Identifies itself as moq-lite-rs

Object delivered end to end first object 39ms

Two publishers: standby / serving no switch-over publisher on standby

2 specification violations

Paramount stitcher

Paramount

34-72-6-160.sslip.io:443

QUIC WT drafts 14–22 IPv4

Identifies itself as moq-lite-rs

1 specification violation

Red5 MoQ relay

Red5

moq-relay.red5.net:4433/moq

QUIC WT drafts 14–22 IPv4

5 specification violations

imquic

Meetecho

lminiero.it:9000

QUIC WT drafts 16–22 IPv4

Identifies itself as imquic 0.0.3/alpha

Object delivered end to end first object 33ms

Two publishers: serving / refused

Nokia Research draft-18

Nokia

moqt.nokiaresearch.com:8443/moq

QUIC WT drafts 17–23 IPv4

Identifies itself as StreamForge MOQ v19

Object delivered end to end first object 3ms

Two publishers: serving / serving

3 specification violations

aiomoqt relay

Marz Research

aiomoqt-relay.marzresearch.net:4443

QUIC WT drafts 14, 16, 18, 20, 22 IPv4

Identifies itself as aiomoqt/0.14.0

Object delivered end to end first object 162ms

Two publishers: standby / serving no switch-over publisher on standby

moxygen

Meta

fb.mvfst.net:9448/moq-relay

QUIC WT drafts 14, 16, 18, 22 IPv4

Identifies itself as Meta MoQ C++ Draft-14

Object delivered end to end first object 124ms

Two publishers: cancelled / serving

1 specification violation

Nokia Research draft-22

Nokia

moqt.nokiaresearch.com:4443/moq

QUIC WT drafts 20–22 IPv4

Identifies itself as StreamForge MOQ v20

Object delivered end to end first object 3ms

Two publishers: serving / serving

Cloudflare draft-16

Cloudflare

draft-16.cloudflare.mediaoverquic.com:443

QUIC WT drafts 15–16 IPv4 IPv6

moqx (OpenMOQ CI)

OpenMOQ

moqx-main.ci.openmoq.org:4433/moq-relay

QUIC WT drafts 16, 18 IPv4

Identifies itself as Meta MoQ C++ Draft-16

Object delivered end to end first object 115ms

Two publishers: cancelled / serving

Cloudflare draft-14

Cloudflare

draft-14.cloudflare.mediaoverquic.com:443/moq

QUIC WT draft 14 IPv4 IPv6

Object delivered end to end first object 3ms

Two publishers: serving / refused

Cloudflare draft-18 interop

Cloudflare

draft-18-interop.cloudflare.mediaoverquic.com:443/moq

QUIC WT draft 18 IPv4

libquicr (quicr.org)

Cisco

us-west-2.relay.quicr.org:33437/relay

QUIC WT draft 18 IPv4

Object delivered end to end first object 182ms

Two publishers: serving / serving mixed payloads duplicate objects

MOQtail IBC2025

MOQtail

ord.ibc25.moqtail.dev:443

WT draft 11 IPv4

Namespace accepted, track never asked for

Two publishers: standby / closed

1 specification violation

MOQtail n1 Chicago

MOQtail

relay.n1.ord.moqtail.dev:443

QUIC WT draft 22 IPv4

Identifies itself as moqtail/0.17.0+2c3efc6

Object delivered end to end first object 116ms

Two publishers: serving / serving

MOQtail n1 Frankfurt

MOQtail

relay.n1.fra.moqtail.dev:443

QUIC WT draft 22 IPv4

Identifies itself as moqtail/0.17.0+2c3efc6

Object delivered end to end first object 24ms

Two publishers: serving / serving

MOQtail n1 Osaka

MOQtail

relay.n1.osa.moqtail.dev:443

QUIC WT draft 22 IPv4

Identifies itself as moqtail/0.17.0+2c3efc6

Object delivered end to end first object 266ms

Two publishers: serving / serving

MOQtail n1 Singapore

MOQtail

relay.n1.sin.moqtail.dev:443

QUIC WT draft 22 IPv4

Identifies itself as moqtail/0.17.0+2c3efc6

Object delivered end to end first object 201ms

Two publishers: serving / serving

MOQtail relay

MOQtail

relay.moqtail.dev:443

QUIC WT draft 22 IPv4

Identifies itself as moqtail/0.17.0+2c3efc6

Object delivered end to end first object 25ms

Two publishers: serving / serving

MOQtail SyncPlay

MOQtail

syncplay.moqtail.dev:4448

WT draft 14 IPv4

Namespace accepted, track never asked for

Two publishers: closed / standby

1 specification violation

MOQtail TimeTravel

MOQtail

timetravel.moqtail.dev:4445

WT draft 11 IPv4

Namespace accepted, track never asked for

Two publishers: standby / closed

1 specification violation

MOQtail WatchParty

MOQtail

watch-party.moqtail.dev:4446

QUIC WT draft 16 IPv4

Identifies itself as moqtail/0.14.1+fbdbc75

Namespace accepted, track never asked for

Two publishers: standby / closed

5 further endpoints in the fleet did not answer this sweep and are not listed.

Changes in the latest sweep

4 Nov 2026, against each endpoint's previous result measured the same way.

No endpoint changed.

Method

Each endpoint is contacted directly over both transports and every draft it might speak, and what comes back is recorded as it arrived. Results are point-in-time and describe one run, not a continuous measurement.

Measured by probe release 0da3083d8bde.

Want this run against your own relay? Ask for a report. And if something here is wrong about your relay, tell us — we keep what each result rests on, so a disputed one gets re-read rather than re-argued.

Debug what this found

The same decoder behind this sweep runs in your browser's DevTools, and reads the capture files it produces.