Drata: Some Automatic Compliance tests are delayed

What to do

Check whether you use Drata API US in us. 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 2h 8m it lasted.
Anything that failed between 2026-04-23 16:34 UTC and 2026-04-23 18:42 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.

investigatingApr 23, 2026, 4:34 PM UTC
Our team is currently investigating an issue causing some Automatic Compliance test results to be globally delayed. During this time, you may see workflows remain in the “testing” state longer than expected while we work on a fix. At this point, we do not anticipate any data loss, as workflows are being safely queued in our backend system.
provider
monitoringApr 23, 2026, 5:36 PM UTC
A fix for the issue with Automatic Compliance tests results has been deployed. The queue is re-processing. We are actively monitoring the remediation status.
provider
resolvedApr 23, 2026, 6:42 PM UTC
The incident has been resolved. The queue is back to normal and processing all tasks on time.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Drata still down?

No, this incident was resolved 2026-04-23 18:42 UTC. For Drata's live state, see https://down.guide/drata.

How long did it last?

2h 8m, from 2026-04-23 16:34 UTC to 2026-04-23 18:42 UTC, by the times Drata posted.

What was affected?

Drata named API US in us.

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.