- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 18of 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 1h 36m it lasted.
Anything that failed between 2026-09-19 18:43 UTC and 2026-09-19 20:19 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 4
- investigating
We are currently investigating this issue.
provider
- investigating
We've identified the cause of the issue preventing MSSP / Multi-Instance Management users from loading their client list. A fix is in progress. All other Drata functionality, including core compliance monitoring, is unaffected.
provider
- investigating
This incident is resolved. MSSP / Multi-Instance Management Client services are now operational.
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-eeb0dce7f1
Is Drata still down?
No, this incident was resolved 2026-09-19 20:19 UTC. For Drata's live state, see https://down.guide/drata.
How long did it last?
1h 36m, from 2026-09-19 18:43 UTC to 2026-09-19 20:19 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.