Sign in

Public MoQ relay endpoints

A URL somebody operates, running somebody's code. Three things that cross, and are worth keeping apart: the endpoint, the operator, and the implementation.

27
endpoints listed
13
operators
10
implementations behind them
22/27
with a TestLab report

How to read this

  • An endpoint is not an implementation. One implementation is many deployments, each at its own version and configuration. A defect measured on one deployment is not a defect in the codebase until someone has checked which of the two it belongs to. The components themselves are in the ecosystem directory .
  • "Not measured" is not a failure. An endpoint with no result is normal. The probe may not have completed a session, the name may not resolve, or the endpoint may not be in the fleet at all — three different situations, none of which is a statement about anybody's relay, and each said explicitly rather than left to an absence.
  • Unknown is a real answer. 3 endpoints below have no published implementation. That is not a row waiting to be filled in — nobody has published what runs there, and the entry says so instead of leaving the field blank.

MOQtail

11 endpoints

MOQtail ABR

ord.abr.moqtail.dev:443

The hostname did not resolve when the fleet was last swept — a fact about the name, not about any relay behind it.

MOQtail draft-22

relay.moqtail.dev:8244

Not measured. The endpoint was not probed in the last sweep.

MOQtail IBC2025

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

relay.n1.ord.moqtail.dev:443

QUIC WT draft 22 IPv4

Object delivered end to end first object 115ms

Two publishers: serving / serving

MOQtail n1 Frankfurt

relay.n1.fra.moqtail.dev:443

QUIC WT draft 22 IPv4

Object delivered end to end first object 24ms

Two publishers: serving / serving

MOQtail n1 Osaka

relay.n1.osa.moqtail.dev:443

QUIC WT draft 22 IPv4

Object delivered end to end first object 272ms

Two publishers: serving / serving

MOQtail n1 Singapore

relay.n1.sin.moqtail.dev:443

QUIC WT draft 22 IPv4

Object delivered end to end first object 207ms

Two publishers: serving / serving

MOQtail relay

relay.moqtail.dev:443

QUIC WT draft 22 IPv4

Object delivered end to end first object 26ms

Two publishers: serving / serving

MOQtail SyncPlay

syncplay.moqtail.dev:4448

WT draft 14 IPv4

Namespace accepted, track never asked for

Two publishers: closed / standby

1 specification violation

MOQtail TimeTravel

timetravel.moqtail.dev:4445

WT draft 11 IPv4

Namespace accepted, track never asked for

Two publishers: closed / standby

1 specification violation

MOQtail WatchParty

watch-party.moqtail.dev:4446

QUIC WT draft 16 IPv4

Namespace accepted, track never asked for

Two publishers: closed / standby

moq-rs

4 endpoints

Cloudflare draft-07

Withdrawn

draft-07.cloudflare.mediaoverquic.com:443

The hostname did not resolve when the fleet was last swept — a fact about the name, not about any relay behind it.

Cloudflare draft-14

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

QUIC WT draft 14 IPv4 IPv6

Object delivered end to end first object 2ms

Two publishers: serving / refused

Cloudflare draft-16

draft-16.cloudflare.mediaoverquic.com:443

QUIC WT drafts 15–16 IPv4 IPv6

Answered on the control plane. Object delivery was not attempted.

Cloudflare draft-18 interop

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

QUIC WT draft 18 IPv4

Answered on the control plane. Object delivery was not attempted.

No published implementation

3 endpoints , more than one operator

Nokia Research draft-18

Nokia

moqt.nokiaresearch.com:8443/moq

QUIC WT drafts 17–23 IPv4

Object delivered end to end first object 2ms

Two publishers: serving / serving

3 specification violations

Nokia Research draft-22

Nokia

moqt.nokiaresearch.com:4443/moq

QUIC WT drafts 20–22 IPv4

Object delivered end to end first object 3ms

Two publishers: serving / serving

Wink

Wink

moq.wink.co:4443/moq

Not measured. The probe did not complete a connection on the last sweep, which says nothing about the endpoint.

moq.dev

2 endpoints , more than one operator

moq.dev CDN

moq.dev

cdn.moq.dev:443/anon

QUIC WT drafts 14–22 IPv4 IPv6

Object delivered end to end first object 40ms

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

Answered on the control plane. Object delivery was not attempted.

1 specification violation

aiomoqt

1 endpoint

aiomoqt relay

aiomoqt-relay.marzresearch.net:4443

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

Object delivered end to end first object 163ms

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

Google Quiche

1 endpoint

quiche-moq

quichemoq.dev:443

Not measured. The probe did not complete a connection on the last sweep, which says nothing about the endpoint.

imquic

1 endpoint

imquic

lminiero.it:9000

QUIC WT drafts 16–22 IPv4

Object delivered end to end first object 31ms

Two publishers: serving / refused

libquicr

1 endpoint

libquicr (quicr.org)

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

QUIC WT draft 18 IPv4

Object delivered end to end first object 173ms

Two publishers: serving / serving mixed payloads duplicate objects

moqx

1 endpoint

moqx (OpenMOQ CI)

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

QUIC WT drafts 16, 18 IPv4

Object delivered end to end first object 115ms

Two publishers: cancelled / serving

Moxygen

1 endpoint

moxygen

fb.mvfst.net:9448/moq-relay

QUIC WT drafts 14, 16, 18, 22 IPv4

Object delivered end to end first object 115ms

Two publishers: cancelled / serving

1 specification violation

Red5 Pro

1 endpoint

Red5 MoQ relay

moq-relay.red5.net:4433/moq

QUIC WT drafts 14–22 IPv4

Answered on the control plane. Object delivery was not attempted.

5 specification violations

Where the results come from

The measurements above are read from one TestLab sweep, run on 2026-11-05. 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 — and no endpoint here is graded.

If an endpoint is missing, or something here is wrong about yours, tell us . We keep what each result rests on, so a disputed one gets re-read rather than re-argued.