Brief SafeBase App Request Failures

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 0m it lasted.

  Anything that failed between 2026-08-21 01:00 UTC and 2026-08-21 01: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 1

1. resolvedAug 21, 2026, 1:00 AM UTC

   This incident has been resolved. For approximately six minutes on August 20, a portion of requests to the SafeBase application failed to complete. Requests during this window may have returned errors or timed out. The cause was a change to our edge traffic filtering rules that applied more broadly than intended, which blocked a subset of legitimate traffic from reaching the service. Our automated monitoring detected the failure within two minutes. The change was reverted at 3:40 PM PT, and traffic was fully restored by 3:44 PM PT once the edge cache had cleared. No customer data was affected, and no action is required on your part. We are adding validation to our rule change process so that changes of this type cannot take effect without a scoped review. We’re posting this update after the fact for completeness and transparency. We apologize for the disruption.

   provider

Corrections

None so far.

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