moqx (OpenMOQ CI)
OpenMOQmoqx-main.ci.openmoq.org:4433/moq-relay
A deployment of moqx, operated by OpenMOQ. 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
- Meta MoQ C++ Draft-16
- Protocols accepted
- moqt-16, h3, moqt-18
- Media delivery
- delivered, first object 115ms
- Violations recorded
- none
Certificate
- Subject
- CN=moqx-main.ci.openmoq.org
- Issuer
- C=US, O=Let's Encrypt, CN=YR1
- Valid until
- 2027-02-02 90 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 |
|---|---|---|---|---|---|---|---|
| 18 QUIC | ✓ err | ✓ err | ✓ err | ✓ ok | ✓ ok | ✓ ok | ✓ ok |
| 16 QUIC | ✓ err | ✓ err | ✓ err | ✓ 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
- 231ms
- First object
- 115ms
- 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 | cancelled The relay accepted it, then withdrew its namespace. | accepted, REQUEST_OK in 115 ms | — | Namespace withdrawn: stream reset (code 1) |
| second publisher disconnected | serving The relay accepted it and subscribed to it. | accepted, REQUEST_OK in 116 ms | identical payloads, differing payloads | — |
| Track | Objects | From | When the publisher left | Ended by |
|---|---|---|---|---|
| identical payloads | each object once 15 delivered | — | ended by the relay | PUBLISH_DONE 4294967295 “closed locally” |
| differing payloads | each object once 15 delivered | second publisher | ended by the relay | PUBLISH_DONE 4294967295 “closed locally” |
A fresh subscription after the publisher left: refused with REQUEST_ERROR 16 “no such namespace or track”.
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 18 · QUIC
- 0x07 moqt_implementation = Meta MoQ C++ Draft-16
- 0x40b54 not defined by this draft = 347243613479778800
draft 16 · QUIC
- 0x02 max_request_id = 100
- 0x04 max_auth_token_cache_size = 1024
- 0x07 moqt_implementation = Meta MoQ C++ Draft-16
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 → relay offered the track.
| Sweep | Reachable | Drafts | Delivery | Offers a track | Violations | Two publishers |
|---|---|---|---|---|---|---|
| 5 Nov 2026 | yes | 16, 18 | Object delivered end to end | relay offered the track | — | no defects |
| 4 Nov 2026 | yes | 16, 18 | Object delivered end to end | relay offered the track | — | no defects |
| 3 Nov 2026 | yes | 16, 18 | Object delivered end to end | relay offered the track | — | no defects |
| 2 Nov 2026 | yes | 16, 18 | Object delivered end to end | relay offered the track | — | no defects |
| 1 Nov 2026 | yes | 16, 18 | Object delivered end to end | relay offered the track | — | no defects |
| 31 Oct 2026 | yes | 16, 18 | Object delivered end to end | relay offered the track | — | no defects |
| 30 Oct 2026 | yes | 16, 18 | Object delivered end to end | relay offered the track | — | no defects |
| 29 Oct 2026 | yes | 16, 18 | Object delivered end to end | relay offered the track | — | no defects |
| 27 Oct 2026 | yes | 16, 18 | Object delivered end to end | — | — | — |
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.