- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 30of 100
What to do
Check whether your product depends on Drata. 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 3h 13m it lasted.
Anything that failed between 2025-10-29 08:33 UTC and 2025-10-29 11:47 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
- identified
We have identified an issue where some customers may see Device category tests remain in the "testing" state after completion. Our engineering team has identified the root cause and is actively working on a fix.
provider
- identified
A fix has been released. Tests with the 'Device' category have been re-enabled and will automatically run with the next cycle of automated compliance tests. For any customers that would like to run the 'Device' category tests now, please use the 'Test now' button.
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-8e2e680589
Is Drata still down?
No, this incident was resolved 2025-10-29 11:47 UTC. For Drata's live state, see https://down.guide/drata.
How long did it last?
3h 13m, from 2025-10-29 08:33 UTC to 2025-10-29 11:47 UTC, by the times Drata posted.
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.