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
- delivered, first object 114ms
- Violations recorded
- none
Certificate
- Subject
- CN=ibc25.moqtail.dev
- Issuer
- C=US, O=Let's Encrypt, CN=YE1
- Valid until
- 2026-09-06 expired 9 days ago
- Trust
- expired
- 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 |
|---|---|---|---|---|---|
| 11 WT | ✓ err | ✓ err | ✗ | · | · |
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
- 227ms
- First object
- 114ms
- Stream framing
- preserved
- Second subscriber
- delivered
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 11 · WT
- 0x02 max_request_id = 2305843009213694000
Notes
- — WebTransport completes only with certificate verification disabled
- — the peer is up but 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.