Trust · Incidents
Incident history.
Every customer-impacting outage or security event gets a public entry below — including ones short enough that customers might not notice. Root cause and remediation are added within seven days of the incident closing.
What we publish
Public-incident bar.
-
Customer-impacting downtime
Any period during which the API or dashboard returned errors (technically: non-2xx responses) to real customer requests — including partial problems, e.g. one hosting region (Hetzner) affected, or one of our vendors (a sub-processor) down.
-
Security events
Any unauthorized access, data exposure, or compromise of our encryption or signing keys (a cryptographic integrity event). We post notice within the legally required notification window; full details follow once forensic analysis is complete.
-
Sub-processor incidents
When an upstream sub-processor (Hetzner / Neon / Upstash / Cloudflare / Postmark / Stripe / Sentry) has an incident affecting our customers, we summarise their post-mortem and link the upstream report.
-
Maintenance windows
Pre-announced windows for planned work — database upgrades or restructuring (migrations, schema changes) and security-certificate renewals (certificate rotations). Notice at least 72 hours in advance; customers can subscribe to advance notifications via /settings → email preferences.
History
Posted incidents.
No customer-impacting incidents to date.
This list started before launch, so it can't quietly omit anything — every incident from the first paying customer onward will land here. The live platform status above always reflects the current moment.
Subscribe
Get notified when status changes.
Customers can opt into incident emails at the dashboard's settings page. Future updates: status.driftstack.dev with email + RSS subscription.