Paramount stitcher
34-72-6-160.sslip.io:443
Paramount's MoQ SSAI sandbox, running a stock moq-dev relay on a bare GCP address.
What this is
- Operated by
- Paramount
- Running
- moq.dev
- Published URL
- https://34-72-6-160.sslip.io:443
- Published as speaking
- draft-18, draft-19, draft-20, draft-21, draft-22 what its operator says, not what was measured
- TestLab id
- stitcher-paramount
What TestLab measured
What this endpoint answered on 2026-11-05. One sweep, on one occasion — not a claim about availability, and not a grade.
- Transports answered
- QUIC and WebTransport
- Drafts answered
- drafts 14–22
- Identifies itself as
- moq-lite-rs
- Media delivery
- Not attempted
- Violations recorded
- 1
- Address families
- IPv4
One reply left the specification
- A request must not use a Request ID at or above the maximum the receiver granted. 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.
Paramount’s MoQ server-side ad insertion sandbox, listed in the MoQ interop runner. It runs a stock moq.dev relay, so Paramount operates code another project wrote: a result here describes this deployment and its configuration before it describes moq.dev.
The address is a bare Google Cloud IP wrapped in sslip.io, which the operator calls a sandbox.
Elsewhere running moq.dev
One other endpoint runs the same implementation. Each is a separate deployment at its own version and configuration, so what one answers is not a claim about the others. All of them are run by the same operator as this one.
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.