System status
All systems operational
Last check 25 Oct 2026, 16:16 UTC · every minute · data also as status.json
Components
Website and dashboard
Operational
The site and the dashboard answer through the public address.
90 days agoToday
100% uptime over 90 days
Response time (last 24 h): median 128 ms, p95 199 ms
The API answers, with its database, queue and workers healthy (/health).
90 days agoToday
98.11% uptime over 90 days
Response time (last 24 h): median 92 ms, p95 120 ms
Image rendering
Operational
A signed image URL renders a built-in template in Chrome and the file is served. A fresh render every 10 minutes, cached responses in between.
90 days agoToday
100% uptime over 90 days
Response time (last 24 h): median 181 ms, p95 2,321 ms
Screenshot API
Operational
The Chrome pool that takes website screenshots is up and accepts work.
90 days agoToday
100% uptime over 90 days
Past incidents (90 days)
No incidents in the last 90 days.
How this page works
- Every minute a check requests the public address the way your code does — DNS, TLS, the proxy, the application — and records the result. Nothing on this page is typed in by hand.
- A component becomes an outage after two failed checks in a row and is back to operational at the next check that passes. One dropped packet does not turn the page red, and we are mailed once per incident.
- The rendering check pays from an internal account, never from your quota.
- The checks run on the same server they watch, so they cannot see that server being down completely. That case is watched from outside, and this page then says its data is delayed.