aiomoqt relay
Marz Researchaiomoqt-relay.marzresearch.net:4443
A deployment of aiomoqt, operated by Marz Research. 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
- aiomoqt/0.14.1
- Protocols accepted
- moqt-22, h3, moqt-20, moqt-18, moqt-16, moq-00
- Media delivery
- delivered, first object 163ms
- Violations recorded
- none
Certificate
- Subject
- CN=aiomoqt-relay.marzresearch.net
- Issuer
- C=US, O=Let's Encrypt, CN=YE1
- Valid until
- 2027-01-16 72 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 | ✓ ok | ✓ ok |
| 20 QUIC | ✓ err | ✓ err | ✓ err | ✓ ok | ✓ ok | ✓ ok | ✓ ok |
| 18 QUIC | ✓ err | ✓ err | ✓ err | ✓ ok | ✓ ok | ✓ ok | ✓ ok |
| 16 QUIC | ✓ err | ✓ err | ✓ err | ✓ ok | ✓ ok | · | ✓ ok |
| 14 QUIC | ✓ err | ✓ err | ✓ err | ✓ 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
- 326ms
- First object
- 163ms
- 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 | standby The relay accepted it and never subscribed to it while a subscriber was waiting. | accepted, REQUEST_OK in 163 ms | — | — |
| second publisher disconnected | serving The relay accepted it and subscribed to it. | accepted, REQUEST_OK in 163 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 2 “track ended” |
| differing payloads | each object once 15 delivered | second publisher | ended by the relay | PUBLISH_DONE 2 “track ended” |
A fresh subscription after the publisher left: delivered, the relay subscribed to the first publisher, first object in 328 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
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 22 · QUIC
- 0x06 max_filter_ranges = 16
- 0x07 moqt_implementation = aiomoqt/0.14.1
draft 20 · QUIC
- 0x06 max_filter_ranges = 16
- 0x07 moqt_implementation = aiomoqt/0.14.1
draft 18 · QUIC
- 0x07 moqt_implementation = aiomoqt/0.14.1
draft 16 · QUIC
- 0x02 max_request_id = 10000
- 0x07 moqt_implementation = aiomoqt/0.14.1
draft 14 · QUIC
- 0x07 not defined by this draft = aiomoqt/0.14.1 (moqt_implementation in 15–23)
- 0x02 max_request_id = 10000
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.
1 Nov 2026 → 2 Nov 2026
- No longer seen: A control message's declared length must match its content.
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 | 14, 16, 18, 20, 22 | Object delivered end to end | relay offered the track | — | no switch-over, publisher on standby |
| 4 Nov 2026 | yes | 14, 16, 18, 20, 22 | Object delivered end to end | relay offered the track | — | no switch-over, publisher on standby |
| 3 Nov 2026 | yes | 14, 16, 18, 20, 22 | Object delivered end to end | relay offered the track | — | no switch-over, publisher on standby |
| 2 Nov 2026 | yes | 14, 16, 18, 20, 22 | Object delivered end to end | relay offered the track | — | no switch-over, publisher on standby |
| 1 Nov 2026 | yes | 14, 16, 18, 20, 22 | Object delivered end to end | relay offered the track | 1 | no switch-over, publisher on standby |
| 31 Oct 2026 | yes | 14, 16, 18, 20, 22 | Object delivered end to end | relay offered the track | 1 | no switch-over, publisher on standby |
| 30 Oct 2026 | yes | 14, 16, 18, 20, 22 | Object delivered end to end | relay offered the track | 1 | no switch-over, publisher on standby |
| 29 Oct 2026 | yes | 14, 16, 18, 20, 22 | Object delivered end to end | relay offered the track | 1 | no switch-over, publisher on standby |
| 27 Oct 2026 | yes | 14, 16, 18, 20, 22 | Object delivered end to end | — | 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.