Snyk Outage History

Snyk engineers have detected intermittent PR check failures affecting the multi-tenant environment app.us.snyk.io. These failures are due to processing issues with GitHub and GitLab webhooks. The Snyk Incident Response has been enacted. Our engineers are investigating this matter further.

Our Engineers are currently investigating an issue which is affecting Free Users from signing up to the Snyk platform. The Snyk Incident Response has been invoked. We will keep you updated with our progress.

Customers using the Bitbucket Cloud integrations may see degradation in service affecting any use of the Bitbucket Cloud integrations, including: Creating/Editing Bitbucket Integration, Listing repos for import, Import (via UI or API) Tests, Recurring Tests, PR Checks Fix PRs We have identified the cause of the issue and are working towards remediation.

During our monitoring phase, we have become aware that customers using Bitbucket Connect App integrations may be unable to import new repositories. We are investigating this and will keep you updated on our progress.

We have deployed a fix that enables a workaround for project imports using the BitBucket Connect App. As this rolls out, you may experience temporary failures with these imports for up to 30 minutes. If you experience an issue, we recommend waiting a few minutes before trying again.

Our Engineers are aware of the degradation affecting PR Checks. Customers may observe that there are processing delays impacting their PR Checks, resulting in PR Checks getting stuck in a processing state. The Snyk Incident Response has been invoked, and our investigations are underway.

Snyk engineers have identified a service degradation across all cloud Bitbucket integrations, caused by a third-party incident. This issue is affecting all tests and projects on Bitbucket Cloud and Bitbucket Cloud App integrations. We are tracking the third party incident for updates.

Snyk engineers identified service degradation across all GitHub integrations, caused by a third-party incident. The Snyk incident response has been activated, and engineers are actively monitoring the issue.

Snyk engineers are currently investigating performance issues affecting IDE plugins. Customers may encounter scan not triggering when Snyk Code is enabled in their IDE settings. The Snyk team is working on a fix, which is expected to be released on March 4th as part of the regularly scheduled CLI update. As a workaround, customers can downgrade the IDE plugin to a previous version. JetBrains: v2.19.0 VSCode: v2.28.1 Eclipse: v3.7.0 Visual Studio: v2.7.0 https://docs.snyk.io/developer-tools/snyk-ide-plugins-and-extensions/compatibility-matrix After the fix is released, customers need to update the CLI to 1.1303.1 to use the latest IDE plugin versions.

Snyk has identified an issue affecting customers who are using Snyk CLI Version 1.1303.0 with the —report option for static analysis. Affected customers are advised to revert to the previous version of Snyk CLI, 1.1302.1, which is unaffected by this problem. Snyk engineers are currently investigating this issue as part of their Incident Response process.

Snyk engineers have identified a path to resolution and are preparing the fix.

Snyk engineers are preparing the identified fix, which is expected to be deployed tomorrow, March 3rd.

Currently we are experiencing some difficulties with case creation from Email. Please use the support portal support.snyk.io for all case creation Email replies to existing cases do not appear to be impacted, however we recommend using the support portal for vital communications We will advise when the service returns to normal

Our engineers are aware of a degradation that impacted project retesting triggered by code changes in GitLab between 11:20 UTC on 12 February and 11:40 UTC on 13 February. The Snyk Incident Response process has been invoked, and the issue is under active investigation.

Snyk has identified failures related to Snyk Imports and PR checks for PIP, affecting all environments. The Snyk Incident response has been enacted, and Snyk Engineers are taking mitigation actions.

Snyk Engineers continue mitigation efforts. Updates to follow.

Snyk engineers identified service degradation across all GitHub integrations, caused by a third-party incident that began at 16:34 UTC. The Snyk incident response has been activated, and engineers are actively monitoring the issue.

Our Engineers have identified degradation affecting Terraform Cloud Integrations. We have identified the root cause and are now working on a fix. Customers may experience failures affecting their IaC Terraform Cloud Integration. The Snyk Incident Response has been invoked. We will keep you updated with our progress.

Snyk Engineers have confirmed certain operations are failing due to GitHub service degradation. The outage is impacting imports for Snyk Open Source and Snyk Code, including retests, code PR checks, and recurring tests. The Snyk Incident Response has been invoked to monitor the situation. Please continue to monitor this page and GitHub's public status page for further information on this outage.