Snyk Incident History

Our investigations remain ongoing. However, we have validated that this only impacts PR Checks for Azure repos for Snyk Code and Open Source within our app.snyk.io environment.We will keep you updated on the progress of our investigation.

Our Engineers are aware of an issue affecting our PR Checks for Snyk Code and Open Source.Initial impact assessment is ongoing, however, so far we believe the issue only impacts a small subset of customers within our app.snyk.io environment.Affected customers may be observing their PR Checks within Snyk Code and Open Source getting stuck in 'waiting' status.The Snyk Incident Response has been invoked, and initial investigations are ongoing.

Our Engineers are aware of an issue affecting our PR Checks for Snyk Code and Open Source.Initial impact assessment is ongoing, however, so far we believe the issue only impacts a small subset of customers within our app.snyk.io environment.Affected customers may be observing their PR Checks within Snyk Code and Open Source getting stuck in 'waiting' status.The Snyk Incident Response has been invoked, and initial investigations are ongoing.

Our Engineers identified an issue with our Google SCC integration.Some customers may observe that a small percentage of their projects did not correctly sync from Snyk to SCC, causing stale Findings.Our Engineers have initiated a rollback to a previous version to mitigate the issue. However, data will not refresh until there is an issue update within the project.

Our Engineers identified an issue affecting our Google SCC, Amazon EventBridge and AWS Security Hub integrations.Some customers may observe that a small percentage of their projects did not correctly sync, causing stale Findings.Our Engineers have initiated a rollback to a previous version to mitigate the issue. However, data will not refresh until there is an issue update within the project.

Snyk Engineers have identified an issue affecting IaC+ scan results in the SNYK-US-01 (app.snyk.io) environment. The Snyk Incident response has been enacted. Customers will observe a delay with the IaC+ scans displayed in the UI. Our Engineers are aware of the issue and are working to mitigate the delays.

Our Engineers have identified that Snyk Code PR checks within the app.snyk.io environment are degraded.Customers using the above environment may observe that Code PR checks are taking longer than normal to complete or fail.The Snyk Incident Response has been invoked, and investigations are underway.

Snyk engineering has detected that some Group Level integration profiles- which are used for batch processes to update the Essentials Inventory- are degraded.New connections cannot be created, and existing connections are shown as failing. Existing inventory assets are unaffected, but updates to asset inventory are delayed.Organisation level SCM integrations (used for import, retest) are unaffected.Snyk Engineering are investigating.

Service to the Snyk support portal (support.snyk.io) is currently degraded.Customers will not be able to log in to the support portal, view or create cases, use the community discussion, or search knowledge articles.Customers can create a case by sending an email to support@snyk.io; however, Snyk Support is currently unable to reply to cases.The service is supported by a third-party vendor, and we are diligently working with them to resolve the issue and restore service.We will provide an update on this page once the issue is resolved or if there is a material development.

Snyk is aware of an issue that impacted customers using the custom branches feature where a subset of projects created using the CLI across the Open Source and Snyk Code products have been duplicated. The issue caused project duplication, and occurred between 28/03/2025 at 11:00 UTC and 31/03/2025 at 06:30 UTC. Duplication is no longer happening, and Snyk is working to de-duplicate the affected projects.

Our Engineers have identified that recurring tests within our app.au.snyk.io environment are degraded.Customers within the above environment may observe that scheduled tests are completing at a slower rate than expected.The Snyk Incident Response has been invoked, and we are investigating.

The fix has been deployed, and our Engineers have observed no further issues.The Snyk Incident Response has now been stood down.

A fix has been identified; however, to prevent any further potential risk to services over the weekend, this will be deployed on Monday, March 24th.We will keep you updated with our progress.

Synk Engineers have identified an issue affecting Snyk-US-02, Snyk-EU-01, and Snyk-AU-01. No impact has been observed, and there is a low expectation that this will occur. However, the potential impact occurs when new code vulnerabilities are introduced after March 19th; customers utilizing the Snyk code report (CLI Upload) may observe that previously found issues will be given new identities. As a consequence, these issues will not be ignorable. Snyk engineers are working towards mitigation.

The fix has been deployed, and our Engineers have observed no further issues.The Snyk Incident Response has now been stood down.

A fix has been identified; however, to prevent any further potential risk to services over the weekend, this will be deployed on Monday, March 24th.We recognise the impact this is having and appreciate your patience while we work to resolve it.We will keep you updated with our progress.

Our engineers have pinpointed the cause of the problem and are actively working on a solution.The fix is complex, therefore, it may take a few days for this to reach the production environment.We will keep you updated on our progress.

Snyk Engineers are preparing the fix. However, no timeline is available at this time. Once available, the fix will be deployed. Additional details to follow.

Our Engineers have identified the root cause and are taking steps to mitigate the issue.

Snyk Engineers are investigating an issue affecting Jira ticket creation using the Jira Integration via the Snyk UI. Customers may observe "Could not get fields" error message when attempting to create Jira tickets via the UI.

No further issues have been observed during the monitoring phase, and our Engineers are confident the issue is now resolved.The Snyk Incident Response has been stood down.

A fix has been deployed, and we are now monitoring to ensure its success.

Our Engineers have identified that Snyk PR checks are degraded.Customers may experience PR Check delays when using Snyk Code.The Snyk Incident Response has been invoked, and we are investigating.

No further issues have been observed during our monitoring phase.The Snyk Incident Response has now been stood down.

Our Engineers have deployed a fix and are now monitoring to ensure this has been successful.

Our Engineers have identified that AppRisk integrations are currently degraded.Customers may observe that integrations within AppRisk have not run as scheduled and that profiles may show up as 'Failed'.The Snyk Incident Response has been invoked, and we are investigating.

Our Engineers are confident the incident is now resolved.The Snyk Incident Response has been stood down.

Our Engineers have deployed a fix and are monitoring the situation to ensure its success.

Our Engineers have identified an issue impacting Snyk Learn.Customers may notice that they are unable to log in to Snyk Learn.The Snyk Incident Response has been invoked, and we are investigating.