Public MoQ relay endpoints

A URL somebody operates, running somebody's code. Three things that cross, and are worth keeping apart: the endpoint, the operator, and the implementation.

23
endpoints listed
11
operators
8
implementations behind them
20/23
with a TestLab report

How to read this

  • An endpoint is not an implementation. One implementation is many deployments, each at its own version and configuration. A defect measured on one deployment is not a defect in the codebase until someone has checked which of the two it belongs to. The components themselves are in the ecosystem directory .
  • "Not measured" is not a failure. An endpoint with no result is normal. The probe may not have completed a session, the name may not resolve, or the endpoint may not be in the fleet at all — three different situations, none of which is a statement about anybody's relay, and each said explicitly rather than left to an absence.
  • Unknown is a real answer. 2 endpoints below have no published implementation. That is not a row waiting to be filled in — nobody has published what runs there, and the entry says so instead of leaving the field blank.

MOQtail

10 endpoints

moq-rs

4 endpoints

moq.dev

2 endpoints , more than one operator

No published implementation

2 endpoints , more than one operator

Google Quiche

1 endpoint

imquic

1 endpoint

libquicr

1 endpoint

moqx

1 endpoint

Moxygen

1 endpoint

Where the results come from

The measurements above are read from one TestLab sweep, run on 2026-09-14. Each endpoint is contacted directly over both transports and every draft it might speak, and what comes back is recorded as it arrived. Results are point-in-time and describe one run, not a continuous measurement — and no endpoint here is graded.

If an endpoint is missing, or something here is wrong about yours, tell us . We keep what each result rests on, so a disputed one gets re-read rather than re-argued.