Drata: Brief SafeBase App Request Failures
Drata reported critical SafeBase request failures: some requests errored or timed out because edge traffic filtering rules blocked legitimate traffic. Recorded start and resolution were both 2026-08-21 01:00 UTC (computed duration: 0 min), although the vendor described approximately six minutes of failures on August 20.
Machine-written from the archived incident (Sol). Check the timeline before relying on it.
Timeline of updates
- resolved
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.
Rewindex changes for this incident
- Critical incident: Brief SafeBase App Request Failures 2026-08-21 01:00 UTC
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Drata profile · Recent Drata incidents · Markdown · JSON