Changes / Drata / Delayed scheduled compliance checks and ticket synchronization in the US region
Drata: Major incident: Delayed scheduled compliance checks and ticket synchronization in the US region
Summary
Drata reported a major degradation delaying scheduled compliance checks and ticket synchronization for some US-region customers, including expiration checks, compliance and vendor review reminders, and linked ticket status updates. It started 2026-10-08 13:40 UTC and was resolved 2026-10-09 23:30 UTC, lasting 33 h 49 min. The web application and API remained available; no data loss was reported.
Machine-written from the diff below (Sol; type: incident degradation). Check the diff before relying on it.
What changed
Before: not present
After: Delayed scheduled compliance checks and ticket synchronization in the US region
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-10-08 13:40 UTC
Before: not present
After: 2026-10-09 23:30 UTC
Before: not present
After: We are currently investigating this issue.
Before: not present
After: We have identified an issue delaying today’s scheduled compliance checks and ticket synchronization for some customers in our US region. Expiration checks, compliance and vendor review reminders, and linked ticket status updates may be delayed. Our team is working on a fix. The Drata web application and API remain available, and no data loss has been reported. We will share updates as recovery progresses.
Before: not present
After: This incident has been resolved.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Delayed scheduled compliance checks and ticket synchronization in the US region (this change) Drata reported a major degradation delaying scheduled compliance checks and ticket synchronization for some US-region customers, including expiration checks, compliance and vendor review reminders, and linked ticket status updates. It started 2026-10-08 13:40 UTC and was resolved 2026-10-09 23:30 UTC, lasting 33 h 49 min. The web application and API remained available; no data loss was reported. | Major incident |