- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- us
What to do
Check whether you use Drata in us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1d 9h it lasted.
Anything that failed between 2026-10-08 13:40 UTC and 2026-10-09 23:30 UTC may need a replay.Subscribe to Drata's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=drata works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Drata 3
- investigating
We are currently investigating this issue.
provider
- investigating
We have identified an issue delaying today’s scheduled compliance checks and ticket synchronization for some customers in our US region. Expiration checks, compliance and vendor review reminders, and linked ticket status updates may be delayed. Our team is working on a fix. The Drata web application and API remain available, and no data loss has been reported. We will share updates as recovery progresses.
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-5168fbd45f
Is Drata still down?
No, this incident was resolved 2026-10-09 23:30 UTC. For Drata's live state, see https://down.guide/drata.
How long did it last?
1d 9h, from 2026-10-08 13:40 UTC to 2026-10-09 23:30 UTC, by the times Drata posted.
What was affected?
Drata named in us.
What caused it?
Drata hasn't published a root cause. If it does, it shows here.
Where does this come from?
Drata's official status page, https://status.drata.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.