- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 23of 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 16h 44m it lasted.
Anything that failed between 2025-12-09 05:52 UTC and 2025-12-09 22:37 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
Some customers may see outdated information displayed in the risk management module. Our team is actively working to resolve the issue as quickly as possible.
provider
- monitoring
A fix for the issue where Risk Management was displaying outdated data has been deployed. Team is monitoring to make sure that the issue has been resolved.
provider
- resolved
The incident is 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-6d57475801
Is Drata still down?
No, this incident was resolved 2025-12-09 22:37 UTC. For Drata's live state, see https://down.guide/drata.
How long did it last?
16h 44m, from 2025-12-09 05:52 UTC to 2025-12-09 22:37 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.