Live / Drata / Incident
Drata: Delayed scheduled compliance checks and ticket synchronization in the US region
Drata · drata.comMajor incidentResolved2026-10-09 23:30 UTC
Public — what happened
Summary
Drata reported a major incident beginning at 13:40 UTC on 2026-10-08 in which some US-region customers saw their scheduled compliance checks and ticket syncing held up. According to the company, this could slow expiration checks, reminders for compliance and vendor reviews, and status changes on linked tickets, though its web app and API stayed up and no data was reported lost. Drata said it had found the problem shortly after the incident began but did not describe a cause, and it marked the incident resolved at 23:30 on 2026-10-09.
Timeline
- Started — 2026-10-08 13:40 UTC
- Investigating — 2026-10-08 13:40 UTC (2 updates)
- Resolved — 2026-10-09 23:30 UTC · 33h 50m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Drata against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Drata: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Drata report →
More from Drata
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.