MOQtail IBC2025
MOQtailord.ibc25.moqtail.dev:443
A deployment of MOQtail. 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
- did not say
- 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 54 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 |
|---|---|---|---|---|---|---|---|
| 11 WT | ✓ err | ✓ err | ✗ | ✗ | ✓ ok | · | · |
Media delivery
One publisher and two subscribers, to see whether an object published through this endpoint reaches a client that asked for it.
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.
| 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, ANNOUNCE_OK in 115 ms | — | — |
| second publisher | closed The relay closed its session while the other publisher was present. | accepted, ANNOUNCE_OK in 115 ms | — | Session ended: an unreadable reply |
| Track | Objects | From | When the publisher left | Ended by |
|---|---|---|---|---|
| identical payloads | nothing arrived | — | not measured | SUBSCRIBE_DONE 2 “Publisher disconnected” |
| differing payloads | nothing arrived | — | not measured | — |
Specification violations
Each new request must carry the next Request ID in the sender's sequence.
Draft 11 over WebTransport, during the delivery run, routing the subscription
- Specification
- draft-ietf-moq-transport-11, Section 8.1
- 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
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.
27 Oct 2026 → 29 Oct 2026 · measured differently
- Offering a track: not measured → not attempted.
| Sweep | Reachable | Drafts | Delivery | Offers a track | Violations | Two publishers |
|---|---|---|---|---|---|---|
| 5 Nov 2026 | yes | 11 | Namespace accepted, track never asked for | not attempted | 1 | no defects |
| 4 Nov 2026 | yes | 11 | Namespace accepted, track never asked for | not attempted | 1 | no defects |
| 3 Nov 2026 | yes | 11 | Namespace accepted, track never asked for | not attempted | 1 | no defects |
| 2 Nov 2026 | yes | 11 | Namespace accepted, track never asked for | not attempted | 1 | no defects |
| 1 Nov 2026 | yes | 11 | Namespace accepted, track never asked for | not attempted | 1 | no defects |
| 31 Oct 2026 | yes | 11 | Namespace accepted, track never asked for | not attempted | 1 | no defects |
| 30 Oct 2026 | yes | 11 | Namespace accepted, track never asked for | not attempted | 1 | no defects |
| 29 Oct 2026 | yes | 11 | Namespace accepted, track never asked for | not attempted | 1 | no defects |
| 27 Oct 2026 | yes | 11 | Namespace accepted, track never asked for | — | 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.