Home/Status
Status
Static page, updated with each release. For a check a machine
should make, request /health.txt instead — it is three bytes and
is never cached.
| Origin | Serving |
|---|---|
| Asset set | Release 2026-08-12, 4 sources |
| HLS ladders | 3 of 4 sources |
| Checksums | Published |
| IPv6 | Not published — IPv4 only for now |
Known limitations
There is one origin. It is a static file server behind a cache, which keeps it cheap and dull, but it also means there is no failover: a maintenance window is a maintenance window.
Assets are immutable within a release, not across releases. Pin to a release if a byte-exact comparison matters — see the changelog for what moved and when.
No IPv6 address is published yet. Clients on IPv6-only networks will need NAT64 or a dual-stack resolver.
Reporting a problem
Before reporting: check /health.txt to separate an outage from
a content problem, and verify the file you received against
SHA256SUMS to separate a transfer problem from
a packaging one. Those two checks resolve most of what gets reported.