Red5 MoQ relay
moq-relay.red5.net:4433/moq
Red5's public MoQ Transport relay, listed for draft-22 interop.
What this is
What TestLab measured
2026-11-12 01:37 UTC
- Transports answered
- QUIC and WebTransport
- Drafts negotiated
- drafts 14–22
- Identifies itself as
- did not say
- Media delivery
- not attempted: The session this step needed did not open. The session did not open: no answer before the deadline during MoQT setup.
- Certificate valid until
- 2027-01-17
- Address families
- IPv4
- Violations recorded
- 5
5 replies left the specification
-
request_id_ceilingA request must not use a Request ID at or above the maximum the receiver granted. draft 14 over QUIC -
parameter_out_of_scopeA message parameter must only appear in the messages its definition names. draft 20 over WebTransport -
control_message_lengthA control message's declared length must match its content. draft 15 over WebTransport -
duplicate_parameterA parameter type must not appear twice in a message unless its definition allows it. draft 15 over WebTransport -
control_message_lengthA control message's declared length must match its content. draft 14 over QUIC
What each one is, and what the specification requires, is on the report.
Also recorded during the sweep — conditions of the connection rather than findings about the protocol
- — The endpoint is up and refused the offered protocols on at least one transport.
Certificate, per-draft control message support, the delivery run and every recorded violation in full.
Red5’s MoQ relay, listed in the MoQ interop runner over raw QUIC and WebTransport. Red5 has not published the relay’s source.
Is this your endpoint?
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.