- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 22of 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 7h 2m it lasted.
Anything that failed between 2026-03-31 16:30 UTC and 2026-03-31 23:32 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've identified an issue preventing users with the Restricted Control Manager and Restricted Risk Manager roles from logging in. Our team is currently investigating and will provide updates as more information becomes available.
provider
- investigating
We've identified the root cause of the login issue affecting Restricted Control Manager and Restricted Risk Manager roles and are actively working to mitigate. We'll provide another update once full access has been restored.
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-2af8f49cd0
Is Drata still down?
No, this incident was resolved 2026-03-31 23:32 UTC. For Drata's live state, see https://down.guide/drata.
How long did it last?
7h 2m, from 2026-03-31 16:30 UTC to 2026-03-31 23:32 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.