Cloudflare draft-14
Cloudflaredraft-14.cloudflare.mediaoverquic.com:443/moq
Sweep of 2026-11-11 01:27 UTC Latest report JSON
- Identifies itself as
- did not say
- Measured
- 2026-11-11 01:27 UTC
- Measured from
- Helsinki, Finland
- Probe
- moqtap-probe 0.7.0 (ee97a7ac6179)
- Drafts negotiated
- draft 14
- Drafts the operator lists
- draft 14
A deployment of moq-rs, operated by Cloudflare. About this endpoint
At a glance
- Protocols accepted
- moq-00, h3
- Media delivery
- delivered
- Violations recorded
- none
Certificate
- Subject
- CN=*.cloudflare.mediaoverquic.com
- Issuer
- C=US, O=Let's Encrypt, CN=YE2
- Valid until
- 2027-01-02 53 days left when measured
- Trust
- Publicly trusted
- Verification
- Completed with the certificate verified
Control messages
What each request got back, per draft. ok and err are both answers; ✗ is a request refused or left unanswered; a dash is a request our side did not complete. Times run from the request to its answer; each request waited up to 3,000 ms.
| Draft | SUBSCRIBE | FETCH | TRACK_STATUS | SUBSCRIBE_NAMESPACE | PUBLISH_NAMESPACE | SUBSCRIBE_TRACKS | PUBLISH |
|---|---|---|---|---|---|---|---|
| 14 QUIC | ✓ err 339 ms | ✗ 3,000 ms | ✓ err 1 ms | ✗ 3,000 ms | ✓ ok 261 ms | · | ✗ 3,000 ms |
- SUBSCRIBE · draft 14 · QUIC SUBSCRIBE_ERROR 4 “not found: Track not found [error:1679ae66-c579-4f98-af06-8e4ba74bbecf]”.
- TRACK_STATUS · draft 14 · QUIC TRACK_STATUS_ERROR 4 “Track not found”.
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
- 87ms
- First object
- 3ms
- 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 363 ms | identical payloads, differing 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:8bf52174-d84b-4a17-befa-a48f84701ba5]”.
Specification violations
None recorded.
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
Measured by sweep
| Sweep | Probe | Reachable | Drafts | Requests answered | Delivery | Offers a track | Certificate valid until | Violations | Two publishers |
|---|---|---|---|---|---|---|---|---|---|
| 11 Nov 2026 | 0.7.0 ee97a7ac6179 | yes | draft 14 | 14 QUIC: 3 of 6 | Object delivered end to end14 QUIC | relay refused the track | 2027-01-02 | — | no defects |
| 10 Nov 2026 | 0.7.0 ee97a7ac6179 | yes | draft 14 | 14 QUIC: 3 of 6 | Object delivered end to end14 QUIC | relay refused the track | 2027-01-02 | — | no defects |
| 9 Nov 2026 | 0.7.0 ee97a7ac6179 | yes | draft 14 | 14 QUIC: 3 of 6 | Object delivered end to end14 QUIC | relay refused the track | 2027-01-02 | — | no defects |
| 8 Nov 2026 | 0.7.0 ee97a7ac6179 | yes | draft 14 | 14 QUIC: 3 of 6 | Object delivered end to end14 QUIC | relay refused the track | 2027-01-02 | — | no defects |
| 7 Nov 2026 | 0.7.0 ee97a7ac6179 | yes | draft 14 | 14 QUIC: 3 of 6 | Object delivered end to end14 QUIC | relay refused the track | 2027-01-02 | — | no defects |
| 6 Nov 2026 | 0.7.0 ee97a7ac6179 | yes | draft 14 | 14 QUIC: 3 of 6 | Object delivered end to end14 QUIC | relay refused the track | 2027-01-02 | — | no defects |
| 5 Nov 2026 | 0.7.0 ee97a7ac6179 | yes | draft 14 | 14 QUIC: 3 of 6 | Object delivered end to end14 QUIC | relay refused the track | 2027-01-02 | — | no defects |
| 4 Nov 2026 | 0.7.0 0da3083d8bde | yes | draft 14 | 14 QUIC: 3 of 6 | Object delivered end to end14 QUIC | relay refused the track | 2027-01-02 | — | no defects |
| 3 Nov 2026 | 0.7.0 fcd05c5302c4 | yes | draft 14 | 14 QUIC: 3 of 6 | Object delivered end to end14 QUIC | relay refused the track | 2027-01-02 | — | no defects |
| 2 Nov 2026 | 0.7.0 fcd05c5302c4 | yes | draft 14 | 14 QUIC: 3 of 6 | Object delivered end to end14 QUIC | relay refused the track | 2027-01-02 | — | no defects |
| 1 Nov 2026 | 0.7.0 fcd05c5302c4 | yes | draft 14 | 14 QUIC: 3 of 6 | Object delivered end to end14 QUIC | relay refused the track | 2027-01-02 | — | no defects |
| 31 Oct 2026 | 0.7.0 fcd05c5302c4 | yes | draft 14 | 14 QUIC: 3 of 6 | Object delivered end to end14 QUIC | relay refused the track | 2027-01-02 | — | no defects |
| 30 Oct 2026 | 0.7.0 fcd05c5302c4 | yes | draft 14 | 14 QUIC: 3 of 6 | Object delivered end to end14 QUIC | relay refused the track | 2027-01-02 | — | no defects |
| 29 Oct 2026 | 0.7.0 632a80524083 | yes | draft 14 | 14 QUIC: 3 of 6 | Object delivered end to end14 QUIC | relay refused the track | 2027-01-02 | — | no defects |
| 27 Oct 2026 | 0.5.0 74c287bac814 | yes | draft 14 | 14 QUIC: 3 of 6 | Object delivered end to end14 QUIC | — | 2027-01-02 | — | — |
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.