- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- us, us-east-1
- Down Index
- 38of 100
What to do
Check whether you use Drata in us, us-east-1. 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 58m it lasted.
Anything that failed between 2025-10-20 09:02 UTC and 2025-10-20 12:00 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 2
- identified
Our team is currently investigating an issue in which AWS incident in us-east-1 is causing monitors to fail for resources in that region and may cause drata.com to load slowly for some customers. We will provide updates as they become available.
provider
- resolved
Our upstream provider, AWS, has fully mitigated the us-east-1 DNS issue. Monitors for that region are now being processed as expected and drata.com is loading normally. This incident is now 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-5e0e3cd4bd
Is Drata still down?
No, this incident was resolved 2025-10-20 12:00 UTC. For Drata's live state, see https://down.guide/drata.
How long did it last?
2h 58m, from 2025-10-20 09:02 UTC to 2025-10-20 12:00 UTC, by the times Drata posted.
What was affected?
Drata named in us, us-east-1.
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.