moq.dev CDN
moq.devcdn.moq.dev:443/anon
A deployment of moq.dev. 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
- moq-lite-rs
- Protocols accepted
- moqt-22, h3, moqt-21, moqt-20, moqt-19, moqt-18, moqt-17, moqt-16, moqt-15, moq-00
- Media delivery
- delivered, first object 40ms
- Violations recorded
- 2
Certificate
- Subject
- CN=cdn.moq.pro
- Issuer
- C=US, O=Let's Encrypt, CN=YE1
- Valid until
- 2026-12-12 38 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 |
|---|---|---|---|---|---|---|---|
| 22 QUIC | ✓ err | ✓ err | ✓ err | ✓ ok | ✓ ok | ✓ err | ✓ err |
| 21 QUIC | ✓ err | ✓ err | ✓ err | ✓ ok | ✓ ok | ✓ err | ✓ err |
| 20 QUIC | ✓ err | ✓ err | ✓ err | ✓ ok | ✓ ok | ✓ err | ✓ err |
| 19 QUIC | ✓ err | ✓ err | ✓ err | ✓ ok | ✓ ok | ✓ err | ✓ err |
| 18 QUIC | ✓ err | ✓ err | ✓ err | ✓ ok | ✓ ok | ✓ err | ✓ err |
| 17 QUIC | ✓ err | ✓ err | ✓ err | ✓ ok | ✓ ok | · | ✓ err |
| 16 QUIC | – | – | – | ✓ ok | – | · | – |
| 15 QUIC | – | – | – | – | – | · | – |
| 14 QUIC | – | – | – | – | – | · | – |
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
- 5/7
- Groups / subgroups
- 2 / 2
- Subscribe answered
- 78ms
- First object
- 40ms
- 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 | standby The relay accepted it and never subscribed to it while a subscriber was waiting. | accepted, REQUEST_OK in 38 ms | — | — |
| second publisher disconnected | serving The relay accepted it and subscribed to it. | accepted, REQUEST_OK in 38 ms | differing payloads, identical payloads | — |
| Track | Objects | From | When the publisher left | Ended by |
|---|---|---|---|---|
| identical payloads | each object once 15 delivered | — | ended by the relay | PUBLISH_DONE 0 “internal error” |
| differing payloads | each object once 15 delivered | second publisher | ended by the relay | PUBLISH_DONE 0 “internal error” |
A fresh subscription after the publisher left: delivered, the relay subscribed to the first publisher, first object in 82 ms.
Ended or stalled a subscription when its publisher left, while the other publisher of the track was still accepted and reachable.
Draft 22, on the track with identical payloads
- Requirement
- A relay must forward Objects of one track from every publisher of it to the matching subscriptions.
- Specification
- draft-ietf-moq-transport-22, Section 7.3
Ended or stalled a subscription when its publisher left, while the other publisher of the track was still accepted and reachable.
Draft 22, on the track with differing payloads
- Requirement
- A relay must forward Objects of one track from every publisher of it to the matching subscriptions.
- Specification
- draft-ietf-moq-transport-22, Section 7.3
Accepted a publisher and never subscribed to it while a subscription to its namespace was live.
Draft 22, on the first publisher
- Requirement
- A relay must send a SUBSCRIBE to every publisher that announced a matching namespace.
- Specification
- draft-ietf-moq-transport-22, Section 7.6
Specification violations
A track namespace must have no more fields than the draft allows, and at least one where the draft requires it.
Draft 15 over QUIC, during the control message probe (SUBSCRIBE)
- Specification
- draft-ietf-moq-transport-15, Section 2.4.1
- Required response
- close the session with error code 0x3
A track namespace must have no more fields than the draft allows, and at least one where the draft requires it.
Draft 14 over QUIC, during the control message probe (SUBSCRIBE)
- Specification
- draft-ietf-moq-transport-14, Section 2.4.1
- Required response
- close the session with error code 0x3
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 22 · QUIC
- 0x07 moqt_implementation = moq-lite-rs
- 0x40b54 not defined by this draft = 3936146074472874000
- 0x40b5a not defined by this draft = 1
- 0x40b5c not defined by this draft = 1
draft 21 · QUIC
- 0x07 moqt_implementation = moq-lite-rs
- 0x40b54 not defined by this draft = 3936146074472874000
- 0x40b5a not defined by this draft = 1
- 0x40b5c not defined by this draft = 1
draft 20 · QUIC
- 0x07 moqt_implementation = moq-lite-rs
- 0x40b54 not defined by this draft = 3936146074472874000
- 0x40b5a not defined by this draft = 1
- 0x40b5c not defined by this draft = 1
draft 19 · QUIC
- 0x07 moqt_implementation = moq-lite-rs
- 0x40b54 not defined by this draft = 3936146074472874000
- 0x40b5a not defined by this draft = 1
- 0x40b5c not defined by this draft = 1
draft 18 · QUIC
- 0x07 moqt_implementation = moq-lite-rs
- 0x40b54 not defined by this draft = 3936146074472874000
- 0x40b5a not defined by this draft = 1
- 0x40b5c not defined by this draft = 1
draft 17 · QUIC
- 0x07 moqt_implementation = moq-lite-rs
- 0x40b54 not defined by this draft = 3936146074472874000
- 0x40b5a not defined by this draft = 1
- 0x40b5c not defined by this draft = 1
draft 16 · QUIC
- 0x02 max_request_id = 4294967295
- 0x07 moqt_implementation = moq-lite-rs
- 0x40b5a not defined by this draft = 1
- 0x40b5c not defined by this draft = 1
draft 15 · QUIC
- 0x40b5a not defined by this draft = 1
- 0x40b5c not defined by this draft = 1
- 0x02 max_request_id = 4294967295
- 0x07 moqt_implementation = moq-lite-rs
draft 14 · QUIC
- 0x40b5c not defined by this draft = 1
- 0x02 max_request_id = 4294967295
- 0x40b5a not defined by this draft = 1
- 0x07 not defined by this draft = moq-lite-rs (moqt_implementation in 15–23)
The relay names itself moq-lite-rs under option 0x07, which is MOQT_IMPLEMENTATION from draft-15 onward. Draft-14 assigns nothing to 0x07, so a draft-14 client has no reason to read it as a name.
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.
29 Oct 2026 → 30 Oct 2026 · measured differently
- Delivery: Namespace accepted, track never asked for → Object delivered end to end.
- Offering a track: not attempted → relay refused the track.
27 Oct 2026 → 29 Oct 2026 · measured differently
- Offering a track: not measured → not attempted.
| Sweep | Reachable | Drafts | Delivery | Offers a track | Violations | Two publishers |
|---|---|---|---|---|---|---|
| 5 Nov 2026 | yes | 14, 15, 16, 17, 18, 19, 20, 21, 22 | Object delivered end to end | relay refused the track | 1 | no switch-over, publisher on standby |
| 4 Nov 2026 | yes | 14, 15, 16, 17, 18, 19, 20, 21, 22 | Object delivered end to end | relay refused the track | 1 | no switch-over, publisher on standby |
| 3 Nov 2026 | yes | 14, 15, 16, 17, 18, 19, 20, 21, 22 | Object delivered end to end | relay refused the track | 1 | no switch-over, publisher on standby |
| 2 Nov 2026 | yes | 14, 15, 16, 17, 18, 19, 20, 21, 22 | Object delivered end to end | relay refused the track | 1 | no switch-over, publisher on standby |
| 1 Nov 2026 | yes | 14, 15, 16, 17, 18, 19, 20, 21, 22 | Object delivered end to end | relay refused the track | 1 | no switch-over, publisher on standby |
| 31 Oct 2026 | yes | 14, 15, 16, 17, 18, 19, 20, 21, 22 | Object delivered end to end | relay refused the track | 1 | no switch-over, publisher on standby |
| 30 Oct 2026 | yes | 14, 15, 16, 17, 18, 19, 20, 21, 22 | Object delivered end to end | relay refused the track | 1 | no switch-over, publisher on standby |
| 29 Oct 2026 | yes | 14, 15, 16, 17, 18, 19, 20, 21, 22 | Namespace accepted, track never asked for | not attempted | 1 | no switch-over, publisher on standby |
| 27 Oct 2026 | yes | 14, 15, 16, 17, 18, 19, 20, 21, 22 | Namespace accepted, track never asked for | — | 1 | — |
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.