aiomoqt relay
Marz Researchaiomoqt-relay.marzresearch.net:4443
Sweep of 2026-10-27 01:21 UTC Latest report JSON
- Identifies itself as
- aiomoqt/0.14.0.dev675+gbbeb489
- Measured
- 2026-10-27 01:27 UTC
- Probe
- moqtap-probe 0.5.0 (74c287bac814)
- Drafts negotiated
- drafts 14, 16, 18, 20, 22
- Drafts the operator lists
- drafts 14, 16, 18, 20, 22
A deployment of aiomoqt, operated by Marz Research. About this endpoint
At a glance
- Protocols accepted
- moqt-22, h3, moqt-20, moqt-18, moqt-16, moq-00
- Media delivery
- delivered
- Violations recorded
- 1
Certificate
- Subject
- CN=aiomoqt-relay.marzresearch.net
- Issuer
- C=US, O=Let's Encrypt, CN=YE1
- Valid until
- 2027-01-16 82 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 |
|---|---|---|---|---|---|---|---|
| 22 QUIC | ✓ err 169 ms | ✓ err 169 ms | ✓ err 169 ms | ✓ ok 169 ms | ✓ ok 169 ms | ✓ ok 169 ms | ✓ ok 170 ms |
| 20 QUIC | ✓ err 170 ms | ✓ err 170 ms | ✓ err 169 ms | ✓ ok 169 ms | ✓ ok 169 ms | ✓ ok 170 ms | ✓ ok 170 ms |
| 18 QUIC | ✓ err 169 ms | ✓ err 169 ms | ✓ err 169 ms | ✓ ok 168 ms | ✓ ok 169 ms | ✓ ok 169 ms | ✓ ok 169 ms |
| 16 QUIC | ✓ err 168 ms | ✓ err 168 ms | ✓ err 169 ms | ✓ ok 168 ms | ✓ ok 169 ms | · | ✓ ok 169 ms |
| 14 QUIC | ✓ err 169 ms | ✓ err 171 ms | – | ✓ ok 169 ms | ✓ ok 169 ms | · | ✓ ok 170 ms |
- SUBSCRIBE · drafts 16, 18, 20, 22 · QUIC REQUEST_ERROR 16 “track does not exist”.
- SUBSCRIBE · draft 14 · QUIC SUBSCRIBE_ERROR 4 “track does not exist”.
- FETCH · drafts 16, 18, 20, 22 · QUIC REQUEST_ERROR 16 “track does not exist”.
- FETCH · draft 14 · QUIC FETCH_ERROR 4 “track does not exist”.
- TRACK_STATUS · drafts 16, 18, 20, 22 · QUIC REQUEST_ERROR 16 “track not served here”.
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
- 365ms
- First object
- 169ms
- Stream framing
- streams kept as sent
- Second subscriber
- Same object delivered to a second subscriber
Specification violations
A control message's declared length must match its content. control_message_length
Draft 14 over QUIC, during the control message probe (TRACK_STATUS)
- Specification
- draft-ietf-moq-transport-14, Section 9
- 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
- 0x06 max_filter_ranges = 16
- 0x07 moqt_implementation = aiomoqt/0.14.0.dev675+gbbeb489
draft 20 · QUIC
- 0x06 max_filter_ranges = 16
- 0x07 moqt_implementation = aiomoqt/0.14.0.dev675+gbbeb489
draft 18 · QUIC
- 0x07 moqt_implementation = aiomoqt/0.14.0.dev675+gbbeb489
draft 16 · QUIC
- 0x02 max_request_id = 10000
- 0x07 moqt_implementation = aiomoqt/0.14.0.dev675+gbbeb489
draft 14 · QUIC
- 0x07 not defined by this draft = aiomoqt/0.14.0.dev675+gbbeb489 (moqt_implementation in 15–22)
- 0x02 max_request_id = 10000
Measured by sweep
| Sweep | Probe | Reachable | Drafts | Requests answered | Delivery | Offers a track | Certificate valid until | Violations |
|---|---|---|---|---|---|---|---|---|
| 27 Oct 2026 | 0.5.0 74c287bac814 | yes | drafts 14, 16, 18, 20, 22 | 22 QUIC: 7 of 720 QUIC: 7 of 718 QUIC: 7 of 716 QUIC: 6 of 614 QUIC: 5 of 5 | Object delivered end to end22 QUIC | — | 2027-01-16 | control_message_length 14 QUIC |
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.