MOQtail n1 Osaka
MOQtailrelay.n1.osa.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
- moqtail/0.17.0+2c3efc6
- Protocols accepted
- moqt-22, h3
- Media delivery
- delivered, first object 272ms
- 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 66 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 |
|---|---|---|---|---|---|---|---|
| 22 QUIC | ✓ err | ✓ err | ✓ err | ✓ ok | ✓ ok | ✓ ok | ✓ ok |
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
- 539ms
- First object
- 272ms
- Stream framing
- streams kept as sent
- Second subscriber
- Same object delivered to a second subscriber
- Offers a track
- subscription not sent
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 277 ms | differing payloads, identical payloads | — |
| second publisher | serving The relay accepted it and subscribed to it. | accepted, REQUEST_OK in 270 ms | differing payloads, identical payloads | — |
| Track | Objects | From | When the publisher left | Ended by |
|---|---|---|---|---|
| identical payloads | each object once 41 delivered | — | carried on from the other publisher first object 491 ms after | — |
| differing payloads | each object once 41 delivered | second publisher | its publisher stayed | — |
A fresh subscription after the publisher left: delivered, first object in 297 ms.
Specification violations
None recorded. Nothing this endpoint sent broke a requirement the probe checks — which is not the same as saying it implements the draft completely.
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 22 · QUIC
- 0x06 max_filter_ranges = 32
- 0x07 moqt_implementation = moqtail/0.17.0+2c3efc6
- 0x08 max_request_updates = 0
- 0x09 not defined by this draft = 0x00c0ff01 (max_control_message_size in 23)
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.
29 Oct 2026 → 30 Oct 2026 · measured differently
- Drafts answered: 18 → 22.
- Offering a track: relay offered the track → subscription not sent.
27 Oct 2026 → 29 Oct 2026 · measured differently
- Delivery: Namespace and subscription accepted, nothing routed to the publisher → Object delivered end to end.
- Offering a track: not measured → relay offered the track.
| Sweep | Reachable | Drafts | Delivery | Offers a track | Violations | Two publishers |
|---|---|---|---|---|---|---|
| 5 Nov 2026 | yes | 22 | Object delivered end to end | subscription not sent | — | no defects |
| 4 Nov 2026 | yes | 22 | Object delivered end to end | subscription not sent | — | no defects |
| 3 Nov 2026 | yes | 22 | Object delivered end to end | subscription not sent | — | no defects |
| 2 Nov 2026 | yes | 22 | Object delivered end to end | subscription not sent | — | no defects |
| 1 Nov 2026 | yes | 22 | Object delivered end to end | subscription not sent | — | no defects |
| 31 Oct 2026 | yes | 22 | Object delivered end to end | subscription not sent | — | no defects |
| 30 Oct 2026 | yes | 22 | Object delivered end to end | subscription not sent | — | no defects |
| 29 Oct 2026 | yes | 18 | Object delivered end to end | relay offered the track | — | no defects |
| 27 Oct 2026 | yes | 18 | Namespace and subscription accepted, nothing routed to the publisher | — | — | — |
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.