MOQtail SyncPlay
MOQtailsyncplay.moqtail.dev:4448
Sweep of 2026-11-01 01:22 UTC Latest report JSON
- Identifies itself as
- did not say
- Measured
- 2026-11-01 01:23 UTC
- Measured from
- Helsinki, Finland
- Probe
- moqtap-probe 0.7.0 (fcd05c5302c4)
- Drafts negotiated
- draft 14
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=*.moqtail.dev
- Issuer
- C=US, O=Let's Encrypt, CN=YR1
- Valid until
- 2026-12-09 38 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 |
|---|---|---|---|---|---|---|---|
| 14 WT | ✓ err 26 ms | ✓ err 26 ms | ✗ 3,000 ms | ✗ 3,000 ms | ✓ ok 26 ms | · | ✗ 26 ms |
- SUBSCRIBE · draft 14 · WT SUBSCRIBE_ERROR 4 “Unknown track namespace”.
- FETCH · draft 14 · WT FETCH_ERROR 4 “Track does not exist”.
- PUBLISH · draft 14 · WT Refused. The connection failed with no error code.
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 | closed The relay closed its session while the other publisher was present. | accepted, PUBLISH_NAMESPACE_OK in 26 ms | — | Session ended: an unreadable reply |
| second publisher | standby The relay accepted it and never subscribed to it while a subscriber was waiting. | accepted, PUBLISH_NAMESPACE_OK in 26 ms | — | — |
| Track | Objects | From | When the publisher left | Ended by |
|---|---|---|---|---|
| identical payloads | nothing arrived | — | not measured | — |
| differing payloads | nothing arrived | — | not measured | — |
Specification violations
Each new request must carry the next Request ID in the sender's sequence. request_id_out_of_sequence
Draft 14 over WebTransport, during the delivery run, routing the subscription
- Specification
- draft-ietf-moq-transport-14, Section 9.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 14 · WT
- 0x02 max_request_id = 2305843009213694000
Measured by sweep
| Sweep | Probe | Reachable | Drafts | Requests answered | Delivery | Offers a track | Certificate valid until | Violations | Two publishers |
|---|---|---|---|---|---|---|---|---|---|
| 1 Nov 2026 | 0.7.0 fcd05c5302c4 | yes | draft 14 | 14 WT: 3 of 6 | Namespace accepted, track never asked for14 WT | not attempted | 2026-12-09 | request_id_out_of_sequence 14 WT | no defects |
| 31 Oct 2026 | 0.7.0 fcd05c5302c4 | yes | draft 14 | 14 WT: 3 of 6 | Namespace accepted, track never asked for14 WT | not attempted | 2026-12-09 | request_id_out_of_sequence 14 WT | no defects |
| 30 Oct 2026 | 0.7.0 fcd05c5302c4 | yes | draft 14 | 14 WT: 3 of 6 | Namespace accepted, track never asked for14 WT | not attempted | 2026-12-09 | request_id_out_of_sequence 14 WT | no defects |
| 29 Oct 2026 | 0.7.0 632a80524083 | yes | draft 14 | 14 WT: 3 of 6 | Namespace accepted, track never asked for14 WT | not attempted | 2026-12-09 | request_id_out_of_sequence 14 WT | no defects |
| 27 Oct 2026 | 0.5.0 74c287bac814 | yes | draft 14 | 14 WT: 3 of 6 | Namespace accepted, track never asked for14 WT | — | 2026-12-09 | request_id_out_of_sequence 14 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.