Skip to main content
Drata

Notification outage

Partial outage Lasted 55m · started · Drata's page

Level
confirmed
Worst impact
Partial outage
Down Index
27of 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 55m it lasted.

    Anything that failed between 2026-02-02 21:10 UTC and 2026-02-02 22:05 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

  1. identified

    We have identified an outage in our 3rd party notification provider that is impacting SafeBase's ability to send emails, Slack, and MS Teams messages. Once the 3rd party provider is back online, all previously unsent messages will be sent.

    provider

  2. identified

    We are continuing to work on a fix for this issue.

    provider

  3. resolved

    Our 3rd party partner has come back online, and notifications are now being sent as usual.

    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-da085e7038

Is Drata still down?

No, this incident was resolved 2026-02-02 22:05 UTC. For Drata's live state, see https://down.guide/drata.

How long did it last?

55m, from 2026-02-02 21:10 UTC to 2026-02-02 22:05 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.