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. For outages and major incidents, root cause and remediation are added within seven business days of the incident closing.
What we publish
What counts as a public incident.
-
Customer-impacting downtime
Any period during which the API or dashboard returned errors to real customer requests — including partial problems, such as an outage in one Hetzner hosting location, or one of our vendors (a sub-processor) being down.
-
Security events
Any unauthorized access, data exposure, or compromise of our encryption or signing keys. For a personal-data breach, affected customers are told without undue delay after we become aware of it (target: 48 hours, DPA section 6.1); full details follow once our investigation is complete.
-
Sub-processor incidents
When one of our sub-processors (Hetzner / Neon / Cloudflare / MacStadium / Postmark / Stripe / Sentry, and the rest on our list) has an incident affecting our customers, we summarise their post-mortem and link to their report.
-
Maintenance windows
Pre-announced windows for planned work, such as database upgrades or security-certificate renewals. Notice at least 48 hours in advance on the status page.
History
Posted incidents.
Driftstack is in pre-launch. From launch, every incident that affects customers is posted here and on status.driftstack.io.
The live platform status above reflects the current moment.
Subscribe
Get notified when status changes.
Subscribe by email from the status page, or manage account notification preferences from the dashboard.