Snyk Outage History

Snyk degraded · 2 active incidents View live status →

Snyk had 60 outages in the last 2 years totaling 683h 45m of downtime — averaging 2.5 incidents per month.

There were 60 Snyk outages since December 8, 2025 totaling 683h 45m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.snyk.io

Minor January 21, 2026

Snyk CLI Degradation

Detected by Pingoru
Jan 21, 2026, 08:21 AM UTC
Resolved
Jan 23, 2026, 09:08 AM UTC
Duration
2d
Affected: Snyk ContainerSnyk ContainerSnyk ContainerSnyk ContainerSnyk ContainerSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open Source
Timeline · 6 updates
  1. investigating Jan 21, 2026, 08:21 AM UTC

    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.

  2. identified Jan 21, 2026, 08:45 AM UTC

    We have identified the root cause of the error and are now working on a fix.

  3. identified Jan 21, 2026, 11:44 AM UTC

    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.

  4. identified Jan 21, 2026, 03:37 PM UTC

    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.

  5. monitoring Jan 23, 2026, 07:22 AM UTC

    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.

  6. resolved Jan 23, 2026, 09:08 AM UTC

    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.

Read the full incident report →

Minor January 16, 2026

Container scans are degraded for images containing JAR files

Detected by Pingoru
Jan 16, 2026, 02:00 PM UTC
Resolved
Jan 19, 2026, 09:10 AM UTC
Duration
2d 19h
Affected: Snyk Container
Timeline · 3 updates
  1. investigating Jan 16, 2026, 02:00 PM UTC

    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.

  2. monitoring Jan 16, 2026, 02:57 PM UTC

    A fix has been deployed, and error rates are normalising. We are monitoring to ensure service stability.

  3. resolved Jan 19, 2026, 09:10 AM UTC

    No further impact has been observed throughout the monitoring period. The Snyk Incident Response has been stood down.

Read the full incident report →

Critical January 7, 2026

Snyk SCM/API Import Degradation

Detected by Pingoru
Jan 07, 2026, 01:37 PM UTC
Resolved
Jan 07, 2026, 02:27 PM UTC
Duration
50m
Affected: Snyk CodeSnyk ContainerSnyk IaCSnyk Open Source
Timeline · 3 updates
  1. investigating Jan 07, 2026, 01:37 PM UTC

    Our Engineers are investigating degradation affecting SCM and API imports across our app.snyk.io environment. Customers are likely to encounter failures when executing SCM or API imports in this environment. CLI tests/monitors are unaffected and should remain operational. The Snyk Incident Response has been invoked. We will keep you updated with our progress.

  2. monitoring Jan 07, 2026, 01:47 PM UTC

    Our Engineers have identified the root cause of the incident and deployed a fix. There is still some lag, which we are working through to ensure all imports are complete. We will continue to monitor services until the lag clears.

  3. resolved Jan 07, 2026, 02:27 PM UTC

    Event queues have normalised, confirming that all pending imports have completed. We are now observing standard processing times. The Snyk Incident Response team has been stood down.

Read the full incident report →

Minor December 29, 2025

Partial Degradation of Reachability Analysis

Detected by Pingoru
Dec 29, 2025, 10:00 AM UTC
Resolved
Dec 29, 2025, 11:00 AM UTC
Duration
1h
Timeline · 1 update
  1. resolved Dec 30, 2025, 12:32 PM UTC

    Between 10:22 and 10:46 UTC on Monday, December 29th, Snyk experienced a partial degradation of backend systems that calculate Reachability for Snyk Code projects. This means a subset of projects tested during this time will be missing the reachability data. This data will be regenerated automatically upon the next retest. All systems have returned to full operation and no further impact was observed. The Snyk incident process has been stood down.

Read the full incident report →

Minor December 27, 2025

Open Source Maven scans degraded

Detected by Pingoru
Dec 27, 2025, 09:06 AM UTC
Resolved
Dec 28, 2025, 07:48 AM UTC
Duration
22h 41m
Affected: Snyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open Source
Timeline · 3 updates
  1. investigating Dec 27, 2025, 09:06 AM UTC

    We have identified an issue impacting Snyk Open Source Maven scans in both SCM and local environments. The Snyk Incident Response has been invoked. We will keep you updated on our progress.

  2. monitoring Dec 27, 2025, 01:07 PM UTC

    A fix has been implemented, and services are now operating normally. We will continue to monitor and provide updates as needed.

  3. resolved Dec 28, 2025, 07:48 AM UTC

    The fix has been successfully implemented, and we are no longer observing any degradation in the Maven scans. Our Incident Response has been stood down.

Read the full incident report →

Minor December 24, 2025

Recurring Tests are Degraded

Detected by Pingoru
Dec 24, 2025, 11:40 AM UTC
Resolved
Dec 25, 2025, 02:23 AM UTC
Duration
14h 42m
Affected: Snyk AppRiskSnyk CodeSnyk ContainerSnyk IaCSnyk Open Source
Timeline · 5 updates
  1. identified Dec 24, 2025, 11:40 AM UTC

    Our Engineers identified that daily and weekly Recurring Tests scheduled to run on the 23rd of December, within the app.snyk.io environment, did not execute as expected. We are now initiating the execution of all Recurring Tests that did not run as scheduled yesterday. The Snyk Incident Response has been invoked. We will keep you updated on our progress.

  2. identified Dec 24, 2025, 11:43 AM UTC

    We have amended the impact statement to reflect that daily Recurring Tests are also affected.

  3. identified Dec 24, 2025, 03:17 PM UTC

    All recurring tests that previously failed to initiate have now been triggered. We expect all tests to be completed by the end of the day on 25th December. We'll provide a further update once all tests have completed.

  4. monitoring Dec 24, 2025, 04:05 PM UTC

    We are now actively monitoring the progress of all recurring tests to ensure successful completion. We'll provide an update once all tests have completed successfully.

  5. resolved Dec 25, 2025, 02:23 AM UTC

    All recurring tests that were missed on December 23 have now completed successfully.

Read the full incident report →

Minor December 23, 2025

GitHub Cloud Integrations Degraded

Detected by Pingoru
Dec 23, 2025, 03:27 PM UTC
Resolved
Dec 23, 2025, 04:48 PM UTC
Duration
1h 21m
Affected: Snyk CodeSnyk CodeSnyk CodeSnyk IaCSnyk IaCSnyk IaCSnyk Open SourceSnyk Open SourceSnyk Open Source
Timeline · 2 updates
  1. investigating Dec 23, 2025, 03:27 PM UTC

    Our Engineering Team is currently investigating a degradation impacting GitHub Cloud Integrations. Customers may experience issues with workflows, including PR Checks, Recurring Tests, Imports, and related functionalities. The Snyk Incident Response has been invoked, and our investigations are underway.

  2. resolved Dec 23, 2025, 04:48 PM UTC

    Our Engineers have observed no further impact, this Incident is now Resolved. The Snyk Incident Response has now been stood down.

Read the full incident report →

Minor December 18, 2025

PNPM project testing and import degraded for SCM scans in regional environments

Detected by Pingoru
Dec 18, 2025, 07:11 AM UTC
Resolved
Jan 06, 2026, 07:14 AM UTC
Duration
19d
Affected: Snyk Open SourceSnyk Open SourceSnyk Open Source
Timeline · 4 updates
  1. investigating Dec 18, 2025, 07:11 AM UTC

    We have detected an issue that is causing SCM scans of PNPM projects to be mis-attributed to NPM or Yarn. This is only occurring in the regional hosted environments (customers that login on sites other than app.snyk.io) Symptoms: * PNPM projects may be detected as NPM projects, or display import errors due to missing yarn.lock files. * Customers using set-and-forget may notice that projects previously detected as PNPM are deactivated and new NPM projects are created. * Customers may notice a change in dependency or vulnerability reports for these projects. This does not affect customers on app.snyk.io This does not affect customers using Snyk CLI to scan pnpm projects, where the PNPM option is enabled in snyk preview. We will update with further information as it becomes available

  2. identified Dec 18, 2025, 03:44 PM UTC

    Our Engineers have identified the root cause and are now working on a solution. We'll keep you updated with our progress.

  3. monitoring Dec 18, 2025, 10:38 PM UTC

    We have applied a fix for this issue, and projects are now testing and importing correctly. * Customers who have been affected are advised to import the affected repos again to ensure that projects are correctly identified, and any projects that were not able to import due to this incident are imported correctly. There is no need to delete existing projects.

  4. resolved Jan 06, 2026, 07:14 AM UTC

    This incident has now been resolved. The Snyk Incident Response has now been stood down.

Read the full incident report →

Minor December 15, 2025

Bitbucket Cloud Degradation

Detected by Pingoru
Dec 15, 2025, 03:43 PM UTC
Resolved
Dec 18, 2025, 01:54 PM UTC
Duration
2d 22h
Affected: Snyk AppRiskSnyk AppRiskSnyk AppRiskSnyk AppRiskSnyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk ContainerSnyk ContainerSnyk ContainerSnyk ContainerSnyk ContainerSnyk IaCSnyk IaCSnyk IaCSnyk IaCSnyk IaCSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open Source
Timeline · 3 updates
  1. investigating Dec 15, 2025, 03:43 PM UTC

    Our Engineers are aware of the degradation affecting Bitbucket Cloud integrations. Some Customers who imported projects via Bitbucket Cloud between the 30th of November and the 11th of December may notice that webhooks haven't been properly installed. The Snyk Incident Response has been invoked, and we are investigating.

  2. investigating Dec 16, 2025, 11:41 AM UTC

    Our investigation into the issue remains ongoing. Customers may have noticed that webhooks were not correctly configured for projects imported from Bitbucket Cloud. This will affect actions such as test-on push, set-and-forget, pull request checks and /snyk fix, among others. As a workaround, customers can initiate a re-import of affected projects, which will install the webhook correctly and resolve the issue. We will keep you updated with our progress.

  3. resolved Dec 18, 2025, 01:54 PM UTC

    We have identified the root cause of the incident and established that this affects only a small subset of customers. We will be reaching out to those customers in due course. However, as a workaround, customers can re-import the affected projects. The Snyk Incident Response has now been stood down.

Read the full incident report →