libquicr (quicr.org)
Ciscous-west-2.relay.quicr.org:33437/relay
Sweep of 2026-11-07 01:24 UTC Latest report JSON
- Identifies itself as
- did not say
- Measured
- 2026-11-07 01:24 UTC
- Measured from
- Helsinki, Finland
- Probe
- moqtap-probe 0.7.0 (ee97a7ac6179)
- Drafts negotiated
- draft 18
- Drafts the operator lists
- draft 18
A deployment of libquicr, operated by Cisco. About this endpoint
At a glance
- Protocols accepted
- moqt-18, h3
- Media delivery
- delivered
- Violations recorded
- none
Certificate
- Subject
- CN=us-west-2.relay.quicr.org
- Issuer
- C=US, O=Let's Encrypt, CN=YE1
- Valid until
- 2027-01-11 65 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 |
|---|---|---|---|---|---|---|---|
| 18 QUIC | ✓ ok 174 ms | ✓ err 175 ms | ✓ err 175 ms | ✓ ok 175 ms | ✓ ok 175 ms | ✓ ok 175 ms | ✓ ok 175 ms |
- FETCH · draft 18 · QUIC REQUEST_ERROR 0 “Cannot process fetch”.
- TRACK_STATUS · draft 18 · QUIC REQUEST_ERROR 16 “Track does not exist”.
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
- 7/7
- Groups / subgroups
- 2 / 3
- Subscribe answered
- 175ms
- First object
- 176ms
- Stream framing
- streams kept as sent
- Second subscriber
- Same object delivered to a second subscriber
- Offers a track
- relay offered 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, REQUEST_OK in 176 ms | differing payloads, identical payloads | — |
| second publisher | serving The relay accepted it and subscribed to it. | accepted, REQUEST_OK in 175 ms | differing payloads, identical payloads | — |
| Track | Objects | From | When the publisher left | Ended by |
|---|---|---|---|---|
| identical payloads | objects delivered twice 15 of 42 twice | — | carried on from the other publisher first object 378 ms after | — |
| differing payloads | objects with two payloads 15 of 42 with two payloads | first publisher, second publisher | carried on from the other publisher first object 183 ms after | — |
A fresh subscription after the publisher left: delivered, first object in 377 ms.
Delivered one Object with two different payloads on one subscription.
Draft 18, on the track with differing payloads
- Requirement
- An endpoint that receives one Object twice with different payloads must treat the track as malformed.
- Specification
- draft-ietf-moq-transport-18, Section 9.1
Delivered the same Object twice, with the same bytes, on one subscription.
Draft 18, on the track with identical payloads
- Requirement
- A relay should deduplicate Objects of one track arriving from more than one publisher before forwarding them.
- Specification
- draft-ietf-moq-transport-18, Section 9.3
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 18 · QUIC
- 0xf1 not defined by this draft = us-west-2.relay.public
Measured by sweep
| Sweep | Probe | Reachable | Drafts | Requests answered | Delivery | Offers a track | Certificate valid until | Violations | Two publishers |
|---|---|---|---|---|---|---|---|---|---|
| 7 Nov 2026 | 0.7.0 ee97a7ac6179 | yes | draft 18 | 18 QUIC: 7 of 7 | Object delivered end to end18 QUIC | relay offered the track | 2027-01-11 | — | mixed payloads, duplicate objects |
| 6 Nov 2026 | 0.7.0 ee97a7ac6179 | yes | draft 18 | 18 QUIC: 7 of 7 | Object delivered end to end18 QUIC | relay offered the track | 2027-01-11 | — | mixed payloads, duplicate objects |
| 5 Nov 2026 | 0.7.0 ee97a7ac6179 | yes | draft 18 | 18 QUIC: 7 of 7 | Object delivered end to end18 QUIC | relay offered the track | 2027-01-11 | — | mixed payloads, duplicate objects |
| 4 Nov 2026 | 0.7.0 0da3083d8bde | yes | draft 18 | 18 QUIC: 7 of 7 | Object delivered end to end18 QUIC | relay offered the track | 2027-01-11 | — | mixed payloads, duplicate objects |
| 3 Nov 2026 | 0.7.0 fcd05c5302c4 | yes | draft 18 | 18 QUIC: 7 of 7 | Object delivered end to end18 QUIC | relay offered the track | 2027-01-11 | — | mixed payloads, duplicate objects |
| 2 Nov 2026 | 0.7.0 fcd05c5302c4 | yes | draft 18 | 18 QUIC: 7 of 7 | Object delivered end to end18 QUIC | relay offered the track | 2027-01-11 | — | mixed payloads, duplicate objects |
| 1 Nov 2026 | 0.7.0 fcd05c5302c4 | yes | draft 18 | 18 QUIC: 7 of 7 | Object delivered end to end18 QUIC | relay offered the track | 2027-01-11 | — | mixed payloads, duplicate objects |
| 31 Oct 2026 | 0.7.0 fcd05c5302c4 | yes | draft 18 | 18 QUIC: 7 of 7 | Object delivered end to end18 QUIC | relay offered the track | 2027-01-11 | — | mixed payloads, duplicate objects |
| 30 Oct 2026 | 0.7.0 fcd05c5302c4 | yes | draft 18 | 18 QUIC: 7 of 7 | Object delivered end to end18 QUIC | relay offered the track | 2027-01-11 | — | mixed payloads, duplicate objects |
| 29 Oct 2026 | 0.7.0 632a80524083 | yes | draft 18 | 18 QUIC: 7 of 7 | Object delivered end to end18 QUIC | relay offered the track | 2027-01-11 | — | mixed payloads, duplicate objects |
| 27 Oct 2026 | 0.5.0 74c287bac814 | yes | draft 18 | 18 QUIC: 7 of 7 | Object delivered end to end18 QUIC | — | 2027-01-11 | — | — |
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.