All endpoints

Cloudflare draft-16

draft-16.cloudflare.mediaoverquic.com:443

Cloudflare's public draft-16 MoQ Transport endpoint, deployed globally alongside the draft-14 one and the version the moq-rs main branch targets.

What this is

Operated by
Cloudflare
Running
moq-rs
Published URL
https://draft-16.cloudflare.mediaoverquic.com
Published as speaking
draft-16 what its operator says, not what was measured
TestLab id
cloudflare-draft-16

What TestLab measured

What this endpoint answered on 2026-09-14. One sweep, on one occasion — not a claim about availability, and not a grade.

Transports answered
QUIC and WebTransport
Drafts answered
drafts 15–16
Identifies itself as
did not say
Media delivery
not attempted
Violations recorded
none
Address families
IPv4, IPv6

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

  • — the peer is up but 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 public MoQ Transport relays running both draft-14 and draft-16 of the protocol globally. This draft-16 deployment is the one the moq-rs main branch targets — the repository states that the implementation targets draft-ietf-moq-transport-16 and that this forms the basis of the production deployment.

The endpoint is AAAA-only in DNS, so a client without IPv6 will not reach it at all.

Deployed relay state and repository state are genuinely different things here. Cloudflare’s deployments run roughly one to two weeks behind moq-rs main, so what this endpoint answers on a given day and what the codebase does at HEAD can differ, and a defect measured here belongs either to moq-rs or to this deployment’s configuration — the two are not interchangeable.

Elsewhere running moq-rs

3 other endpoints run the same implementation. Each is a separate deployment at its own version and configuration, so what one answers is not a claim about the others. 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.