MOQtail WatchParty
watch-party.moqtail.dev:4446
The WatchParty demo relay on the MOQtail fleet, on a single AWS eu-central-1 instance.
What this is
- Operated by
- MOQtail
- Running
- MOQtail
- Published URL
- https://watch-party.moqtail.dev:4446/
- TestLab id
- moqtail-watchparty
What TestLab measured
2026-11-12 01:37 UTC
- Transports answered
- QUIC and WebTransport
- Drafts negotiated
- draft 16
- Identifies itself as
- moqtail/0.14.1+fbdbc75
- Media delivery
- Namespace accepted, track never asked for
- Certificate valid until
- 2026-12-09
- Address families
- IPv4
- Violations recorded
- none
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.
The relay behind MOQtail’s WatchParty demo, on a single AWS instance in eu-central-1.
Elsewhere running MOQtail
10 other endpoints run the same implementation. All of them are run by the same operator as this one.
MOQtail ABR
MOQtailord.abr.moqtail.dev:443
No connection completed in the last sweep.
Name resolution failed.
MOQtail draft-22
MOQtailrelay.moqtail.dev:8244
- Drafts the operator lists
- draft 22
No connection completed in the last sweep.
QUIC: no answer before the deadline during the QUIC handshake after 8,000 ms.
WebTransport: no answer before the deadline during opening the WebTransport session after 8,000 ms.
MOQtail IBC2025
MOQtailord.ibc25.moqtail.dev:443
- Drafts negotiated
- draft 11
- Identifies itself as
- did not say
- Certificate valid until
- 2026-12-28
Namespace accepted, track never asked for
Two publishers: closed / standby
1 specification violation: request_id_out_of_sequence
MOQtail n1 Chicago
MOQtailrelay.n1.ord.moqtail.dev:443
- Drafts negotiated
- draft 22
- Identifies itself as
- moqtail/0.18.0+c1f88e7
- Certificate valid until
- 2027-02-08
Object delivered end to end
Two publishers: standby / serving publisher on standby
MOQtail n1 Frankfurt
MOQtailrelay.n1.fra.moqtail.dev:443
- Drafts negotiated
- draft 22
- Identifies itself as
- moqtail/0.18.0+c1f88e7
- Certificate valid until
- 2027-02-07
Object delivered end to end
Two publishers: standby / serving no switch-over publisher on standby
MOQtail n1 Osaka
MOQtailrelay.n1.osa.moqtail.dev:443
- Drafts negotiated
- draft 22
- Identifies itself as
- moqtail/0.18.0+c1f88e7
- Certificate valid until
- 2027-02-07
Object delivered end to end
Two publishers: standby / serving no switch-over publisher on standby
MOQtail n1 Singapore
MOQtailrelay.n1.sin.moqtail.dev:443
- Drafts negotiated
- draft 22
- Identifies itself as
- moqtail/0.18.0+c1f88e7
- Certificate valid until
- 2027-02-08
Object delivered end to end
Two publishers: standby / serving no switch-over publisher on standby
MOQtail relay
MOQtailrelay.moqtail.dev:443
- Drafts negotiated
- draft 22
- Identifies itself as
- moqtail/0.18.0+c1f88e7
- Certificate valid until
- 2027-02-07
Object delivered end to end
Two publishers: standby / serving no switch-over publisher on standby
MOQtail SyncPlay
MOQtailsyncplay.moqtail.dev:4448
- Drafts negotiated
- draft 14
- Identifies itself as
- did not say
- Certificate valid until
- 2026-12-09
Namespace accepted, track never asked for
Two publishers: closed / standby
1 specification violation: request_id_ceiling
MOQtail TimeTravel
MOQtailtimetravel.moqtail.dev:4445
- Drafts negotiated
- draft 11
- Identifies itself as
- did not say
- Certificate valid until
- 2026-12-09
Namespace accepted, track never asked for
Two publishers: closed / standby
1 specification violation: request_id_ceiling
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.