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
- TestLab id
- stitcher-paramount
What TestLab measured
What this endpoint answered on 2026-09-14. One sweep, on one occasion — not a claim about availability, and not a grade.
- Transports answered
- QUIC and WebTransport
- Drafts answered
- drafts 14–20
- Identifies itself as
- moq-lite-rs
- Media delivery
- not attempted
- Violations recorded
- 1
- Address families
- IPv4
One reply left the specification
- request-id-ceiling draft 14 over QUIC
What each one is, and what the specification requires, is on the report.
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.
This is the one endpoint in the fleet where the operator and the implementer are different parties. Everywhere else — Cloudflare and moq-rs, MOQtail, Meta and Moxygen, Meetecho and imquic, Cisco and libquicr, OpenMOQ and moqx — the project that wrote the code also runs the box. Here Paramount runs somebody else’s, and the registry says as much: a stock moq.dev relay. So anything measured here is a statement about this deployment before it is a statement about moq.dev, and a defect found on it should not be read as a defect in moq.dev without checking the version and the configuration first.
Its operator calls it a sandbox, and the address is a bare GCP IP wrapped in sslip.io — what you stand up for a temporary box rather than what you put a service behind.
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.