Update - 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.
Jun 08, 2026 - 15:40 PDT
Investigating - We are currently investigating this issue.
Jun 08, 2026 - 15:38 PDT
US
Operational
90 days ago
99.98
% uptime
Today
API US
Operational
90 days ago
100.0
% uptime
Today
Agent API US
Operational
90 days ago
100.0
% uptime
Today
Public API US
Operational
90 days ago
99.92
% uptime
Today
Auditor API US
Operational
90 days ago
100.0
% uptime
Today
Incoming Webhooks US
Operational
90 days ago
100.0
% uptime
Today
EU
Operational
90 days ago
100.0
% uptime
Today
API EU
Operational
90 days ago
100.0
% uptime
Today
Agent API EU
Operational
90 days ago
100.0
% uptime
Today
Public API EU
Operational
90 days ago
100.0
% uptime
Today
Auditor API EU
Operational
90 days ago
100.0
% uptime
Today
Incoming Webhooks EU
Operational
90 days ago
100.0
% uptime
Today
APAC
Operational
90 days ago
100.0
% uptime
Today
API APAC
Operational
90 days ago
100.0
% uptime
Today
AGENT API APAC
Operational
90 days ago
100.0
% uptime
Today
Public API APAC
Operational
90 days ago
100.0
% uptime
Today
Auditor API APAC
Operational
90 days ago
100.0
% uptime
Today
Incoming Webhooks APAC
Operational
90 days ago
100.0
% uptime
Today
Web Application
Operational
90 days ago
100.0
% uptime
Today
Trust Center Pages
Operational
90 days ago
100.0
% uptime
Today
Trust Center Admin Page
Degraded Performance
90 days ago
100.0
% uptime
Today
AIQA
Operational
90 days ago
100.0
% uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Related
No incidents or maintenance related to this downtime.
Some customers may be experiencing gaps in automated monitoring for resources in the AWS me-central-1 (UAE) and me-south-1 (Bahrain) regions.
Due to ongoing service disruptions in these regions, we have temporarily disabled Drata's automated monitoring (data syncs and tests) for both regions. This change prevents test errors and instability for customers with infrastructure there. We are unsure when the situation will resolve but will continue to monitor for new changes. Posted on
May 18, 2026 - 01:13 PDT
Resolved -
This incident has been resolved.
Jun 4, 10:29 PDT
Monitoring -
A fix has been implemented and we are monitoring the results.
Jun 4, 09:29 PDT
Identified -
The issue has been identified and a fix is being implemented.
Jun 4, 09:29 PDT
Update -
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.
Jun 4, 09:29 PDT
Update -
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.
Jun 4, 09:24 PDT
Investigating -
We are currently investigating this issue.
Jun 4, 09:22 PDT
Completed -
The scheduled maintenance has been completed.
Jun 1, 15:00 PDT
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 1, 13:00 PDT
Scheduled -
On Monday, June 1st from 22:00 – 00:00 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.
May 29, 00:28 PDT
Completed -
The scheduled maintenance has been completed.
Jun 1, 07:00 PDT
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 1, 05:00 PDT
Scheduled -
On Monday, June 1st from 10:00 PM – 12:00 AM AEST, all APAC 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.
May 29, 00:55 PDT
Completed -
The scheduled maintenance has been completed.
Jun 1, 02:00 PDT
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 1, 00:00 PDT
Scheduled -
On Monday, June 1st from 12:00 AM – 2:00 AM PDT, all US 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.
May 29, 00:26 PDT
Resolved -
This incident has been resolved.
May 29, 07:27 PDT
Update -
Fix is being tested.
May 22, 10:11 PDT
Update -
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.
May 22, 09:58 PDT
Investigating -
We are currently investigating this issue.
May 22, 09:56 PDT
Update -
The incident is resolved
May 25, 07:22 PDT
Resolved -
This incident has been resolved.
May 25, 07:22 PDT
Monitoring -
A fix for the issue has been deployed. Policy Approvals are now fully operational
May 22, 16:55 PDT
Update -
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.
May 22, 07:50 PDT
Identified -
The issue has been identified and a fix is being implemented.
May 22, 07:49 PDT