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.

Sweep of 2026-11-03 01:25 UTC, measured from Helsinki, Finland, by moqtap-probe 0.7.0 (fcd05c5302c4)

Latest sweep JSON CSV

22/26
endpoints answered
9/10
implementations answered
10
drafts negotiated across the fleet
8/9
implementations delivered a published object

3 endpoints with no published implementation are not counted.

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

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

2 specification violations: namespace_tuple_size ×2

Paramount stitcher

Paramount

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

QUIC WT drafts 14–22 IPv4

Identifies itself as moq-lite-rs

Delivery not attempted. No draft the relay speaks accepted a namespace.

1 specification violation: request_id_ceiling

Red5 MoQ relay

Red5

moq-relay.red5.net:4433/moq

QUIC WT drafts 14–22 IPv4

Delivery not attempted. The session this step needed did not open. The session did not open: no answer before the deadline during MoQT setup.

5 specification violations: control_message_length ×2duplicate_parameterparameter_out_of_scoperequest_id_ceiling

imquic

Meetecho

lminiero.it:9000

QUIC WT drafts 16–22 IPv4

Identifies itself as imquic 0.0.3/alpha

Object delivered end to end

Two publishers: serving / refused

Nokia Research draft-18

Nokia

moqt.nokiaresearch.com:8443/moq

QUIC WT drafts 17–22 IPv4

Identifies itself as StreamForge MOQ v19

Object delivered end to end

Two publishers: serving / serving

3 specification violations: parameter_out_of_scope ×3

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

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

Two publishers: cancelled / serving

1 specification violation: duplicate_track_alias

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

Two publishers: serving / serving

Cloudflare draft-16

Cloudflare

draft-16.cloudflare.mediaoverquic.com:443

QUIC WT drafts 15–16 IPv4 IPv6

Delivery not attempted. No draft the relay speaks accepted a namespace.

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

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

Two publishers: serving / refused

Cloudflare draft-18 interop

Cloudflare

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

QUIC WT draft 18 IPv4

Delivery not attempted. No draft the relay speaks accepted a namespace.

libquicr (quicr.org)

Cisco

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

QUIC WT draft 18 IPv4

Object delivered end to end

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: request_id_out_of_sequence

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

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

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

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

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

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: request_id_out_of_sequence

MOQtail TimeTravel

MOQtail

timetravel.moqtail.dev:4445

WT draft 11 IPv4

Namespace accepted, track never asked for

Two publishers: closed / standby

1 specification violation: request_id_out_of_sequence

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: closed / standby

No connection in this sweep

  • Cloudflare draft-07 Cloudflare Withdrawn

    draft-07.cloudflare.mediaoverquic.com:443

    Name resolution failed.

  • ord.abr.moqtail.dev:443

    Name resolution failed.

  • quichemoq.dev:443

    QUIC: no answer before the deadline during the QUIC handshake after 8,000 ms.

    WebTransport: no answer before the deadline during opening the WebTransport session after 8,000 ms.

  • moq.wink.co:4443/moq

    QUIC: no answer before the deadline during the QUIC handshake after 8,000 ms.

    WebTransport: no answer before the deadline during opening the WebTransport session after 8,000 ms.

Not dialled in this sweep

Method

Each endpoint is contacted directly over both transports and every draft it might speak, and what comes back is recorded as it arrived.

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.