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.
Our Engineers are investigating the degradation affecting Snyk Recurring Tests. Some Customers may notice that their daily recurring tests have not executed as expected. 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.
Our Engineers are investigating the degradation affecting Snyk Recurring Tests. Some Customers may notice that their daily recurring tests have not executed as expected. The Snyk Incident Response has been invoked. We will keep you updated with our progress.
Our engineers are currently investigating a degradation affecting customers who have opted in to Full Source Code Analysis. A small subset of affected customers may observe issues with importing, PR Checks, manual tests, and recurring tests for their Go projects. The Snyk Incident Response has been invoked, and our investigations are underway.
Our Engineers are currently investigating the loss of Reporting (Analytics) across the Snyk Platform. Customers will observe that reporting services are currently unavailable. The Snyk Incident Response has been invoked, and our investigations are underway.
Our Engineers are investigating degradation affecting Snyk Recurring Tests. Some Customers may notice that their daily recurring tests have not executed as expected. The Snyk Incident Response has been invoked, and our investigations have commenced.
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.
Our Engineers have determined a degradation of PR/MR Checks that is causing delays for the processing times. We are currently investigating the cause and will provide updates on scope of impact as our investigation proceeds.
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 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.
* We have detected an issue that is causing a degradation in Open Source scans and projects on app.us.snyk.io * Affected services including Importing, Retests, Loading Projects, Pr Checks * Loading projects may show “Something went wrong” and importing projects may show “project could not be created” Currently other environments appear to be unaffected. We are investigating and will report regularly with updates including any changes in scope.
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.