Is Drata down?

We are currently investigating this issue.

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.

This incident has been resolved.

We are currently investigating this issue.

We are currently investigating this issue.

We identified an issue where some policy PDFs downloaded from Drata were missing the "Policy version history" page. This page lists versions, dates, owner, approvers, and publisher. It affected some policy versions published between late March and September 21, 2026. The policy content itself is complete and accurate, and no data was lost. Only the version history page was missing from the downloaded PDF. Policies published after September 21 include it correctly. We are working to restore the missing page for the affected policies. If you need a complete copy of a policy for an audit, please contact Support and we'll help. We'll post another update when the work is complete.

We have restored the missing version history page for the large majority of affected policies created in Policy Builder, across all regions. During validation, we found that some restored pages left out earlier draft versions that had been discarded. These are older drafts removed before our approvals feature existed. We have fixed this, and we are now regenerating affected versions

We have restored the missing version history page in policy PDFs for all affected builder policies. The history now matches the version History tab in Drata. What this means for you 1. The policy content was never affected, and no data was lost. 2. Downloaded PDFs for Policy Builder policies now include a complete and accurate version history page. No action is needed on your side. 3. If you downloaded a policy PDF earlier (before today), download it again to get the accurate version history page. 4. Uploaded policies (PDFs you uploaded to Drata) are still being restored. We will post an update here once that is complete.

The missing "Policy version history" page has been restored in policy PDFs, for both policies created in Policy Builder and PDFs uploaded to Drata. We have verified the results across all regions, and this incident is now resolved. What this means for you 1. You don't need to do anything in Drata. 2. If you downloaded or shared an affected policy PDF before today, for example with an auditor, download it again to get the restored page. 3. Your policy content was never affected, and no data was lost. No new policy versions were created, and employees were not asked to accept policies again.

This incident has been resolved.

We are currently investigating this issue.

We have identified an issue in one of our cron services. We are actively working on a fix.

# 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.

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.

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

A fix has been implemented and we are monitoring the results.

The incident is resolved

We are currently investigating this issue.

We've identified the cause of the issue preventing MSSP / Multi-Instance Management users from loading their client list. A fix is in progress. All other Drata functionality, including core compliance monitoring, is unaffected.

This incident is resolved. MSSP / Multi-Instance Management Client services are now operational.

This incident has been resolved.