Vanta

Affected: 3rd Party Integrations

Names an upstream provider: Cloudflare.

1. identified 2026-10-21 15:40 UTC

   We have identified an issue with the CloudFlare API serving Ruleset data (https://developers.cloudflare.com/api/resources/rulesets/), causing fetches to fail and data to be stale for two Cloudflare entities: CloudflareDomainInventory and CloudflareZoneRule. We are deploying a...

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Vendor Risk Management

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-09-17 19:37 UTC

   We are aware of an issue causing the “Company completes security assessments for relevant vendors” product test to fail incorrectly for some customers and are working to restore accurate test results.

2. monitoring 2026-09-17 21:00 UTC

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

3. monitoring 2026-09-18 05:00 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-09-18 05:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Questionnaire Automation, Vendor Risk Management, Vanta MCP Server, Vanta AI

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-09-14 14:10 UTC

   We are aware of issues with the following AI products: Vendor Risk Management, Questionnaire Automation, Policy Search, and Policy Generation. We understand the root cause and are working to provide a solution.

2. identified 2026-09-14 14:10 UTC

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

3. resolved 2026-09-14 15:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: 3rd Party Integrations

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. identified 2026-09-09 19:56 UTC

   We are aware of an issue causing sync operations to fail for GCP Firebase projects and databases, leading to some stale resource data in the Vanta app. We are working with the GCP team to resolve the issue.

2. identified 2026-09-10 15:12 UTC

   We are continuing to work with the GCP team to resolve the issue causing sync operations to fail for GCP Firebase projects and databases, resulting in stale resource data in the Vanta app.

3. identified 2026-09-10 21:35 UTC

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

4. resolved 2026-09-10 21:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vanta's status page.

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-08-03 18:12 UTC

   We have resolved an issue where customers were unable to programmatically install the Vanta agent using our installation scripts (such as deployments via MDM). This was caused by an unexpected permissions change that made the scripts repository private starting on July 31, 2026,...

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Core App

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-07-07 17:02 UTC

   An incorrect default variant has been set for our HIPAA framework, leading to the addition of new controls which were not previously selected by users. A fix has been implemented and we are monitoring the results.

2. resolved 2026-07-07 20:10 UTC

   Incident has been resolved, default variant set to the correct one for the HIPAA framework.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Vanta AI

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-03 21:09 UTC

   The MCP servers are temporarily unavailable in EU and AUS. Our team is investigating the root cause and will provide an update as soon as possible.

2. resolved 2026-06-04 17:20 UTC

   A fix for the MCP server functionality has been deployed and validated.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Core App

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-27 05:44 UTC

   We have identified an issue with MSP console preventing MSP users from accessing MSP customer domains Our team is investigating the root cause and will provide an update as soon as possible.

2. resolved 2026-05-27 06:58 UTC

   This incident has been resolved, and MSP users should now be able to successfully access MSP customer domains again.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Core App

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-22 17:06 UTC

   Integrations are failing to load on the Integrations page. We have identified the cause and are working on deploying a fix.

2. identified 2026-05-22 17:12 UTC

   We are aware of an issue causing the Integrations page to not display connected integrations. All integrations are functioning normally; this is a display issue only and does not affect any active connections. We have identified the root cause and a fix is currently being...

3. resolved 2026-05-22 17:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: 3rd Party Integrations

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-05-14 05:37 UTC

   Outage in 3rd-Party Integration Confluence for syncing Policies and Documents. Atlassian is aware and actively working on mitigating the issue.

2. resolved 2026-05-14 06:43 UTC

   This incident has been resolved, and policy and document syncing should be functioning as expected.

Excerpts are shortened. Read the full incident on Vanta's status page.

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. resolved 2026-05-13 07:30 UTC

   Bad configuration change during attempt to fix web-background worker queue delay caused an elevated number of 500 errors.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Core App, Access Reviews, Questionnaire Automation, Vanta Public API, Vendor Risk Management, Trust Center, Vanta AI

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-06 22:33 UTC

   We are currently investigating degraded performance affecting multiple areas of the Vanta platform. Some users may be experiencing errors or timeouts when loading pages or making API requests. Our engineering team has identified elevated database load as the likely cause and is...

2. identified 2026-05-07 00:24 UTC

   We have identified the cause of this incident and are actively working to resolve it. US region users may continue to experience errors or inability to access the platform while this work is ongoing. EU and AUS regions remain unaffected.

3. monitoring 2026-05-07 14:05 UTC

   Error rates have returned to normal levels and US region users should see normal operations. We are continuing to monitor closely to confirm stability.

4. resolved 2026-05-07 23:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Core App, Access Reviews, Questionnaire Automation, Vendor Risk Management, Trust Center, Vanta AI

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-01 10:25 UTC

   We are currently investigating elevated error rates affecting our EU region. US and AUS regions are not affected.

2. identified 2026-05-01 11:41 UTC

   We have identified the cause of this incident and are actively working to resolve it. EU region users may continue to experience errors or inability to access the platform while this work is ongoing. US and AUS regions remain unaffected.

3. monitoring 2026-05-01 13:03 UTC

   Error rates have returned to normal levels and EU region users should be able to access the platform. We are continuing to monitor closely to confirm stability.

4. identified 2026-05-01 14:35 UTC

   We are continuing to investigate an issue affecting our EU region. While error rates had returned to normal levels earlier today, we have identified that recovery of our EU infrastructure is taking longer than expected. EU region users may continue to experience intermittent...

5. monitoring 2026-05-01 16:34 UTC

   Error rates have returned to normal levels and EU region users should be able to access the platform. We are continuing to monitor closely to confirm stability.

6. resolved 2026-05-02 12:43 UTC

   All systems are fully functional and this incident has been resolved.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: 3rd Party Integrations

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-04-28 21:57 UTC

   We have identified an issue with connecting new private and partner integrations. We've identified the issue and are working on a mitigation.

2. resolved 2026-04-29 01:01 UTC

   We've applied a fix and confirmed services are working as expected again.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: 3rd Party Integrations

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. identified 2026-04-27 18:56 UTC

   We've identified an issue that may cause GitHub Pull Requests, Issues, and Dependabot vulnerabilities not to appear in Vanta and may affect the status of related tests. The root cause is a downstream GitHub incident (https://www.githubstatus.com/incidents/ql942tw29yl6). We are...

2. identified 2026-04-28 03:27 UTC

   The underlying GitHub incident has been resolved, and GitHub data in Vanta is gradually being restored. We expect the remaining missing data to be restored within the next few hours, and we will finish the remaining remediation actions in the morning.

3. identified 2026-04-28 17:31 UTC

   A follow-up GitHub incident (https://www.githubstatus.com/incidents/x69zbgdyfzg0) is now active, which may be causing missing Pull Request data in Vanta. We're waiting for this to be resolved before completing the final mitigation steps.

4. resolved 2026-05-01 17:42 UTC

   The underlying GitHub incidents have been resolved, and remediation steps on Vanta's end are complete.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Core App

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-22 15:26 UTC

   We are currently investigating an issue preventing customers from connecting the Bitbucket integration. Users attempting to authorize Vanta against Bitbucket are being redirected back with an "unknown error." Existing Bitbucket integrations are unaffected — only new connections...

2. identified 2026-04-22 19:59 UTC

   We have identified the cause of the Bitbucket integration connection failures affecting a some customers. A fix has been developed, tested, and is currently being deployed. Customers with existing Bitbucket connections have not been affected. Once the deployment completes,...

3. resolved 2026-04-22 21:37 UTC

   The fix has been deployed and the Bitbucket integration is connecting normally again. Customers who previously encountered the "unknown error" while trying to connect Bitbucket should now be able to successfully complete the connection flow by retrying.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Core App

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-17 19:53 UTC

   We are currently investigating an issue where automated emails are not being sent for evidence requests and request reminders.

2. investigating 2026-04-17 20:07 UTC

   As a workaround, customers can manually send evidence requests in the app which will trigger the notifications.

3. identified 2026-04-17 23:20 UTC

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

4. monitoring 2026-04-20 23:57 UTC

   We have deployed a fix that resume reminder emails going forward. For assessments that are overdue, we will be sending out email to vendors. In addition, we will be notifying affected users shortly

5. resolved 2026-04-30 06:05 UTC

   This incident has been resolved, and [problem] should be functioning as expected.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: 3rd Party Integrations

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-04-10 23:43 UTC

   We're having some issues with authentication and data synchronization delays for the Linear integration that will continue throughout the weekend. The engineering team is already working on a fix, which is estimated for early next week.

2. monitoring 2026-04-17 20:48 UTC

   A fix will be rolled out over the weekend to fully resolve the Linear integration issues. We will update once it has been rolled out and verified.

3. resolved 2026-04-27 15:08 UTC

   This incident was fully resolved on April 24th and no further issues have been observed.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Core App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-19 18:13 UTC

   We're observing issues when updating Gitlab Vulnerabilities for some domains. Our team is investigating the root cause and will provide an update as soon as possible.

2. identified 2026-03-20 18:14 UTC

   Vanta engineers have identified the issue causing fetches for GitLab vulnerabilities to fail and are working to implement a fix. We are monitoring the behaviour and will continue to provide updates as they become available.

3. resolved 2026-03-31 01:28 UTC

   This incident has been resolved, and updating Gitlab Vulnerabilities should be functioning as expected.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Core App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-03-17 22:43 UTC

   Some customers may experience degraded policy approval submissions. Our team has identified the root cause and has a fix in flight.

2. resolved 2026-03-18 02:07 UTC

   This incident has been resolved, and submitting policies for approval should be functioning as expected.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Trust Center

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-03-16 17:21 UTC

   The issue has been identified and our Engineering team is actively working on a resolution.

2. resolved 2026-03-16 23:08 UTC

   This incident has been resolved, and Trust Center for Trust Collaborators should be functioning as expected.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Core App

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-03-13 00:32 UTC

   We have identified an issue in which some customers may experience policy evidence appearing as missing from associated controls in in-progress or future audits. The underlying policy data has not been deleted and remains accessible within the Vanta product. However, the linkage...

2. identified 2026-03-13 21:28 UTC

   We are continuing to restore data for impacted customers. Full resolution is expected in the next 2-3 hours. We will provide updates as we near full restoration.

3. resolved 2026-03-13 22:50 UTC

   This incident has been resolved and data has been restored for impacted customers across all regions.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Core App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-03-09 20:03 UTC

   Auditors are unable to download the evidence packet for automated tests in audit. We've identified the root cause and are rolling out a fix

2. resolved 2026-03-09 21:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Core App

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-03-09 18:52 UTC

   We've identified an issue where users attempting to edit their Issues in Vanta are being met with an error message. This error message is being shown even when user's changes are being saved successfully. We're working on a fix for this issue and will update here when it's...

2. resolved 2026-03-09 20:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: 3rd Party Integrations

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-25 17:02 UTC

   We have observed an issue with fetches regarding the Rippling integration. This affects fetches for computers and background checks. Our team is actively investigating and will provide updates when possible.

2. investigating 2026-02-25 18:36 UTC

   We are continuing to investigate this issue.

3. investigating 2026-02-26 12:41 UTC

   We are continuing to investigate this issue.

4. investigating 2026-02-27 12:16 UTC

   We are currently investigating with Rippling's engineering team and actively looking into this issue. Customers who have the Rippling integration connected may start observing fetching errors. No customer action is required on the errors at this point in time.

5. monitoring 2026-03-04 14:40 UTC

   The issue has been remediated and new Rippling fetches have been observed to be successful. We are continuing to monitor the fix for now.

6. resolved 2026-03-06 22:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Core App

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-20 19:45 UTC

   Some customers may see security trainings related tests that errantly flipped from pass to fail - we've identified the cause and are mitigating at the moment.

2. resolved 2026-02-20 20:42 UTC

   This issue is fully resolved now - customers that were affected should have tests passing as expected now and previous failures are invalidated.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: 3rd Party Integrations

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-18 20:02 UTC

   We've identified an issue where customers are unable to complete the import documents flow for Confluence, Google Drive and Share Point Integrations. This issue does not cause any data loss and our team is working to resolve this as quickly as possible. We'll provide more...

2. identified 2026-02-18 20:48 UTC

   We've identified the issue and are working on the fix.

3. resolved 2026-02-19 00:40 UTC

   This incident has been resolved, and Document imports from Confluence, Google Drive and Share Point should be functioning as expected.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Core App, Access Reviews, Questionnaire Automation, Vendor Risk Management, Trust Center, Vanta AI

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-02-03 19:09 UTC

   The Vanta web app is temporarily unavailable due to a recent configuration change. The changes are being rolled back and service should be restored soon.

2. resolved 2026-02-03 19:36 UTC

   The Vanta web app was unavailable from 1:51 PM EST to 2:08 PM EST (17 minutes) due to a configuration change related to a third-party vendor outage. This change has been rolled back and the incident is now resolved.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: 3rd Party Integrations

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-02-02 21:33 UTC

   We've identified the cause of an issue impacting Slack and Microsoft Teams notifications, as well as the "Comments & activity" notifications icon for some users. The root cause is an ongoing incident with a third-party vendor. The vendor has begun recovery efforts, and we're...

2. resolved 2026-02-02 23:37 UTC

   The third-party vendor incident that was impacting Slack and Microsoft Teams notifications has been resolved. Notification delivery is now functioning normally, and the "Comments & activity" notifications icon has recovered. We'll continue to monitor to ensure ongoing stability.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Access Reviews

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-01-27 16:45 UTC

   We have identified an issue where the Access tab is missing from the core navigation. In addition, some MSP customers are only seeing the `/integrations` page. We have a fix for the Access tab issue and are still trying to find cause for the MSP Integrations problem Our team is...

2. identified 2026-01-27 16:49 UTC

   Core customers can still access the access page by searching Access - Accounts (https://app.vanta.com/c/{customer}/access/accounts), or if there is a failed test you can click the Access Page hyperlink, and we're working to restore it to nav.

3. monitoring 2026-01-27 23:44 UTC

   Earlier today, a system synchronization mistakenly removed features for a small number of MSP customer accounts. We have restored access to these accounts and are working to resolve the data discrepancy.

4. monitoring 2026-01-28 23:37 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-01-28 23:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: 3rd Party Integrations

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-01-16 18:59 UTC

   Customers using the QAuto browser extension on the latest version of Google Chrome (version 144) may experience issues logging in. We have identified that a recent Chrome update introduced a compatibility issue affecting the extension’s message handling, which can result in...

2. resolved 2026-01-20 15:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Core App

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2026-01-15 15:08 UTC

   We have identified an issue with test logic change for cloudflare-domain-protection-bot-management-enabled, where code was prematurely rolled out, causing some customers to see erroneous failures. Our team is investigating the root cause and will provide an update as soon as...

2. identified 2026-01-15 16:22 UTC

   This issue has has been identified and a fix is being work on.

3. resolved 2026-01-16 14:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Core App

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-15 15:03 UTC

   We have identified an issue impacting the full page view for Risks, causing issues loading the page. In the meantime, we have rolled this back to the legacy Risk view. Our team is investigating the root cause and will provide an update as soon as possible.

2. resolved 2026-01-15 20:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: 3rd Party Integrations

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-22 20:59 UTC

   We have identified an issue where customers using the Sentry integration are seeing unlinking errors and are unable to reconnect the integration. Our team is investigating the root cause and will provide an update as soon as possible.

2. investigating 2025-12-23 01:54 UTC

   Our team understands the root cause of this issue and is working on a fix. Full resolution is expected by mid-day US hours on Tuesday 12/23.

3. identified 2025-12-23 17:54 UTC

   We have deployed a fix for this issue and are rolling it out to all customers over the next 4 hours.

4. monitoring 2025-12-24 01:10 UTC

   The fix has been rolled out to all customers. If a customer has attempted to re-link the Sentry integration and failed during the incident, they may need to re-link again.

5. resolved 2025-12-24 14:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Core App

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-12-15 20:46 UTC

   We have identified an issue where the framework column on the policies table is not displaying correct data. Our team has identified the root cause and a fix is in progress.

2. resolved 2025-12-16 17:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: 3rd Party Integrations

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: OpenAI.

1. investigating 2025-12-02 21:59 UTC

   We have identified an issue causing OpenAI integrations to unlink. Our team is investigating the root cause and will provide an update as soon as possible.

2. investigating 2025-12-02 21:59 UTC

   We are continuing to investigate this issue.

3. resolved 2025-12-04 22:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Core App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-26 14:48 UTC

   We've identified an issue where some users may see errors when loading some of their test detail pages. Our team is currently investigating.

2. monitoring 2025-11-26 15:05 UTC

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

3. resolved 2025-11-26 16:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Core App

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-11-18 12:00 UTC

   An issue with a core networking infrastructure provider is disrupting access to the Vanta web app and all Trust Centers. The provider has confirmed the issue and is investigating, and Vanta engineers are also investigating mitigations.

2. investigating 2025-11-18 14:13 UTC

   An issue with a core networking infrastructure provider is disrupting access to the Vanta web app and all Trust Centers. The provider has confirmed the issue and is investigating, and Vanta engineers are also investigating mitigations.

3. monitoring 2025-11-18 14:49 UTC

   The provider is deploying a fix, and we are seeing some recovery.

4. resolved 2025-11-18 17:39 UTC

   Access to the Vanta web app and Trust Centers has been restored.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Core App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-10 19:40 UTC

   We're currently experiencing a major performance regression resulting in the Vanta application being unable to load. We are actively working to mitigate.

2. investigating 2025-11-10 19:47 UTC

   We're currently investigating the issue, and will provide an update soon.

3. identified 2025-11-10 20:06 UTC

   We’ve identified the root cause and are actively working on mitigations. The Vanta application should now load for users although latencies remain high

4. monitoring 2025-11-10 21:38 UTC

   We’ve finished our mitigation efforts, and latency metrics have returned to normal. We’re continuing to monitor app performance.

5. resolved 2025-11-10 22:38 UTC

   This incident has been resolved and Vanta app should now load for all users.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Core App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-11-05 01:08 UTC

   We have identified an issue causing errors when users attempt to create or edit automated task workflows on tests. Our team is actively working on releasing a fix and will share an update as soon as possible.

2. resolved 2025-11-05 12:41 UTC

   Our team has released a fix and the issue is resolved.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Vanta Device Monitor

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-10-20 21:11 UTC

   We have identified an issue where the Vanta Device Monitor is not installing successfully. Our team is investigating the root cause and will provide an update as soon as possible.

2. resolved 2025-10-20 21:25 UTC

   This incident has been resolved, and installing the Vanta Device Monitor should be functioning as expected.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Core App

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-20 15:25 UTC

   The Vanta web app is failing to load for a large number of users in the US region. The engineering team is investigating.

2. identified 2025-10-20 16:53 UTC

   We are experiencing degradation from the major outage affecting Amazon Web Services (AWS) in the US-East-1 region. Customer domains hosted in the US region remain degraded and are experiencing slowness and errors across the platform. Our team is working closely with AWS and...

3. monitoring 2025-10-20 20:02 UTC

   AWS recovery efforts are still ongoing for the US-East-1 region outage. Our team is still working with AWS and will provide updates as recovery efforts progress. Customers may continue to see periods of elevated latency and occasional errors until services are fully restored.

4. resolved 2025-10-20 22:26 UTC

   The Vanta web app is now stable in all regions.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Access Reviews

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-10-15 22:38 UTC

   We have identified an issue access reviews are having a degraded experience. Editing metadata about an access review in review can cause in-review account snapshots to be dropped, impacting customers who have edited access reviews between October 7th and today. We've shipped a...

2. monitoring 2025-10-15 22:40 UTC

   A fix is being implemented and we are monitoring the results.

3. resolved 2025-10-20 15:15 UTC

   The incident has been resolved. The new access review no longer has this issue, and all affected customers have been contacted to assist with resolution. If you were not contacted, you were not affected.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Core App

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-10 22:00 UTC

   We have identified an issue with the 'MFA required on version control tool' GitLab test flipping to failed state. Our team is investigating the root cause and will provide an update as soon as possible.

2. monitoring 2025-10-14 21:54 UTC

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

3. resolved 2025-10-15 15:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Core App

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2025-10-06 16:19 UTC

   Vanta web users may intermittently receive an error message from Cloudflare or a 'Connecting times out' error. The engineering team is investigating and will share updates once available. In the meantime, refreshing the page should resolve the issue.

2. identified 2025-10-07 13:40 UTC

   The Engineering team has identified the issue and is actively working on releasing a fix.

3. monitoring 2025-10-07 15:16 UTC

   A fix has been implemented, we are currently monitoring the results.

4. resolved 2025-10-07 21:24 UTC

   This incident should now be resolved. Please don't hesitate to reach out to Vanta Support if you continue to run into any issues.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Core App

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-02 14:45 UTC

   We are currently investigating an issue where users clicking links in notifications are sent to homepage rather than redirected to audit or comment. Users are still able to manually navigate to audit or comment.

2. investigating 2025-10-02 14:47 UTC

   We are continuing to investigate this issue.

3. monitoring 2025-10-02 15:14 UTC

   A fix has been implemented and we are monitoring results.

4. resolved 2025-10-02 15:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: 3rd Party Integrations

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-02 14:39 UTC

   Customers are experiencing issues with their Jira integration health causing it to unlink. We are investigating the root cause.

2. identified 2025-10-03 19:06 UTC

   We've identified the issue and our Engineering team is working to resolve

3. resolved 2025-10-07 13:52 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Core App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-30 15:56 UTC

   We have identified an issue where customers are unable to view deactivated tests on the Tests page. Our team is investigating the root cause and will provide an update as soon as possible.

2. monitoring 2025-09-30 16:05 UTC

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

3. resolved 2025-09-30 16:35 UTC

   This incident is resolved.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: 3rd Party Integrations

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-09-26 18:45 UTC

   An issue with connecting Google Workspace has been identified that our engineering team is working to resolve. You may see errors upon trying to connect the integration. We'll continue to keep you updated as we work towards resolving this.

2. monitoring 2025-09-26 20:15 UTC

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

3. resolved 2025-09-29 16:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Core App

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-09-25 13:45 UTC

   We have identified an issue with syncing policies via the Confluence integration. Our team is investigating the root cause and will provide an update as soon as possible.

2. identified 2025-09-25 13:50 UTC

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

3. resolved 2025-09-26 21:23 UTC

   This incident has been resolved. Our team recommends reconnecting the Confluence integration in Vanta to resume policy syncing and documents importing.

Excerpts are shortened. Read the full incident on Vanta's status page.

Affected: Core App

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-09-23 18:58 UTC

   We have identified an issue impacting some customers where a 'Something went wrong' error is received when hovering over the Status badge on the Tests page for a test linked to more than 1 framework. Our team has identified the issue and is working to implement a fix.

2. resolved 2025-09-23 20:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Vanta's status page.