System status
Checked every five minutes from the machine that runs the components, which is a limit this page states rather than hides. Last check 2026-08-27 00:19 UTC.
Components
| API | operational |
| Extraction worker | operational |
| Database | operational |
Uptime
678 checksThis measures our own health check, not what a browser in your country experienced. The two are not the same thing, and the difference is the next section.
Incidents
| when | what | duration |
|---|---|---|
| 2026-08-26 08:29 UTC | worker:deactivating | 10 min |
| 2026-08-26 00:49 UTC | healthz | 5 min |
| 2026-08-25 08:34 UTC | healthz | 5 min |
| 2026-08-24 16:01 UTC | healthz | 5 min |
| 2026-08-24 15:27 UTC | healthz | 5 min |
| 2026-08-24 14:41 UTC | healthz | 5 min |
| 2026-08-24 08:52 UTC | healthz | 5 min |
What this page cannot tell you
This page is served by the same machine and the same network path it reports on. If the host is down, or your ISP blocks the network we are reachable through, this page is unreachable too and will not be showing you a problem — it will be showing you nothing.
That is not hypothetical here. Spanish ISPs have repeatedly blocked large ranges of a CDN we sit behind during football broadcasts, under court orders aimed at piracy, taking unrelated sites down with them. From inside one of those blocks, Varve and this page are both simply gone, and nothing we host can tell you which it was — which is the honest limit of a status page hosted on the thing it reports on.
A status page hosted off our own infrastructure would fix this properly and is not built yet.