Sign in
All relays

aiomoqt relay

Marz Research

aiomoqt-relay.marzresearch.net:4443

QUIC WT drafts 14, 16, 18, 20, 22 IPv4

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.15.0.dev1118+g1049da0
Protocols accepted
moqt-22, h3, moqt-20, moqt-18, moqt-16, moq-00
Media delivery
delivered, first object 162ms
Violations recorded
none

Certificate

Subject
CN=aiomoqt-relay.marzresearch.net
Issuer
C=US, O=Let's Encrypt, CN=YE1
Valid until
2027-01-16 69 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 SUBSCRIBEFETCHTRACK_STATUSSUBSCRIBE_NAMESPACEPUBLISH_NAMESPACESUBSCRIBE_TRACKSPUBLISH
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.

Object delivered end to end draft 22 · QUIC
Objects delivered
7/7
Groups / subgroups
2 / 3
Subscribe answered
326ms
First object
162ms
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.

Measured draft 22 · QUIC
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 162 ms identical payloads, differing payloads —
second publisher serving The relay accepted it and subscribed to it. accepted, REQUEST_OK in 163 ms identical payloads, differing payloads —
Track Objects From When the publisher left Ended by
identical payloads each object once 42 delivered — carried on from the other publisher first object 343 ms after —
differing payloads each object once 42 delivered first publisher, second publisher carried on from the other publisher first object 148 ms after —

A fresh subscription after the publisher left: delivered, first object in 163 ms.

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.15.0.dev1118+g1049da0

draft 20 · QUIC

  • 0x06 max_filter_ranges = 16
  • 0x07 moqt_implementation = aiomoqt/0.15.0.dev1118+g1049da0

draft 18 · QUIC

  • 0x07 moqt_implementation = aiomoqt/0.15.0.dev1118+g1049da0

draft 16 · QUIC

  • 0x02 max_request_id = 10000
  • 0x07 moqt_implementation = aiomoqt/0.15.0.dev1118+g1049da0

draft 14 · QUIC

  • 0x07 not defined by this draft = aiomoqt/0.15.0.dev1118+g1049da0 (moqt_implementation in 15–23)
  • 0x02 max_request_id = 10000

History

12 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.

  • 6 Nov 2026 → 7 Nov 2026

    • With two publishers, no longer seen: Ended or stalled a subscription when its publisher left, while the other publisher of the track was still accepted and reachable. With two publishers, no longer seen: Accepted a publisher and never subscribed to it while a subscription to its namespace was live.
  • 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.
SweepReachableDraftsDeliveryOffers a trackViolationsTwo publishers
8 Nov 2026yes14, 16, 18, 20, 22Object delivered end to endrelay offered the track—no defects
7 Nov 2026yes14, 16, 18, 20, 22Object delivered end to endrelay offered the track—no defects
6 Nov 2026yes14, 16, 18, 20, 22Object delivered end to endrelay offered the track—no switch-over, publisher on standby
5 Nov 2026yes14, 16, 18, 20, 22Object delivered end to endrelay offered the track—no switch-over, publisher on standby
4 Nov 2026yes14, 16, 18, 20, 22Object delivered end to endrelay offered the track—no switch-over, publisher on standby
3 Nov 2026yes14, 16, 18, 20, 22Object delivered end to endrelay offered the track—no switch-over, publisher on standby
2 Nov 2026yes14, 16, 18, 20, 22Object delivered end to endrelay offered the track—no switch-over, publisher on standby
1 Nov 2026yes14, 16, 18, 20, 22Object delivered end to endrelay offered the track1no switch-over, publisher on standby
31 Oct 2026yes14, 16, 18, 20, 22Object delivered end to endrelay offered the track1no switch-over, publisher on standby
30 Oct 2026yes14, 16, 18, 20, 22Object delivered end to endrelay offered the track1no switch-over, publisher on standby
29 Oct 2026yes14, 16, 18, 20, 22Object delivered end to endrelay offered the track1no switch-over, publisher on standby
27 Oct 2026yes14, 16, 18, 20, 22Object 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.