Snyk CLI Degradation
Update - As an immediate workaround, we recommend reverting to a CLI version prior to 1.1302.0.

A hotfix addressing this issue is expected to be released tomorrow, 22nd January.
Jan 21, 2026 - 15:37 UTC
Update - We have identified a solution and are preparing to deploy this as a hotfix. We will update you again once the hotfix has been released.
Jan 21, 2026 - 11:44 UTC
Identified - We have identified the root cause of the error and are now working on a fix.
Jan 21, 2026 - 08:45 UTC
Investigating - 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.
Jan 21, 2026 - 08:21 UTC
Snyk BitBucket Server Broker Integrations Degraded
Monitoring - Following our investigation, we have determined that Universal Broker version 5.4.9 contains a resolution for this issue. We recommend that affected customers upgrade to version 5.4.9 or, preferably, the latest available release to restore full service and maintain ongoing stability.
Jan 21, 2026 - 15:13 UTC
Investigating - 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.
Jan 21, 2026 - 13:48 UTC
SNYK-US-01 (app.snyk.io) Operational
Snyk AppRisk Operational
Snyk Code Operational
Snyk Container Operational
Snyk IaC Operational
Snyk Open Source Operational
Snyk Learn Operational
SNYK-US-02 (app.us.snyk.io) Operational
Snyk AppRisk Operational
Snyk Code Operational
Snyk Container Operational
Snyk IaC Operational
Snyk Open Source Operational
Snyk Learn Operational
SNYK-EU-01 (app.eu.snyk.io) Operational
Snyk AppRisk Operational
Snyk Code Operational
Snyk Container Operational
Snyk IaC Operational
Snyk Open Source Operational
Snyk Learn Operational
SNYK-AU-01 (app.au.snyk.io) Operational
Snyk AppRisk Operational
Snyk Code Operational
Snyk Container Operational
Snyk IaC Operational
Snyk Open Source Operational
Snyk Learn Operational
SNYK-GOV-01 (app.snykgov.io) Operational
Snyk Code Operational
Snyk Container Operational
Snyk IaC Operational
Snyk Open Source Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Jan 22, 2026
Third Party Outage Affecting Snyk Operations
Resolved - GitHub have confirmed service restoration, and all Snyk services have recovered.

The Snyk incident Response has been stood down.
Jan 22, 15:24 UTC
Monitoring - We are starting to see improvement in our service.

We will continue to monitor operations until GitHub confirm full restoration.
Jan 22, 15:04 UTC
Identified - 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.
Jan 22, 14:31 UTC
Jan 21, 2026

Unresolved incidents: Snyk BitBucket Server Broker Integrations Degraded, Snyk CLI Degradation.

Jan 20, 2026

No incidents reported.

Jan 19, 2026
Container scans are degraded for images containing JAR files
Resolved - No further impact has been observed throughout the monitoring period.

The Snyk Incident Response has been stood down.
Jan 19, 09:10 UTC
Monitoring - A fix has been deployed, and error rates are normalising.

We are monitoring to ensure service stability.
Jan 16, 14:57 UTC
Investigating - 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.
Jan 16, 14:00 UTC
Jan 18, 2026

No incidents reported.

Jan 17, 2026

No incidents reported.

Jan 16, 2026
Snyk Recurring Tests Degraded
Resolved - Snyk engineers have been monitoring the environment and confirmed that all systems are operating within normal baselines. The incident response has been stood down.
Jan 16, 21:25 UTC
Update - All Recurring Tests from yesterday are now complete.

We have enabled today's batch; however, some tests may be approximately 1-2 hours behind their normal schedule.

Due to remediation actions taken during this incident, we are observing delays in the propagation of issue data to the Reporting and Rest API after import.

We will continue monitor and provide updates as we progress.
Jan 16, 14:17 UTC
Update - Recurring tests are progressing well, and we are not observing any of the symptoms seen yesterday.

We will continue to monitor progress and keep you updated.
Jan 16, 08:06 UTC
Monitoring - Mitigation efforts have been implemented across all environments. Recurring tests are being rerun in all environments, with SNYK-AU-01 set to resume at 4 AM ACT. Customers may experience delayed results over the next 48 hours. Additionally, there may be a brief fluctuation in risk scores and reachability, which will be addressed in the next test batch. Snyk engineers are closely monitoring all environments.
Jan 15, 19:59 UTC
Update - Snyk engineers are continuing to deploy the mitigation to individual tenants. The mitigation has been applied to the Multi-Tenant US region. Customers may experience delays in recurring tests for the environment over the next 48 hours. Mitigation efforts are ongoing.
Jan 15, 18:53 UTC
Identified - Our engineers have identified a fix, which is currently being deployed.

We will provide a further update once the implementation is complete.
Jan 15, 15:51 UTC
Update - It has been identified that all our environments are affected.
The investigation remains ongoing, and all recurring tests have been suspended pending identification and mitigation of the root cause.
Jan 15, 14:22 UTC
Update - The investigation remains ongoing, and all recurring tests have been suspended pending identification and mitigation of the root cause.
Jan 15, 14:16 UTC
Update - Due to the impact across both app.snyk.io and app.au.snyk.io, customers may notice a temporary fluctuation in risk/priority scores for recurring test results.

Our investigations into the root cause of this incident remain ongoing.
Jan 15, 13:22 UTC
Update - Our investigations are ongoing, and we have identified that customers in our app.au.snyk.io environment are also affected.

Therefore, customers in the specified environment may notice that the Daily Recurring Tests scheduled for execution on the 14th of January may be delayed. We have not cancelled any tests in this environment to date.

We do not expect any other flows across both affected environments to be affected.
Jan 15, 12:23 UTC
Update - To avoid impacting our planned Recurring Tests for today (15th January), we will cancel any Daily Recurring Tests from yesterday's (14th January) schedule that haven't initiated or completed.

We will provide further updates as our investigation progresses.
Jan 15, 10:48 UTC
Investigating - 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.
Jan 15, 09:38 UTC
Jan 15, 2026
Jan 14, 2026

No incidents reported.

Jan 13, 2026
Snyk Code Degradation
Resolved - We have observed no further impact on services during our monitoring period.

The Snyk Incident Response has been stood down.
Jan 13, 14:25 UTC
Monitoring - 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.
Jan 13, 13:07 UTC
Jan 12, 2026

No incidents reported.

Jan 11, 2026

No incidents reported.

Jan 10, 2026

No incidents reported.

Jan 9, 2026

No incidents reported.

Jan 8, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage