All Systems Operational

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
Feb 2, 2026
Snyk Recurring Tests Degraded
Resolved - Our Engineers have implemented a fix, and are no longer observing delays affecting Recurring Tests.

The Snyk Incident Response has been stood down.
Feb 2, 07:08 UTC
Investigating - 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.
Jan 30, 13:20 UTC
Feb 1, 2026

No incidents reported.

Jan 31, 2026

No incidents reported.

Jan 30, 2026
Jan 29, 2026
Project import on US-01 region intermittently completes with "Project could not be created"
Resolved - Our Engineers have implemented a fix and are confident this incident is now resolved.

The Snyk Incident Response has now been stood down.
Jan 29, 09:36 UTC
Update - Our investigations into the root cause are continuing.

We will keep you updated as we progress.
Jan 29, 08:40 UTC
Investigating - 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.
Jan 29, 06:44 UTC
Jan 28, 2026
Snyk Code Degradation
Resolved - Snyk engineers monitored the environment after the mitigation was deployed and have observed normal operations. The Snyk Incident Response has been stood down.
Jan 28, 19:48 UTC
Monitoring - The mitigation deployment is complete. Snyk Engineers are monitoring the environment.
Jan 28, 18:47 UTC
Identified - Snyk engineers have identified the cause of the issue and have implemented a change to reduce its impact. Because the failures are intermittent, customers may rerun tests as a temporary workaround. We will keep you updated on our progress.
Jan 28, 18:13 UTC
Update - Our investigations remain ongoing.

We will keep you updated with our progress.
Jan 28, 15:05 UTC
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.
Jan 28, 12:32 UTC
Snyk Iac Terraform Cloud Integration Degraded
Resolved - We have observed no further issues during our monitoring period.

The Snyk Incident Response has now been stood down.
Jan 28, 11:54 UTC
Monitoring - We have deployed a fix and are no longer observing issues with Terraform Cloud Integrations.

We will continue to monitor the services to ensure no further issues arise.
Jan 28, 11:25 UTC
Identified - 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.
Jan 28, 10:48 UTC
Jan 27, 2026

No incidents reported.

Jan 26, 2026
Snyk Issues API Degraded
Resolved - Our Engineers are aware of the degradation affecting our Issues API between 11:45 and 12:34 UTC.

Customers may have experienced degradation affecting the Issues API during this window.

Services have now recovered, and we do not expect any further impact.
Jan 26, 13:13 UTC
Jan 25, 2026

No incidents reported.

Jan 24, 2026

No incidents reported.

Jan 23, 2026
Snyk CLI Degradation
Resolved - Affected customers can restore service by upgrading to the latest stable Snyk CLI release: v1.1302.1.

The Snyk Incident Response has now been stood down.
Jan 23, 09:08 UTC
Monitoring - The hotfix has now been released and is included in our latest stable Snyk CLI release: v1.1302.1.

We recommend that affected customers upgrade their CLI to restore impacted services.

We will continue to monitor services to ensure ongoing stability.
Jan 23, 07:22 UTC
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, 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, 11:44 UTC
Identified - We have identified the root cause of the error and are now working on a fix.
Jan 21, 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, 08:21 UTC
Snyk BitBucket Server Broker Integrations Degraded
Resolved - All affected customers should upgrade to Universal Broker version 5.4.9 to restore service.

The Snyk Incident Response has now been stood down.
Jan 23, 08:02 UTC
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, 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, 13:48 UTC
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
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
← Incident History Powered by Atlassian Statuspage