Drata Outage History

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.

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.

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

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.

We are currently investigating this issue.

We are currently investigating this issue.

We are currently investigating this issue.

We're seeing an increase in Public API request failures in the US region. Requests may succeed when retried. We're actively investigating and will provide updates when they become available.

We're investigating failures affecting the Public API in the US region. Framework and control readiness may not calculate correctly during this time. Public API endpoints retrieving framework data may fail or present incorrect data currently. No data has been lost — readiness data is intact and will display accurately once resolved. EU and APAC are unaffected currently.

A fix for the issue framework readiness data was not loading correctly for some accounts. team has already deployed an initial fix to production and is deploying a second update today to fully resolve the issue. We are actively deploying the fix to all regions.

We are currently investigating this issue.

We've identified an issue where some users may not receive the in-app notification when certain reports or exports finish generation. We have found no evidence that the underlying files fail to generate or are lost - the notification delivery is what's affected. We are actively working on the fix. We'll post the update on the progress.

We're still validating the fix and will provide an update once it's deployed.

We are currently investigating this issue.

We're investigating an issue affecting the Salesforce integration for a subset of customers. Salesforce data lookups are intermittently failing due to an authentication issue with our integration provider. SafeBase itself remains fully operational, and no customer data is affected. We are engaged with our provider on a resolution.

We are currently investigating this issue.

We are seeing an elevated number of errors on AIQA related to degraded performance of an upstream provider. The impact is isolated to AIQA. We are monitoring closely and will provide updates as they become available.

Upstream provider has stablized, and reported the issue has been resolved. The degredaded performance has been eliminated for the last 30 minutes, and is expected to be resolved.

We are currently investigating this issue.

We've identified an issue impacting some customers in which some users who have service user and auditor accounts are unable to access their own tenant. We are actively working on a fix.

Fix is being tested.

Public API in the US region is currently unavailable. We're investigating and will provide updates as they become available.

We are investigating an issue where real-time in-app notifications and status updates are not being delivered to some users. Features that rely on live updates may appear to be stuck loading or may not reflect the latest status without a manual page refresh. Affected functionality may include: - AI workflow progress and completion notifications - Approval workflow status updates - Policy suggestion progress - Monitor test results - Vendor assessment updates - Bulk operation completion alerts - General in-app notifications Workaround: Manually refreshing the page or logging out and back in will restore real-time updates temporarily. Our engineering team has identified the likely cause and is actively working on a fix. We will provide updates as the investigation progresses.

Our team is currently investigating an issue where completed Security Reviews are not being reflected in Training Records. We will provide updates as they become available.

Our team is currently investigating an issue causing some Automatic Compliance test results to be globally delayed. During this time, you may see workflows remain in the “testing” state longer than expected while we work on a fix. At this point, we do not anticipate any data loss, as workflows are being safely queued in our backend system.

We are investigating an increase in magic link timeouts on Drata api. We have identified the issue and the fix is in progress.

We've identified an issue preventing users with the Restricted Control Manager and Restricted Risk Manager roles from logging in. Our team is currently investigating and will provide updates as more information becomes available.

We've identified the root cause of the login issue affecting Restricted Control Manager and Restricted Risk Manager roles and are actively working to mitigate. We'll provide another update once full access has been restored.

US: On Monday, March 30th from 12:00 AM - 2:00 AM PDT all US Drata customers will be included in a scheduled maintenance window. APAC: On Monday, March 30th from 10:00 PM - 12:00 AM AEST all APAC Drata customers will be included in a scheduled maintenance window. EU: On Tuesday, March 31st from 10:00 PM - 12:00 AM CEST all EU Drata customers will be included in a scheduled maintenance window. During this time, you may experience brief disruptions in service, as processes may need to reconnect. We assure you that we will strive to minimize any inconvenience. We appreciate your understanding and support as we continue to improve our services. If you have any concerns or questions, please do not hesitate to contact us.