Sign in
All relays

MOQtail n1 Chicago

MOQtail

relay.n1.ord.moqtail.dev:443

Sweep of 2026-10-27 01:21 UTC Latest report JSON

Identifies itself as
moqtail/0.15.0+1873793
Measured
2026-10-27 01:25 UTC
Probe
moqtap-probe 0.5.0 (74c287bac814)
Drafts negotiated
draft 18
QUIC WT IPv4

A deployment of MOQtail. About this endpoint

At a glance

Protocols accepted
moqt-18, h3
Media delivery
Namespace and subscription accepted, nothing routed to the publisher
Violations recorded
none

Certificate

Subject
CN=*.moqtail.dev
Issuer
C=AT, O=ZeroSSL GmbH, CN=ZeroSSL ECC DV SSL CA 2
Valid until
2027-01-09 75 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 SUBSCRIBEFETCHTRACK_STATUSSUBSCRIBE_NAMESPACEPUBLISH_NAMESPACESUBSCRIBE_TRACKSPUBLISH
18 QUIC ✓ err 133 ms ✗ 3,000 ms ✗ 3,000 ms ✓ ok 123 ms ✓ ok 131 ms ✓ ok 135 ms ✗ 3,000 ms
  • SUBSCRIBE · draft 18 · QUIC REQUEST_ERROR 16 “Unknown track namespace”.

Media delivery

One publisher and two subscribers, to see whether an object published through this endpoint reaches a client that asked for it.

Namespace and subscription accepted, nothing routed to the publisher draft 18 · QUIC

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

  • 0x07 moqt_implementation = moqtail/0.15.0+1873793

Measured by sweep

SweepProbeReachableDraftsRequests answeredDeliveryOffers a trackCertificate valid untilViolations
27 Oct 20260.5.0 74c287bac814yesdraft 1818 QUIC: 4 of 7Namespace and subscription accepted, nothing routed to the publisher18 QUIC—2027-01-09—

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.