Vanta had 59 outages in the last 2 years totaling 1534h 19m of downtime — averaging 2.4 incidents per month.
There were 59 Vanta outages since August 21, 2025 totaling 1534h 19m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
A fix for the MCP server functionality has been deployed and validated.
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.
This incident has been resolved, and MSP users should now be able to successfully access MSP customer domains again.
Integrations are failing to load on the Integrations page. We have identified the cause and are working on deploying a fix.
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 deployed.
This incident has been resolved.
Outage in 3rd-Party Integration Confluence for syncing Policies and Documents. Atlassian is aware and actively working on mitigating the issue.
This incident has been resolved, and policy and document syncing should be functioning as expected.
Bad configuration change during attempt to fix web-background worker queue delay caused an elevated number of 500 errors.
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 actively working to resolve the issue. We have also engaged our database provider's support team for additional assistance. We will provide another update within 30 minutes. We apologize for the disruption.
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.
Error rates have returned to normal levels and US region users should see normal operations. We are continuing to monitor closely to confirm stability.
This incident has been resolved.
We are currently investigating elevated error rates affecting our EU region. US and AUS regions are not affected.
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.
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.
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 errors or degraded performance. Our team is actively working to expedite recovery. All other regions remain unaffected.
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.
All systems are fully functional and this incident has been resolved.
We have identified an issue with connecting new private and partner integrations. We've identified the issue and are working on a mitigation.
We've applied a fix and confirmed services are working as expected again.
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 working on mitigation.
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.
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.
The underlying GitHub incidents have been resolved, and remediation steps on Vanta's end are complete.
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 are failing. Our engineering team is actively investigating, and we will provide another update as soon as we have more information.
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, customers who previously hit this error will need to retry connecting their Bitbucket integration. We will post another update once the fix is fully rolled out.
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.
We are currently investigating an issue where automated emails are not being sent for evidence requests and request reminders.
As a workaround, customers can manually send evidence requests in the app which will trigger the notifications.
The issue has been identified and a fix is being implemented.
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
This incident has been resolved, and [problem] should be functioning as expected.
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.
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.
This incident was fully resolved on April 24th and no further issues have been observed.
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.
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.
This incident has been resolved, and updating Gitlab Vulnerabilities should be functioning as expected.
Some customers may experience degraded policy approval submissions. Our team has identified the root cause and has a fix in flight.
This incident has been resolved, and submitting policies for approval should be functioning as expected.
The issue has been identified and our Engineering team is actively working on a resolution.
This incident has been resolved, and Trust Center for Trust Collaborators should be functioning as expected.
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 between the policy evidence and its associated control (and therefore the audit workflow) was disrupted, causing the evidence to not surface in audit views as expected. Our team is actively working to restore the affected mappings and fully recover the audit evidence.
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.
This incident has been resolved and data has been restored for impacted customers across all regions.
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
This incident has been resolved.
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 resolved.
This incident has been resolved.
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.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
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.
The issue has been remediated and new Rippling fetches have been observed to be successful. We are continuing to monitor the fix for now.
This incident has been resolved.
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.
This issue is fully resolved now - customers that were affected should have tests passing as expected now and previous failures are invalidated.
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 updates here
We've identified the issue and are working on the fix.
This incident has been resolved, and Document imports from Confluence, Google Drive and Share Point should be functioning as expected.
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.
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.
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 closely monitoring their progress while service is restored. We'll provide additional updates as more information becomes available.
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.
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 investigating the root cause and will provide an update as soon as possible.
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.
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.
We are continuing to monitor for any further issues.
This incident has been resolved.
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 login failures. Our engineering team is actively testing a fix. As a workaround, customers can continue using QAuto through alternative browsers such as Microsoft Edge or Brave. We will share additional updates as they become available.
This incident has been resolved.