Service status
All systems operational.
Checked , live when you loaded this page.
| Component | Status |
|---|---|
| Website and API | Operational |
| Stored results and reports | Operational |
| Scanning | Operational |
Machine-readable: /status.json — for your own monitoring. It returns 200 whatever the state, because it reports status rather than being a health check.
Incident history
No incidents in the last 90 days.
How this history is made
Entries are written automatically from the same checks shown above. There is no way for us to add, edit or remove one — a history somebody curates is a history that can quietly leave out a bad week, which is the week you came here to find out about.
It can only record what those checks can see, and outages shorter than two minutes are left out: a page full of one-minute entries is one people learn to ignore. Anything happening right now is shown however brief.
Get told when this changes
One message when something breaks, one when it is fixed, and nothing in between — updates every ten minutes are how people learn to filter them. No account needed: whoever most needs to know may be the one who cannot sign in to find out.
Every message carries a one-click unsubscribe link.