MOQtail n1 Chicago
MOQtailrelay.n1.ord.moqtail.dev:443
Sweep of 2026-10-29 01:29 UTC Latest report JSON
- Identifies itself as
- moqtail/0.15.0+1873793
- Measured
- 2026-10-29 01:34 UTC
- Measured from
- Helsinki, Finland
- Probe
- moqtap-probe 0.7.0 (632a80524083)
- Drafts negotiated
- draft 18
A deployment of MOQtail. About this endpoint
At a glance
- Protocols accepted
- moqt-18, h3
- Media delivery
- delivered
- 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 73 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 |
|---|---|---|---|---|---|---|---|
| 18 QUIC | ✓ err 130 ms | ✓ err 130 ms | ✓ err 130 ms | ✓ ok 130 ms | ✓ ok 132 ms | ✓ ok 131 ms | ✓ ok 130 ms |
- SUBSCRIBE · draft 18 · QUIC REQUEST_ERROR 16 “Unknown track namespace”.
- FETCH · draft 18 · QUIC REQUEST_ERROR 16 “Track does not exist”.
- TRACK_STATUS · draft 18 · QUIC REQUEST_ERROR 16 “No publisher found”.
Media delivery
One publisher and two subscribers, to see whether an object published through this endpoint reaches a client that asked for it.
- Objects delivered
- 7/7
- Groups / subgroups
- 2 / 3
- Subscribe answered
- 238ms
- First object
- 116ms
- 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.
| 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 115 ms | differing payloads, identical payloads | — |
| second publisher | serving The relay accepted it and subscribed to it. | accepted, REQUEST_OK in 130 ms | differing payloads, identical payloads | — |
| Track | Objects | From | When the publisher left | Ended by |
|---|---|---|---|---|
| identical payloads | each object once 43 delivered | — | carried on from the other publisher first object 312 ms after | — |
| differing payloads | each object once 43 delivered | first publisher, second publisher | carried on from the other publisher first object 116 ms after | — |
A fresh subscription after the publisher left: delivered, first object in 310 ms.
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
| Sweep | Probe | Reachable | Drafts | Requests answered | Delivery | Offers a track | Certificate valid until | Violations | Two publishers |
|---|---|---|---|---|---|---|---|---|---|
| 29 Oct 2026 | 0.7.0 632a80524083 | yes | draft 18 | 18 QUIC: 7 of 7 | Object delivered end to end18 QUIC | relay offered the track | 2027-01-09 | — | no defects |
| 27 Oct 2026 | 0.5.0 74c287bac814 | yes | draft 18 | 18 QUIC: 4 of 7 | Namespace 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.