Service status
What is running, checked from your browser.
The rows below are read from the live service the moment this page opens, not from a page somebody updates by hand when they remember. If the application does not answer, that is what the page will say.
Independently of this page, a watchdog outside the product reaches the site every fifteen minutes and opens an incident the moment a check fails. Incidents are recorded below and stay recorded.
Right now
Each component, as it answers.
Not checked yet. This page needs JavaScript to read the live service; with it off, the incident record below is still current.
Incidents
Recorded since 2026-09-10, and kept.
No incidents recorded since 2026-09-10. The watchdog has run every fifteen minutes throughout; the day it fails a check, the incident appears here.
An incident is opened when the watchdog's check fails or a customer reports a fault, and is closed with what happened and what changed. A record that only listed the outages we chose to mention would not be worth reading.
How this is watched
Three checks, none of them inside the product.
Every fifteen minutes
A watchdog reaches the site the way a customer does — the health endpoint, then the pages people open — and checks the application is serving from the database it should be and that the background worker has written its heartbeat in the last five minutes. A page that answers but takes more than eight seconds counts as a fault.
On every error
Every error the application records is forwarded out of the process the moment it happens, with the request id the browser was given, so a fault is known before it is reported.
Every month
A restore drill dumps the database, restores it into a scratch copy and compares every table's row count, timing the whole thing. The policy's recovery figures come from that measurement and nowhere else.
What to do if something is wrong
Write to support@siaaru.com with the request id from the page that failed — it is in the response headers and on the error screen — and the time. The id ties your browser's failure to the exact server work behind it.