Status
System status
Current status
Incident history
No incidents to report.
How this page works
The grid above is automatic: every load of this page asks the console for a fresh read of GET /api/status, which actually checks each component — a real database query, a real request to the gateway, a live call to the AI provider and to the email provider — rather than a status someone typed in. Results are cached for a few minutes so a burst of visitors doesn’t cause a burst of checks; the “checked” timestamp above is how old the current read is.
Incident history below it is still written by hand — a check can say a component is down, it can’t write the honest paragraph explaining what happened and what was done about it. Incidents that meet the bar defined in the incident response plan get a direct email to affected customers, in addition to an entry here once it’s safe to describe what happened.
Something look wrong that isn’t reflected here? contact@getdast.tech — the live grid updates itself, but incident write-ups are still manual, so a direct report is the fastest way to get one added.