Cloudflare draft-14
Cloudflaredraft-14.cloudflare.mediaoverquic.com:443/moq
A deployment of moq-rs, operated by Cloudflare. Everything below was measured on this deployment, at whatever version and configuration it was running — it is not a measurement of that codebase. About this endpoint
At a glance
- Identifies itself as
- did not say
- Protocols accepted
- moq-00, h3
- Media delivery
- delivered, first object 2ms
- Violations recorded
- none
Certificate
- Subject
- CN=*.cloudflare.mediaoverquic.com
- Issuer
- C=US, O=Let's Encrypt, CN=YE2
- Valid until
- 2027-01-02 59 days left
- Trust
- Publicly trusted
- Verification
- Completed with the certificate verified
Control messages
Which control messages this endpoint answered, per draft. An error reply is still an answer — ok and err are both support; what is recorded as missing is a message that got no answer at all. A dash is neither: it means the exchange ended on our side, so nothing about this endpoint was measured there.
| Draft | SUBSCRIBE | FETCH | TRACK_STATUS | SUBSCRIBE_NAMESPACE | PUBLISH_NAMESPACE | SUBSCRIBE_TRACKS | PUBLISH |
|---|---|---|---|---|---|---|---|
| 14 QUIC | ✓ err | ✗ | ✓ err | ✗ | ✓ ok | · | ✗ |
Media delivery
One publisher and two subscribers, to see whether an object published through this endpoint reaches a client that asked for it.
- Objects delivered
- 2/7
- Groups / subgroups
- 1 / 1
- Subscribe answered
- 95ms
- First object
- 2ms
- Stream framing
- streams kept as sent
- Second subscriber
- Same object delivered to a second subscriber
- Offers a track
- relay refused the track
Two publishers of one track
Two publishers announce the same namespace and publish the same tracks, one with identical payloads and one with payloads that differ by publisher. Partway through, the publisher serving the subscribers disconnects without notice. A fresh subscription, sent afterwards, shows whether the remaining publisher could still be reached.
| Publisher | Role | Announcement | Subscribed to | Ended by the relay |
|---|---|---|---|---|
| first publisher disconnected | serving The relay accepted it and subscribed to it. | accepted, PUBLISH_NAMESPACE_OK in 404 ms | differing payloads, identical payloads | — |
| second publisher | refused The relay refused its announcement, or did not answer it. | refused, PUBLISH_NAMESPACE_ERROR 0 “done” Announced again after the other left: answer not readable. The stream ended with no reset. | — | Session ended: stream ended |
| Track | Objects | From | When the publisher left | Ended by |
|---|---|---|---|---|
| identical payloads | each object once 15 delivered | — | ended by the relay | PUBLISH_DONE 0 “closed, code=0” |
| differing payloads | each object once 15 delivered | first publisher | ended by the relay | PUBLISH_DONE 0 “closed, code=0” |
A fresh subscription after the publisher left: refused with SUBSCRIBE_ERROR 4 “not found: Track not found [error:b23e8405-ac99-44e8-a5bc-d95ee44f2310]”.
Specification violations
None recorded. Nothing this endpoint sent broke a requirement the probe checks — which is not the same as saying it implements the draft completely.
Setup parameters
What this endpoint sent back in its setup response, per draft. A parameter with no name is a code point the negotiated draft does not define.
draft 14 · QUIC
- 0x02 max_request_id = 100
History
9 sweeps, newest first. A step where the probe build or the measuring location changed is marked, and is not read as a change of the relay.
27 Oct 2026 → 29 Oct 2026 · measured differently
- Offering a track: not measured → relay refused the track.
| Sweep | Reachable | Drafts | Delivery | Offers a track | Violations | Two publishers |
|---|---|---|---|---|---|---|
| 5 Nov 2026 | yes | 14 | Object delivered end to end | relay refused the track | — | no defects |
| 4 Nov 2026 | yes | 14 | Object delivered end to end | relay refused the track | — | no defects |
| 3 Nov 2026 | yes | 14 | Object delivered end to end | relay refused the track | — | no defects |
| 2 Nov 2026 | yes | 14 | Object delivered end to end | relay refused the track | — | no defects |
| 1 Nov 2026 | yes | 14 | Object delivered end to end | relay refused the track | — | no defects |
| 31 Oct 2026 | yes | 14 | Object delivered end to end | relay refused the track | — | no defects |
| 30 Oct 2026 | yes | 14 | Object delivered end to end | relay refused the track | — | no defects |
| 29 Oct 2026 | yes | 14 | Object delivered end to end | relay refused the track | — | no defects |
| 27 Oct 2026 | yes | 14 | Object delivered end to end | — | — | — |
Notes
- — The endpoint is up and refused the offered protocols on at least one transport.
Is this your relay?
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.