Drata change history

Drata reported a major degradation delaying scheduled compliance checks and ticket synchronization for some US-region customers, including expiration checks, compliance and vendor review reminders, and linked ticket status updates. It started 2026-10-08 13:40 UTC and was resolved 2026-10-09 23:30 UTC, lasting 33 h 49 min. The web application and API remained available; no data loss was reported.

Drata reported a major incident: some downloaded policy PDFs lacked the “Policy version history” page; policy content remained complete and no data was lost. It ran from 2026-10-05 19:28 UTC to 2026-10-10 00:01 UTC (4 days 4 h). Drata restored pages across all regions for Policy Builder and uploaded PDFs; customers who downloaded or shared affected PDFs should download again.

Drata reported major cron service degradation affecting background tasks that flag expired reports, update approval statuses, apply policies, and recalculate control readiness, potentially leaving compliance data stale. It started at 2026-09-24 18:56 UTC and was resolved at 2026-09-25 16:37 UTC, lasting 21 h 40 min; a fix was deployed and monitored.

Drata reported a critical outage affecting Trust Center Pages, Trust Center Admin Page, AIQA, and Compliance Monitoring (AI Summary), caused by upstream provider network service degradation. It started at 2026-09-01 15:14 UTC and was resolved at 2026-09-01 19:29 UTC, lasting 4 h 14 min; all impacted services were operational at resolution.

Drata’s major US Public API degradation caused request failures and potentially incorrect framework/control readiness data from 2026-08-26 13:32 UTC to 2026-08-28 23:58 UTC (2 days 10 h). No data was lost; EU and APAC were initially unaffected. Drata deployed fixes and reported normal operation at resolution, with no customer action required.

Drata reported critical SafeBase request failures: some requests errored or timed out because edge traffic filtering rules blocked legitimate traffic. Recorded start and resolution were both 2026-08-21 01:00 UTC (computed duration: 0 min), although the vendor described approximately six minutes of failures on August 20.

Drata reported a major incident affecting in-app completion notifications for some report and export downloads, with no evidence that files failed to generate or were lost. It started 2026-08-11 21:06 UTC and was resolved 2026-08-14 19:44 UTC, lasting 2 days 22 h; a fix was deployed and validated.

Drata temporarily disabled the 'Bulk Actions' button on the Personnel page, preventing customers from using that functionality. The vendor rated the incident major; it began 2026-06-22 18:01 UTC and lasted 4 days 3 h, resolving at 2026-06-26 21:18 UTC. Drata reported an edge case during validation and deployed a fix before resolution.

Drata reported major SafeBase Salesforce integration degradation starting 2026-06-08 22:38 UTC, resolved 2026-06-09 22:07 UTC after 23 h 28 min. Salesforce data lookups intermittently failed for a subset of customers due to refresh token expiration at its integration provider; SafeBase remained operational and no customer data was affected. The integration was fully restored.

Drata reported a major incident isolated to AIQA, with elevated errors attributed to degraded performance of an upstream provider. It ran from 2026-06-04 16:22 UTC to 2026-06-04 17:29 UTC, lasting 1 h 7 min. Drata reported that the provider stabilized and a fix was implemented before marking the incident resolved.

Some Drata users with service user and auditor accounts could not access their own tenant in a major-impact outage. It started at 2026-05-22 16:56 UTC and was resolved at 2026-05-29 14:27 UTC, lasting 6 days 21 h; Drata reported testing a fix but stated no cause.

Drata reported a major tenant access outage affecting a subset of customers working with managed security service providers (MSSPs), starting 2026-05-20 17:56 UTC. A fix was implemented, and the incident was resolved at 2026-05-22 19:07 UTC after 2 days 1 h.

Drata’s US Public API was unavailable in a critical incident starting 2026-05-14 10:54 UTC, resolved at 2026-05-14 13:36 UTC after 2 h 42 min. Drata reported deploying updates that restored availability at 12:35 UTC and confirmed stability after monitoring; it identified but did not disclose the root cause.

Drata reported a major incident where completed Security Awareness Trainings were not properly reflected in Personnel Records, starting 2026-04-28 17:09 UTC and lasting 6 days 2 h. Drata mitigated the issue and resolved it at 2026-05-04 19:19 UTC after syncing trainings and updating corresponding compliance checks.

Drata reported a major incident globally delaying some Automatic Compliance test results, leaving workflows in “testing” longer than expected. It ran from 2026-04-23 16:34 UTC to 2026-04-23 18:42 UTC (2 h 8 min). A fix was deployed and the queue returned to normal; Drata anticipated no data loss because workflows were safely queued.

Drata reported a major Guest Admin Access outage affecting Guest Admins’ ability to view clients within "Business Accounts". It started at 2026-03-16 16:55 UTC and was resolved at 2026-03-16 19:16 UTC, lasting 2 h 20 min. Drata released an update and stated that Guest Admins should now be able to view clients as expected.

Drata reported a critical outage preventing access across all app functionality, starting 2026-02-03 19:06 UTC and resolved 2026-02-04 00:04 UTC (4 h 57 min). Drata attributed elevated error rates to upstream Cloudflare incidents; functionality was briefly reported restored before errors returned.

SafeBase could not send emails, Slack, or MS Teams messages because its third-party notification provider was offline; Drata rated the impact major. The incident started at 2026-02-02 21:10 UTC and was resolved at 2026-02-02 22:05 UTC, lasting 54 min. The provider returned online and normal sending resumed; the vendor said previously unsent messages would be sent.

Drata reported a major degradation in background job processing affecting downloads and policy approvals, starting 2025-12-16 00:24 UTC. The incident lasted 2 h 57 min and was resolved at 2025-12-16 03:22 UTC; Drata reported mitigation at 01:02 UTC and confirmed a fix was deployed at resolution.

SafeBase’s AIQA, Ask AI, and AI Search features were affected by a Google Cloud Vertex AI API outage, rated critical by the vendor. The incident started at 2025-12-11 13:36 UTC and was resolved at 2025-12-11 22:41 UTC, lasting 9 h 4 min. The vendor reported Google’s fix restored its pipelines before monitoring.

Drata reported a critical outage affecting loading of app.drata.com, drata.com and Trust Center pages due to a Cloudflare outage. It started at 2025-12-05 09:11 UTC and lasted 9 min, resolving at 2025-12-05 09:20 UTC after Cloudflare implemented a fix; Drata confirmed all sites were working as expected.

Drata reported a critical EU API incident preventing customers from logging in to the Web Application in the EU region. It started at 2025-12-04 10:36 UTC and was resolved at 2025-12-04 10:50 UTC, lasting 13 min; Drata reported implementing a fix and restoring login access at 10:39 UTC.

A major Web Application outage affected some customers loading app.drata.com, drata.com and Trust Center pages due to a Cloudflare outage. It started at 2025-11-18 14:09 UTC and lasted 1 h 4 min, resolving at 2025-11-18 15:13 UTC after Cloudflare released a fix that restored functionality.

Some Drata customers could not log in to the Web Application during a critical incident that started at 2025-11-04 03:51 UTC and lasted 22 h 55 min, resolving at 2025-11-05 02:46 UTC. Drata identified the root cause without disclosing it and deployed a fix to all regions.

Drata reported a major incident involving intermittent login issues starting at 2025-10-31 03:08 UTC, potentially disrupting customer access. A fix was deployed, and the incident was resolved at 2025-10-31 03:10 UTC after 2 min.

Drata reported a major partial outage affecting AIQA and Trust Library Answering, citing increased error rates from Google's AI infrastructure. The incident started at 2025-10-31 00:18 UTC and was resolved at 2025-10-31 01:05 UTC, lasting 46 min; Drata said it was working with Google, which was investigating.

Drata reported a major incident starting 2025-10-29 08:33 UTC: some customers’ Device category tests remained in “testing” after completion. It lasted 3 h 13 min and was resolved at 2025-10-29 11:47 UTC. A fix re-enabled the tests for the next automated compliance cycle; customers could also run them immediately using “Test now”.

Some Drata users were unable to log in through Okta in a major-impact incident starting 2025-10-21 19:13 UTC. Drata reported deploying a fix and mitigating the issue at that time, then marked it resolved at 2025-10-21 19:17 UTC; the recorded duration was 3 min.

Drata reported a major degradation starting 2025-10-20 09:02 UTC: an AWS us-east-1 issue caused regional monitor failures and possible slow loading of drata.com. Resolved at 2025-10-20 12:00 UTC after 2 h 57 min, AWS’s DNS issue was fully mitigated, monitors processed normally, and drata.com loaded normally.

A critical outage prevented a subset of compliance tests from running for some Drata customers in the US region. It started at 2025-09-26 14:44 UTC and was resolved at 2025-09-26 20:02 UTC, lasting 5 h 17 min. Drata confirmed service was restored and all affected customers’ compliance tests had run to completion.

Drata reported a major incident affecting some customers: multiple policy acknowledgement emails were sent for archived policies, and all emails, including login-related emails, were delayed. It started at 2025-09-18 14:10 UTC and resolved at 2025-09-18 18:00 UTC; the computed duration was 3 h 49 min. A deployed fix resolved the multiple-email issue and login-email delays.

Drata reported a major login outage affecting the Personnel Compliance Managers role, titled “People Ops Role unable to login.” It started at 2025-08-14 19:08 UTC and was resolved at 2025-08-14 19:50 UTC, lasting 42 min; Drata said it was deploying a fix.

Drata reported a major email outage starting 2025-08-14 16:14 UTC, with all emails stuck rather than sending. The incident lasted 19 min and was resolved at 2025-08-14 16:34 UTC; Drata confirmed all emails were being sent as usual.

Drata reported a major AIQA outage starting 2025-07-21 19:41 UTC: an outage at its AI document processing provider caused AIQA runs to fail. It was resolved at 2025-07-21 20:17 UTC after 36 min, and Drata said it implemented a safety measure against similar regressions.