Sign in
All relays

Red5 MoQ relay

Red5

moq-relay.red5.net:4433/moq

Sweep of 2026-11-04 01:25 UTC Latest report JSON

Identifies itself as
did not say
Measured
2026-11-04 01:34 UTC
Measured from
Helsinki, Finland
Probe
moqtap-probe 0.7.0 (0da3083d8bde)
Drafts negotiated
drafts 14–22
Drafts the operator lists
draft 22
QUIC WT IPv4

A deployment of Red5 Pro, operated by Red5. About this endpoint

At a glance

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 75 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.

  • SUBSCRIBE · drafts 16–18, 21–22 · QUIC REQUEST_ERROR 16 “Track not found”.
  • SUBSCRIBE · drafts 19–20 · WT REQUEST_ERROR 16 “Track not found”.
  • SUBSCRIBE · draft 14 · QUIC SUBSCRIBE_ERROR 404 “Track not found”.
  • FETCH · drafts 16, 18, 21–22 · QUIC REQUEST_ERROR 16 “Track not found”.
  • FETCH · draft 19 · WT REQUEST_ERROR 16 “Track not found”.
  • FETCH · draft 14 · QUIC Refused. The stream ended with no reset.
  • TRACK_STATUS · drafts 16–18, 21–22 · QUIC REQUEST_ERROR 16 “Track does not exist”.
  • TRACK_STATUS · drafts 19–20 · WT REQUEST_ERROR 16 “Track does not exist”.
  • TRACK_STATUS · draft 14 · QUIC Refused. The stream ended with no reset.
  • SUBSCRIBE_NAMESPACE · draft 15 · WT Refused. The stream ended with no reset.
  • SUBSCRIBE_NAMESPACE · draft 14 · QUIC SUBSCRIBE_NAMESPACE_ERROR 3 “No published tracks in namespace”.

Media delivery

One publisher and two subscribers, to see whether an object published through this endpoint reaches a client that asked for it.

Not attempted draft 22 · QUIC

The session this step needed did not open. The session did not open: no answer before the deadline during MoQT setup.

Specification violations

A request must not use a Request ID at or above the maximum the receiver granted. request_id_ceiling

Draft 14 over QUIC, during the control message probe (PUBLISH)

Specification
draft-ietf-moq-transport-14, Section 9.5
“If a Request ID equal to or larger than this is received by the endpoint that sent the MAX_REQUEST_ID in any request message (PUBLISH_NAMESPACE, FETCH, SUBSCRIBE, SUBSCRIBE_NAMESPACE, SUBSCRIBE_UDPATE or TRACK_STATUS), the endpoint MUST close the session with an error of TOO_MANY_REQUESTS.”
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. parameter_out_of_scope

Draft 20 over WebTransport, during the control message probe (PUBLISH)

Specification
draft-ietf-moq-transport-20, Section 10.2.1
“Each Message Parameter definition indicates the message types in which it can appear. If it appears in some other type of message, the receiving endpoint MUST close the connection with a PROTOCOL_VIOLATION.”
Required response
close the session with PROTOCOL_VIOLATION (0x3)

A control message's declared length must match its content. control_message_length

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. duplicate_parameter

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. control_message_length

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

Measured by sweep

SweepProbeReachableDraftsRequests answeredDeliveryOffers a trackCertificate valid untilViolations
4 Nov 20260.7.0 0da3083d8bdeyesdrafts 14–2222 QUIC: 7 of 721 QUIC: 7 of 720 WT: 5 of 619 WT: 7 of 718 QUIC: 7 of 717 QUIC: 2 of 616 QUIC: 5 of 515 WT: 1 of 214 QUIC: 3 of 5Not attempted22 QUICnot attempted2027-01-17control_message_length 14 QUICcontrol_message_length 15 WTduplicate_parameter 15 WTparameter_out_of_scope 20 WTrequest_id_ceiling 14 QUIC
3 Nov 20260.7.0 fcd05c5302c4yesdrafts 14–2222 QUIC: 7 of 721 QUIC: 7 of 720 WT: 5 of 619 WT: 7 of 718 QUIC: 7 of 717 QUIC: 2 of 616 QUIC: 5 of 515 WT: 1 of 214 QUIC: 3 of 5Not attempted22 QUICnot attempted2027-01-17control_message_length 14 QUICcontrol_message_length 15 WTduplicate_parameter 15 WTparameter_out_of_scope 20 WTrequest_id_ceiling 14 QUIC
2 Nov 20260.7.0 fcd05c5302c4yesdrafts 14–2222 QUIC: 7 of 721 QUIC: 7 of 720 WT: 5 of 619 WT: 7 of 718 QUIC: 7 of 717 QUIC: 2 of 616 QUIC: 5 of 515 WT: 1 of 214 QUIC: 3 of 5Not attempted22 QUICnot attempted2027-01-17control_message_length 14 QUICcontrol_message_length 15 WTduplicate_parameter 15 WTparameter_out_of_scope 20 WTrequest_id_ceiling 14 QUIC
1 Nov 20260.7.0 fcd05c5302c4yesdrafts 14–2222 QUIC: 7 of 721 QUIC: 7 of 720 WT: 5 of 619 WT: 7 of 718 QUIC: 7 of 717 QUIC: 2 of 616 QUIC: 5 of 515 WT: 1 of 214 QUIC: 3 of 5Not attempted22 QUICnot attempted2027-01-17control_message_length 14 QUICcontrol_message_length 15 WTduplicate_parameter 15 WTparameter_out_of_scope 20 WTrequest_id_ceiling 14 QUIC
31 Oct 20260.7.0 fcd05c5302c4yesdrafts 14–2222 QUIC: 7 of 721 QUIC: 7 of 720 WT: 5 of 619 WT: 7 of 718 QUIC: 7 of 717 QUIC: 2 of 616 QUIC: 5 of 515 WT: 1 of 214 QUIC: 3 of 5Not attempted22 QUICnot attempted2027-01-17control_message_length 14 QUICcontrol_message_length 15 WTduplicate_parameter 15 WTparameter_out_of_scope 20 WTrequest_id_ceiling 14 QUIC
30 Oct 20260.7.0 fcd05c5302c4yesdrafts 14–2222 QUIC: 7 of 721 QUIC: 7 of 720 WT: 5 of 619 WT: 7 of 718 QUIC: 7 of 717 QUIC: 2 of 616 QUIC: 5 of 515 WT: 1 of 214 QUIC: 3 of 5Not attempted22 QUICnot attempted2027-01-17control_message_length 14 QUICcontrol_message_length 15 WTduplicate_parameter 15 WTparameter_out_of_scope 20 WTrequest_id_ceiling 14 QUIC
29 Oct 20260.7.0 632a80524083yesdrafts 14–2222 QUIC: 7 of 721 QUIC: 7 of 720 WT: 5 of 619 WT: 7 of 718 QUIC: 7 of 717 QUIC: 2 of 616 QUIC: 5 of 515 WT: 1 of 214 QUIC: 3 of 5Not attempted22 QUICnot attempted2027-01-17control_message_length 14 QUICcontrol_message_length 15 WTduplicate_parameter 15 WTparameter_out_of_scope 20 WTrequest_id_ceiling 14 QUIC
27 Oct 20260.5.0 74c287bac814yesdrafts 14–2222 QUIC: 7 of 721 QUIC: 7 of 720 WT: 5 of 619 WT: 7 of 718 QUIC: 7 of 717 QUIC: 2 of 616 QUIC: 5 of 515 WT: 1 of 214 QUIC: 3 of 5Not attempted22 QUIC—2027-01-17control_message_length 14 QUICcontrol_message_length 15 WTduplicate_parameter 15 WTparameter_out_of_scope 20 WTrequest_id_ceiling 14 QUIC

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.