Snyk

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 are investigating the degradation affecting Recurring Tests across the app.snyk.io environment. Some customers may notice that the Recurring Tests that were scheduled to run on the 29th of January may be delayed. The Snyk Incident Response has been invoked. We will keep you updated on our progress.

Some customers in the MT-US-1 region are reporting issues when importing new projects. This affects all integrations. When the project import completes, the Import Logs page may show the error "Project could not be created", even though projects were in fact created. Customers using the set-and-forget beta feature that experience this issue will find that projects that are marked as "Project could not be created" will be deactivated when Snyk receives a push event from the source code management system. Engineers are investigating.

We're currently investigating service degradation affecting Snyk Code, within our app.snyk.io environment. Customers may observe intermittent failures affecting the test service. This will impact actions such as PR Checks and CLI tests, among others. The Snyk Incident Response has been invoked.

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.

We are currently investigating degradation affecting BitBucket Server Brokered integrations. This degradation specifically affects Universal Broker versions 4.218.0 through 5.4.8. Customers may experience failures across the PR Experience, including PR Checks, fixed PRs, and inline comments. The Snyk Incident Response has been invoked, and investigations are underway.

Our Engineers are investigating the degradation affecting the Snyk CLI. Some customers may receive the error: packageURL validation failed with go.mod replace directive (SNYK-CLI-0000) when initiating CLI Tests for their GO Projects. This affects Snyk CLI version 1.1302.0. As a workaround, we recommend rolling back to a previous version of the CLI. The Snyk Incident Response has been invoked, and our investigations are underway.

Our Engineers have discovered an issue impacting our container scans for images that contain JAR files. The Snyk Incident Response has been invoked. We will keep you updated on our progress.

Our Engineers are investigating the degradation affecting our Daily Recurring Tests, across the app.snyk.io environment. Some customers may notice that the Daily Recurring Tests that were scheduled to run on the 14th of January may be delayed. This may also affect Daily Recurring Tests scheduled for today (15th January). The Snyk Incident Response has been invoked. We will keep you updated on our progress.

Our Engineers are aware of an outage affecting Snyk Code services between 12:46 UTC - 12:54 UTC, across our app.snyk.io environment. Services have now recovered. Customers may have observed that Snyk Code scans, imports, and PR checks failed during this outage window. The Snyk Incident Response has been invoked, and our investigations are underway.