- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 33of 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 21h 41m it lasted.
Anything that failed between 2026-09-24 18:56 UTC and 2026-09-25 16: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.
Root cause
We have identified the root cause of the cron service degradation and are working to deploy fix.
Category: Deploy or config change
Read the postmortemUpdates from Drata 7
- investigating
We are currently investigating this issue.
provider
- investigating
We have identified an issue in one of our cron services. We are actively working on a fix.
provider
- investigating
Engineering Team is actively investigating this issue.
provider
- investigating
We have identified the root cause of the cron service degradation and are working to deploy fix. The cron service that was impacted automatically runs background tasks that keep compliance data fresh. It flags expired reports, updates approval statuses when deadlines hit, applies new policies, and recalculates control readiness.
provider
- investigating
Fix has been deployed. We will be monitoring the next cron run to ensure incident has been fully resolved. The next cron run is scheduled for 11:00 UTC
provider
- monitoring
A fix has been implemented and we are monitoring the results.
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-1e796810cd
Is Drata still down?
No, this incident was resolved 2026-09-25 16:37 UTC. For Drata's live state, see https://down.guide/drata.
How long did it last?
21h 41m, from 2026-09-24 18:56 UTC to 2026-09-25 16:37 UTC, by the times Drata posted.
What caused it?
Deploy or config change. Drata wrote: "We have identified the root cause of the cron service degradation and are working to deploy fix." The postmortem: https://stspg.io/6bv6bkkkwrvs
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.