moxygen
Metafb.mvfst.net:9448/moq-relay
Sweep of 2026-10-29 01:29 UTC Latest report JSON
- Identifies itself as
- Meta MoQ C++ Draft-14
- Measured
- 2026-10-29 01:29 UTC
- Measured from
- Helsinki, Finland
- Probe
- moqtap-probe 0.7.0 (632a80524083)
- Drafts negotiated
- drafts 14, 16, 18, 22
- Drafts the operator lists
- drafts 16, 18, 22
A deployment of Moxygen, operated by Meta. About this endpoint
At a glance
- Protocols accepted
- moq-00, h3, moqt-16, moqt-18, moqt-22
- Media delivery
- delivered
- Violations recorded
- 1
Certificate
- Subject
- CN=fb.mvfst.net
- Issuer
- C=US, O=Let's Encrypt, CN=YE1
- Valid until
- 2026-12-24 57 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 |
|---|---|---|---|---|---|---|---|
| 22 QUIC | ✓ err 130 ms | ✓ err 130 ms | ✓ err 130 ms | ✓ ok 132 ms | ✓ ok 130 ms | ✓ ok 130 ms | ✓ ok 130 ms |
| 18 QUIC | ✓ err 116 ms | ✓ err 114 ms | ✓ err 114 ms | ✓ ok 114 ms | ✓ ok 114 ms | ✓ ok 114 ms | ✓ ok 114 ms |
| 16 QUIC | ✓ err 116 ms | ✓ err 116 ms | ✓ err 116 ms | ✓ ok 116 ms | ✓ ok 116 ms | · | ✓ ok 116 ms |
| 14 QUIC | ✓ err 117 ms | ✓ err 117 ms | ✓ err 116 ms | ✓ ok 117 ms | ✓ ok 116 ms | · | ✓ ok 117 ms |
- SUBSCRIBE · drafts 16, 18, 22 · QUIC REQUEST_ERROR 16 “no such namespace or track”.
- SUBSCRIBE · draft 14 · QUIC SUBSCRIBE_ERROR 16 “no such namespace or track”.
- FETCH · drafts 16, 18, 22 · QUIC REQUEST_ERROR 16 “no upstream for fetch”.
- FETCH · draft 14 · QUIC FETCH_ERROR 16 “no upstream for fetch”.
- TRACK_STATUS · drafts 16, 18, 22 · QUIC REQUEST_ERROR 16 “no such namespace or track”.
- TRACK_STATUS · draft 14 · QUIC TRACK_STATUS_ERROR 16 “no such namespace or track”.
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
- 248ms
- First object
- 117ms
- Stream framing
- streams kept as sent
- Second subscriber
- Same object delivered to a second subscriber
- Offers a track
- relay offered nothing
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 116 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 | differing payloads, identical 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
One Track Alias must not be used for two tracks at once. duplicate_track_alias
Draft 22 over QUIC, during the delivery run, asking the relay to offer a track
- Specification
- draft-ietf-moq-transport-22, Section 3.1.3
- “The same Track Alias MUST NOT be used by a publisher to refer to two different Tracks simultaneously in the same session. If a subscriber receives a PUBLISH or SUBSCRIBE_OK that uses the same Track Alias as a different Track with an Established subscription, it MUST close the session with error DUPLICATE_TRACK_ALIAS.”
- Required response
- close the session with DUPLICATE_TRACK_ALIAS (0x5)
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
- 0x07 moqt_implementation = Meta MoQ C++ Draft-14
draft 18 · QUIC
- 0x07 moqt_implementation = Meta MoQ C++ Draft-14
draft 16 · QUIC
- 0x02 max_request_id = 100
- 0x04 max_auth_token_cache_size = 1024
- 0x07 moqt_implementation = Meta MoQ C++ Draft-14
draft 14 · QUIC
- 0x02 max_request_id = 100
- 0x04 max_auth_token_cache_size = 1024
- 0x07 not defined by this draft = Meta MoQ C++ Draft-14 (moqt_implementation in 15–22)
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 | drafts 14, 16, 18, 22 | 22 QUIC: 7 of 718 QUIC: 7 of 716 QUIC: 6 of 614 QUIC: 6 of 6 | Object delivered end to end22 QUIC | relay offered nothing | 2026-12-24 | duplicate_track_alias 22 QUIC | no defects |
| 27 Oct 2026 | 0.5.0 74c287bac814 | yes | drafts 14, 16, 18, 22 | 22 QUIC: 7 of 718 QUIC: 7 of 716 QUIC: 6 of 614 QUIC: 6 of 6 | Object delivered end to end22 QUIC | — | 2026-12-24 | — | — |
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.