Red5 MoQ relay
Red5moq-relay.red5.net:4433/moq
A deployment of Red5 Pro, operated by Red5. 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
- moqt-22, h3, moqt-21, moqt-18, moqt-17, moqt-16, moq-00
- Media delivery
- not attempted
- Violations recorded
- 5
Certificate
- Subject
- CN=moq-relay.red5.net
- Issuer
- C=US, O=Let's Encrypt, CN=YR1
- Valid until
- 2027-01-17 74 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 |
| 21 QUIC | ✓ err | ✓ err | ✓ err | ✓ ok | ✓ ok | ✓ ok | ✓ ok |
| 20 WT | ✓ err | ✗ | ✓ err | ✓ ok | ✓ ok | ✓ ok | – |
| 19 WT | ✓ err | ✓ err | ✓ err | ✓ ok | ✓ ok | ✓ ok | ✓ ok |
| 18 QUIC | ✓ err | ✓ err | ✓ err | ✓ ok | ✓ ok | ✓ ok | ✓ ok |
| 17 QUIC | ✓ err | ✗ | ✓ err | ✗ | ✗ | · | ✗ |
| 16 QUIC | ✓ err | ✓ err | ✓ err | ✓ ok | ✓ ok | · | – |
| 15 WT | – | – | – | ✗ | ✓ ok | · | – |
| 14 QUIC | ✓ err | ✗ | ✗ | ✓ err | ✓ ok | · | – |
Specification violations
A request must not use a Request ID at or above the maximum the receiver granted.
Draft 14 over QUIC, during the control message probe (PUBLISH)
- Specification
- draft-ietf-moq-transport-14, Section 9.5
- Required response
- close the session with TOO_MANY_REQUESTS (0x7)
- Maximum Request ID granted
- 0
A message parameter must only appear in the messages its definition names.
Draft 20 over WebTransport, during the control message probe (PUBLISH)
- Specification
- draft-ietf-moq-transport-20, Section 10.2.1
- Required response
- close the session with PROTOCOL_VIOLATION (0x3)
A control message's declared length must match its content.
Draft 15 over WebTransport, during the control message probe (SUBSCRIBE)
- Specification
- draft-ietf-moq-transport-15, Section 9
- Required response
- close the session with error code 0x3
A parameter type must not appear twice in a message unless its definition allows it.
Draft 15 over WebTransport, during the control message probe (PUBLISH)
- Specification
- draft-ietf-moq-transport-15, Section 9.2
- Required response
- close the session with error code 0x3
A control message's declared length must match its content.
Draft 14 over QUIC, during version negotiation
- Specification
- draft-ietf-moq-transport-14, Section 9
- Required response
- close the session with error code 0x3
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
No parameters sent.
draft 21 · QUIC
No parameters sent.
draft 20 · WT
No parameters sent.
draft 19 · WT
No parameters sent.
draft 18 · QUIC
No parameters sent.
draft 17 · QUIC
No parameters sent.
draft 16 · QUIC
- 0x02 max_request_id = 100
draft 15 · WT
- 0x02 max_request_id = 100
draft 14 · QUIC
- 0x02 max_request_id = 100
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 → not attempted.
| Sweep | Reachable | Drafts | Delivery | Offers a track | Violations |
|---|---|---|---|---|---|
| 5 Nov 2026 | yes | 14, 15, 16, 17, 18, 19, 20, 21, 22 | Not attempted | not attempted | 4 |
| 4 Nov 2026 | yes | 14, 15, 16, 17, 18, 19, 20, 21, 22 | Not attempted | not attempted | 4 |
| 3 Nov 2026 | yes | 14, 15, 16, 17, 18, 19, 20, 21, 22 | Not attempted | not attempted | 4 |
| 2 Nov 2026 | yes | 14, 15, 16, 17, 18, 19, 20, 21, 22 | Not attempted | not attempted | 4 |
| 1 Nov 2026 | yes | 14, 15, 16, 17, 18, 19, 20, 21, 22 | Not attempted | not attempted | 4 |
| 31 Oct 2026 | yes | 14, 15, 16, 17, 18, 19, 20, 21, 22 | Not attempted | not attempted | 4 |
| 30 Oct 2026 | yes | 14, 15, 16, 17, 18, 19, 20, 21, 22 | Not attempted | not attempted | 4 |
| 29 Oct 2026 | yes | 14, 15, 16, 17, 18, 19, 20, 21, 22 | Not attempted | not attempted | 4 |
| 27 Oct 2026 | yes | 14, 15, 16, 17, 18, 19, 20, 21, 22 | Not attempted | — | 4 |
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.