Snyk Outage History

Started Feb 11, 2026, 02:18 PM UTC· resolved Feb 20, 2026, 05:39 PM UTC

1. investigating Feb 11, 2026, 02:18 PM UTC

   Our Engineers are investigating the degradation which is affecting our Recurring Tests within the app.snyk.io environment. Customers may observe that their daily Recurring Tests from the 10th of February are delayed. The Snyk Incident Response has been invoked, and our investigations are progressing.

2. investigating Feb 12, 2026, 08:44 AM UTC

   Our investigations into the root cause of the degradation remain ongoing. Customers may continue to observe delays with daily Recurring Tests that were scheduled to run on the 10th of February.

3. investigating Feb 13, 2026, 08:51 AM UTC

   Customers may continue to observe delays affecting some daily tests from the 10th and 12th of February. We are working to ensure these tests are completed as part of today's scheduled run. We will keep you updated with our progress.

4. investigating Feb 16, 2026, 09:19 AM UTC

   Our engineers are actively working on mitigation activities. However, some customers may still experience delays with daily Recurring Tests. We will continue to provide updates on our progress.

5. investigating Feb 17, 2026, 02:13 PM UTC

   Some customers may still experience delays with daily Recurring Tests that were scheduled to run on the 16th of February. However, we expect any delayed/missed tests from the 16th (February) to be completed during today's run. We have implemented measures to mitigate the delays and will monitor today's run to ensure this has been successful. Further updates to follow.

6. monitoring Feb 18, 2026, 03:10 PM UTC

   We're no longer observing delays affecting our daily Recurring Tests. However, we will continue to monitor throughout tomorrows scheduled run to ensure there are no further delays experienced.

7. monitoring Feb 20, 2026, 09:03 AM UTC

   We are continuing our monitoring phase to ensure there are no further delays to our Recurring Tests.

8. resolved Feb 20, 2026, 05:39 PM UTC

   Snyk engineers have been monitoring the environment and are no longer seeing delays affecting our daily recurring tests. The Snyk incident response has been stood down.

Read the full incident report →

Started Jan 29, 2026, 06:44 AM UTC· resolved Jan 29, 2026, 09:36 AM UTC

1. investigating Jan 29, 2026, 06:44 AM UTC

   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.

2. investigating Jan 29, 2026, 08:40 AM UTC

   Our investigations into the root cause are continuing. We will keep you updated as we progress.

3. resolved Jan 29, 2026, 09:36 AM UTC

   Our Engineers have implemented a fix and are confident this incident is now resolved. The Snyk Incident Response has now been stood down.

Read the full incident report →

Started Jan 28, 2026, 10:48 AM UTC· resolved Jan 28, 2026, 11:54 AM UTC

1. identified Jan 28, 2026, 10:48 AM UTC

   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.

2. monitoring Jan 28, 2026, 11:25 AM UTC

   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.

3. resolved Jan 28, 2026, 11:54 AM UTC

   We have observed no further issues during our monitoring period. The Snyk Incident Response has now been stood down.

Read the full incident report →

Started Jan 22, 2026, 02:31 PM UTC· resolved Jan 22, 2026, 03:24 PM UTC

1. identified Jan 22, 2026, 02:31 PM UTC

   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.

2. monitoring Jan 22, 2026, 03:04 PM UTC

   We are starting to see improvement in our service. We will continue to monitor operations until GitHub confirm full restoration.

3. resolved Jan 22, 2026, 03:24 PM UTC

   GitHub have confirmed service restoration, and all Snyk services have recovered. The Snyk incident Response has been stood down.

Read the full incident report →

Started Jan 21, 2026, 01:48 PM UTC· resolved Jan 23, 2026, 08:02 AM UTC

1. investigating Jan 21, 2026, 01:48 PM UTC

   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.

2. monitoring Jan 21, 2026, 03:13 PM UTC

   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.

3. resolved Jan 23, 2026, 08:02 AM UTC

   All affected customers should upgrade to Universal Broker version 5.4.9 to restore service. The Snyk Incident Response has now been stood down.

Read the full incident report →

Started Jan 21, 2026, 08:21 AM UTC· resolved Jan 23, 2026, 09:08 AM UTC

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 →

Started Jan 16, 2026, 02:00 PM UTC· resolved Jan 19, 2026, 09:10 AM UTC

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 →

Started Jan 07, 2026, 01:37 PM UTC· resolved Jan 07, 2026, 02:27 PM UTC

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 →

Started Dec 29, 2025, 10:00 AM UTC· resolved Dec 29, 2025, 11:00 AM UTC

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 →

Started Dec 27, 2025, 09:06 AM UTC· resolved Dec 28, 2025, 07:48 AM UTC

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 →

Started Dec 24, 2025, 11:40 AM UTC· resolved Dec 25, 2025, 02:23 AM UTC

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 →

Started Dec 23, 2025, 03:27 PM UTC· resolved Dec 23, 2025, 04:48 PM UTC

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 →

Started Dec 18, 2025, 07:11 AM UTC· resolved Jan 06, 2026, 07:14 AM UTC

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 →

Started Dec 15, 2025, 03:43 PM UTC· resolved Dec 18, 2025, 01:54 PM UTC

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 →