Vanta Status

Identified: 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.

Identified: 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.

Identified: 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.

Monitoring: 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

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

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

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

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

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

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

Monitoring: 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.

Identified: 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.

Resolved: 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.

Identified: 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.

Investigating: 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.