Sign in
All endpoints

Cloudflare draft-14

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

Cloudflare's public draft-14 MoQ Transport endpoint, in alpha and open for testing and development.

What this is

Operated by
Cloudflare
Running
moq-rs
Published URL
https://draft-14.cloudflare.mediaoverquic.com:443/moq
Drafts the operator lists
draft 14
TestLab id
cloudflare-draft-14

What TestLab measured

2026-11-12 01:30 UTC

Transports answered
QUIC and WebTransport
Drafts negotiated
draft 14
Identifies itself as
did not say
Media delivery
delivered
Certificate valid until
2027-01-02
Address families
IPv4, IPv6
Violations recorded
none

Also recorded during the sweep — conditions of the connection rather than findings about the protocol

  • — The endpoint is up and refused the offered protocols on at least one transport.
Full TestLab report

Certificate, per-draft control message support, the delivery run and every recorded violation in full.

Cloudflare operates this endpoint as a public draft-14 MoQ Transport relay, described as alpha and available for testing and development of MoQ applications.

The lists below are what Cloudflare publishes about the endpoint.

Supported messages (published)

  • SUBSCRIBE, SUBSCRIBE_OK, SUBSCRIBE_ERROR, UNSUBSCRIBE
  • PUBLISH_NAMESPACE, PUBLISH_NAMESPACE_OK, PUBLISH_NAMESPACE_ERROR, PUBLISH_NAMESPACE_CANCEL, PUBLISH_NAMESPACE_DONE
  • PUBLISH_OK, PUBLISH_DONE
  • TRACK_STATUS, TRACK_STATUS_OK
  • SETUP messages (CLIENT_SETUP, SERVER_SETUP)

Not supported (published)

  • GOAWAY
  • MAX_REQUEST_ID, REQUESTS_BLOCKED
  • SUBSCRIBE_UPDATE
  • PUBLISH_ERROR
  • FETCH, FETCH_OK, FETCH_ERROR, FETCH_CANCEL
  • TRACK_STATUS_ERROR
  • SUBSCRIBE_NAMESPACE, SUBSCRIBE_NAMESPACE_OK, SUBSCRIBE_NAMESPACE_ERROR, UNSUBSCRIBE_NAMESPACE

Elsewhere running moq-rs

3 other endpoints run the same implementation. All of them are run by the same operator as this one.

Is this your endpoint?

If something here is wrong, tell us — we keep what each result rests on, so a disputed one gets re-read rather than re-argued. We can also run this against endpoints that are not public.