libquicr (quicr.org)
Ciscous-west-2.relay.quicr.org:33437/relay
A deployment of libquicr, operated by Cisco. 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
- us-west-2.relay.public — under 0xf1, which draft 18 does not define
- Protocols accepted
- moqt-18, h3
- Media delivery
- delivered, first object 173ms
- 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 67 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 |
|---|---|---|---|---|---|---|---|
| 18 QUIC | ✓ ok | ✓ err | ✓ err | ✓ ok | ✓ ok | ✓ ok | ✓ 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
- 7/7
- Groups / subgroups
- 2 / 3
- Subscribe answered
- 173ms
- First object
- 173ms
- 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 184 ms | identical payloads, differing payloads | — |
| second publisher | serving The relay accepted it and subscribed to it. | accepted, REQUEST_OK in 174 ms | identical payloads, differing 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 395 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 194 ms after | — |
A fresh subscription after the publisher left: delivered, first object in 387 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. 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 18 · QUIC
- 0xf1 not defined by this draft = us-west-2.relay.public
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
- Transports: quic → quic, web_transport.
27 Oct 2026 → 29 Oct 2026 · measured differently
- Offering a track: not measured → relay offered the track.
| Sweep | Reachable | Drafts | Delivery | Offers a track | Violations | Two publishers |
|---|---|---|---|---|---|---|
| 5 Nov 2026 | yes | 18 | Object delivered end to end | relay offered the track | — | mixed payloads, duplicate objects |
| 4 Nov 2026 | yes | 18 | Object delivered end to end | relay offered the track | — | mixed payloads, duplicate objects |
| 3 Nov 2026 | yes | 18 | Object delivered end to end | relay offered the track | — | mixed payloads, duplicate objects |
| 2 Nov 2026 | yes | 18 | Object delivered end to end | relay offered the track | — | mixed payloads, duplicate objects |
| 1 Nov 2026 | yes | 18 | Object delivered end to end | relay offered the track | — | mixed payloads, duplicate objects |
| 31 Oct 2026 | yes | 18 | Object delivered end to end | relay offered the track | — | mixed payloads, duplicate objects |
| 30 Oct 2026 | yes | 18 | Object delivered end to end | relay offered the track | — | mixed payloads, duplicate objects |
| 29 Oct 2026 | yes | 18 | Object delivered end to end | relay offered the track | — | mixed payloads, duplicate objects |
| 27 Oct 2026 | yes | 18 | 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.