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.
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. 2 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
10 endpointsMOQtail 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 IBC2025
ord.ibc25.moqtail.dev:443
Object delivered end to end first object 114ms
MOQtail n1 Chicago
relay.n1.ord.moqtail.dev:443
Object delivered end to end first object 118ms
MOQtail n1 Frankfurt
relay.n1.fra.moqtail.dev:443
Object delivered end to end first object 47ms
MOQtail n1 Osaka
relay.n1.osa.moqtail.dev:443
Object delivered end to end first object 287ms
MOQtail n1 Singapore
relay.n1.sin.moqtail.dev:443
Object delivered end to end first object 222ms
MOQtail relay
relay.moqtail.dev:443
Object delivered end to end first object 38ms
MOQtail SyncPlay
syncplay.moqtail.dev:4448
Namespace accepted, track never asked for
1 specification violation
MOQtail TimeTravel
timetravel.moqtail.dev:4445
Namespace accepted, track never asked for
1 specification violation
MOQtail WatchParty
watch-party.moqtail.dev:4446
Namespace accepted, track never asked for
moq-rs
4 endpointsCloudflare draft-07
Withdrawndraft-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
Object delivered end to end first object 20ms
Cloudflare draft-16
draft-16.cloudflare.mediaoverquic.com:443
Answered on the control plane. Object delivery was not attempted.
Cloudflare draft-18 interop
draft-18-interop.cloudflare.mediaoverquic.com:443/moq
Answered on the control plane. Object delivery was not attempted.
moq.dev
2 endpoints , more than one operatormoq.dev CDN
moq.devcdn.moq.dev:443/anon
Answered on the control plane. Object delivery was not attempted.
1 specification violation
Paramount stitcher
Paramount34-72-6-160.sslip.io:443
Answered on the control plane. Object delivery was not attempted.
1 specification violation
No published implementation
2 endpoints , more than one operatorGoogle Quiche
1 endpointimquic
1 endpointlibquicr
1 endpointmoqx
1 endpointMoxygen
1 endpointWhere the results come from
The measurements above are read from one TestLab sweep, run on 2026-09-14. 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.