Drata experienced a major incident on September 24, 2026, lasting 21h 40m. The incident has been resolved; the full update timeline is below.
Update timeline
- investigating Sep 24, 2026, 06:56 PM UTC
We are currently investigating this issue.
- investigating Sep 24, 2026, 06:57 PM UTC
We have identified an issue in one of our cron services. We are actively working on a fix.
- investigating Sep 24, 2026, 09:56 PM UTC
# Status Update **Incident:** Cron Service Degradation We have identified and fixed the root cause of the cron service failures affecting compliance automation. Our engineering team discovered that the service was loading all users into memory before filtering, causing failures when processing larger datasets. **What's Happening Now:** We have developed a code fix that optimizes this process to retrieve only the necessary filtered data upfront. Testing has validated the solution, and we are deploying this fix to production immediately.
- investigating Sep 24, 2026, 10:18 PM UTC
We have identified the root cause of the cron service degradation and are working to deploy fix. The cron service that was impacted automatically runs background tasks that keep compliance data fresh. It flags expired reports, updates approval statuses when deadlines hit, applies new policies, and recalculates control readiness.
- investigating Sep 24, 2026, 11:10 PM UTC
Fix has been deployed. We will be monitoring the next cron run to ensure incident has been fully resolved. The next cron run is scheduled for 11:00 UTC
- monitoring Sep 24, 2026, 11:11 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 25, 2026, 04:37 PM UTC
The incident is resolved