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.

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.

Engineering Team is actively investigating this issue.

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.

We are actively investigating issues with Trust Center Pages, Trust Center Admin Pages and AIQA.

We continue to investigate connectivity issues to Trust Center Pages, Admin Page and AIQA.

We identified Trust Center Pages, Trust Center Admin Page and AIQA issues to be related to upstream provider network service degradation. We continue to monitor and will update this page as soon as we have more details.

We continue to monitor upstream provided updates. Following products are affected: - Trust Center Pages - Trust Center Admin Page - AIQA - Compliance Monitoring (AI Summary)

We are seeing early signs of recovery and it's confirmed by our upstream provider. We continue to monitor.

This incident is resolved and confirmed by our upstream provider. All impacted services are now operational. What happened: Trust Center Pages, Trust Center Admin Page, AIQA, Compliance Monitoring (AI Summary) were unavailable due to the upstream provider network service degradation.

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 have deployed fixes that significantly reduced errors related to framework readiness processing. A final fix for one remaining affected route is being deployed. We will monitor through the weekend and expect to provide further update ASAP.

The issue has been resolved and all systems are operating normally. We will continue monitoring throughout the weekend to ensure stability. No further action is required from customers at this time.

This incident has been resolved. For approximately six minutes on August 20, a portion of requests to the SafeBase application failed to complete. Requests during this window may have returned errors or timed out. The cause was a change to our edge traffic filtering rules that applied more broadly than intended, which blocked a subset of legitimate traffic from reaching the service. Our automated monitoring detected the failure within two minutes. The change was reverted at 3:40 PM PT, and traffic was fully restored by 3:44 PM PT once the edge cache had cleared. No customer data was affected, and no action is required on your part. We are adding validation to our rule change process so that changes of this type cannot take effect without a scoped review. We’re posting this update after the fact for completeness and transparency. We apologize for the disruption.

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.

The fix has been deployed and validated. We'll continue monitoring it.

This incident has been resolved.

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

We've identified an issue with 'Bulk Actions' button on Personnel page and have temporarily disabled this functionality while we work on a resolution.

We are currently validating the fix for the Bulk Actions issue. Once validation is complete, we will proceed with deployment.

Our team has found an edge case during validation and is working to resolve this issue prior to proceeding with deployment.

The team has identified a fix for the edge case and is continuing to work toward resolving the issue.

We have deployed the fix for the Bulk Action issue. Our team will continue to monitor before marking the issue as resolved.

This incident has been resolved.

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.

This incident has been resolved.

The Salesforce integration is fully restored. Between June 6 and June 8, a subset of customers experienced failures with Salesforce data lookups due to a refresh token expiration issue at our integration provider. We're working with our provider on permanent measures to prevent recurrence and will follow up with any affected customer if further action is needed on their side. We apologize for the disruption and appreciate your patience.

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.

The issue has been identified and a fix is being implemented.

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

This incident has been 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.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

We are aware that some customers may be experiencing issues with policy approvals. Our team is actively working to resolve this as soon as possible.

A fix for the issue has been deployed. Policy Approvals are now fully operational

This incident has been resolved.

The incident is resolved

The issue has been identified and a fix is being implemented.

We’re investigating an issue impacting access to Drata for a subset of customers who are working with managed security service providers (MSSPs). We’ve identified the problem and are actively working on a fix. We’ll continue to share updates as progress is made.

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

This incident has been resolved.

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

Our team has identified the root cause. We're actively working on a fix.

Updates have been deployed. US Public API is available again. We're monitoring to ensure all affected areas are resolved.

After monitoring for an extended time we've confirmed US Public API has been stable since we've introduced the updates earlier. The incident is resolved.

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 engineering team has applied a fix and will continue to monitor for any issues.

This incident has been resolved.

We are monitoring the impact of the Salesforce Authentication Issues we identified earlier today. Customers should see the current status of their Salesforce integration in SafeBase Settings -> Integrations. If any refresh attempts of the connection fail, please reach out to SafeBase Technical Support.

After monitoring, this incident has been resolved. If you experience any further issues with the integration, please reach out to SafeBase Technical Support.

We're aware of an issue with our Salesforce Integration Provider, which could cause your Salesforce connection to show as having an "Authentication issue". This is not affecting all customers. They are investigating and will let us know as soon as we can advise the best course of action. Fully re-authenticating to Salesforce seems to fix the issue but we still working to confirm that.

We are continuing to work on a fix for this issue.

The issue with our Salesforce Integration Partner has been resolved* * According to our Salesforce Integration Partner, some customers may still be experiencing authentication failures. Re-authenticating their Salesforce connection in the SafeBase app will resolve these errors.

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 has mitigated issue where Security Awareness Trainings were not properly reflected within Personnel Records right after completion.

Security Trainings have been properly synced into Drata, and the corresponding compliance checks have been updated accordingly.