Sign in
All relays

MOQtail IBC2025

MOQtail

ord.ibc25.moqtail.dev:443

Sweep of 2026-11-10 01:29 UTC Latest report JSON

Identifies itself as
did not say
Measured
2026-11-10 01:33 UTC
Measured from
Helsinki, Finland
Probe
moqtap-probe 0.7.0 (ee97a7ac6179)
Drafts negotiated
draft 11
WT IPv4

A deployment of MOQtail. About this endpoint

At a glance

Protocols accepted
h3
Media delivery
Namespace accepted, track never asked for
Violations recorded
1

Certificate

Subject
CN=ibc25.moqtail.dev
Issuer
C=US, O=Let's Encrypt, CN=YE1
Valid until
2026-12-28 49 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
11 WT ✓ err 123 ms ✓ err 124 ms ✗ 3,000 ms ✗ 3,000 ms ✓ ok 122 ms ··
  • SUBSCRIBE · draft 11 · WT SUBSCRIBE_ERROR 4 “Unknown track namespace”.
  • FETCH · draft 11 · WT FETCH_ERROR 4 “Track does not exist”.

Media delivery

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

Namespace accepted, track never asked for draft 11 · WebTransport

The subscription routed to the publisher could not be read. The endpoint broke a rule of the draft: each new request must carry the next Request ID in the sender's sequence.

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.

The relay closed a serving publisher’s session early draft 11 · WebTransport
Publisher Role Announcement Subscribed to Ended by the relay
first publisher closed The relay closed its session while the other publisher was present. accepted, ANNOUNCE_OK in 123 ms — Session ended: an unreadable reply
second publisher standby The relay accepted it and never subscribed to it while a subscriber was waiting. accepted, ANNOUNCE_OK in 115 ms — —
Track Objects From When the publisher left Ended by
identical payloads nothing arrived — not measured —
differing payloads nothing arrived — not measured SUBSCRIBE_DONE 2 “Publisher disconnected”

Specification violations

Each new request must carry the next Request ID in the sender's sequence. request_id_out_of_sequence

Draft 11 over WebTransport, during the delivery run, routing the subscription

Specification
draft-ietf-moq-transport-11, Section 8.1
“If an endpoint receives a Request ID that is not valid for the peer, or a new request with a Request ID that is not expected, it MUST close the session with Invalid Request ID.”
Required response
close the session with Invalid Request ID (0x4)

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 11 · WT

  • 0x02 max_request_id = 2305843009213694000

Measured by sweep

SweepProbeReachableDraftsRequests answeredDeliveryOffers a trackCertificate valid untilViolationsTwo publishers
10 Nov 20260.7.0 ee97a7ac6179yesdraft 1111 WT: 3 of 5Namespace accepted, track never asked for11 WTnot attempted2026-12-28request_id_out_of_sequence 11 WTno defects
9 Nov 20260.7.0 ee97a7ac6179yesdraft 1111 WT: 3 of 5Namespace accepted, track never asked for11 WTnot attempted2026-12-28request_id_out_of_sequence 11 WTno defects
8 Nov 20260.7.0 ee97a7ac6179yesdraft 1111 WT: 3 of 5Namespace accepted, track never asked for11 WTnot attempted2026-12-28request_id_out_of_sequence 11 WTno defects
7 Nov 20260.7.0 ee97a7ac6179yesdraft 1111 WT: 3 of 5Namespace accepted, track never asked for11 WTnot attempted2026-12-28request_id_out_of_sequence 11 WTno defects
6 Nov 20260.7.0 ee97a7ac6179yesdraft 1111 WT: 3 of 5Namespace accepted, track never asked for11 WTnot attempted2026-12-28request_id_out_of_sequence 11 WTno defects
5 Nov 20260.7.0 ee97a7ac6179yesdraft 1111 WT: 3 of 5Namespace accepted, track never asked for11 WTnot attempted2026-12-28request_id_out_of_sequence 11 WTno defects
4 Nov 20260.7.0 0da3083d8bdeyesdraft 1111 WT: 3 of 5Namespace accepted, track never asked for11 WTnot attempted2026-12-28request_id_out_of_sequence 11 WTno defects
3 Nov 20260.7.0 fcd05c5302c4yesdraft 1111 WT: 3 of 5Namespace accepted, track never asked for11 WTnot attempted2026-12-28request_id_out_of_sequence 11 WTno defects
2 Nov 20260.7.0 fcd05c5302c4yesdraft 1111 WT: 3 of 5Namespace accepted, track never asked for11 WTnot attempted2026-12-28request_id_out_of_sequence 11 WTno defects
1 Nov 20260.7.0 fcd05c5302c4yesdraft 1111 WT: 3 of 5Namespace accepted, track never asked for11 WTnot attempted2026-12-28request_id_out_of_sequence 11 WTno defects
31 Oct 20260.7.0 fcd05c5302c4yesdraft 1111 WT: 3 of 5Namespace accepted, track never asked for11 WTnot attempted2026-12-28request_id_out_of_sequence 11 WTno defects
30 Oct 20260.7.0 fcd05c5302c4yesdraft 1111 WT: 3 of 5Namespace accepted, track never asked for11 WTnot attempted2026-12-28request_id_out_of_sequence 11 WTno defects
29 Oct 20260.7.0 632a80524083yesdraft 1111 WT: 3 of 5Namespace accepted, track never asked for11 WTnot attempted2026-12-28request_id_out_of_sequence 11 WTno defects
27 Oct 20260.5.0 74c287bac814yesdraft 1111 WT: 3 of 5Namespace accepted, track never asked for11 WT—2026-12-28request_id_out_of_sequence 11 WT—

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.

Get in touch Debug it yourself