All endpoints

Cloudflare draft-18 interop

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

Cloudflare's separate draft-18 interop endpoint, exercised by the MoQ interop runner and treated as a development endpoint rather than a production relay.

What this is

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

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
draft 18
Identifies itself as
did not say
Media delivery
not attempted
Violations recorded
none
Address families
IPv4

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 runs this draft-18 interop endpoint separately from its draft-14 and draft-16 relays, and it is exercised in the MoQ interop runner — it appears in that project’s implementations.json.

As of the IETF 126 interop it was not yet at parity with the production relays: control-plane conformance passed and single-subscriber object delivery worked after moq-rs updates in July 2026, but delivery under concurrent subscribers still failed — with three subscribers, one SUBSCRIBE timed out and the receiving subscribers got a partial object set. Treat it as a development endpoint rather than a production relay.

That is a report from the interop runner, not from this probe. The TestLab sweep does not test concurrent subscribers beyond the two the delivery probe uses.

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.