Monitoring - A fix has been deployed, and error rates are normalising.

We are monitoring to ensure service stability.

Jan 16, 2026 - 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, 2026 - 14:00 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 17, 2026

No incidents reported today.

Jan 16, 2026
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
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.

Jan 7, 2026
Resolved - 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.

Jan 7, 14:27 UTC
Monitoring - 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.

Jan 7, 13:47 UTC
Investigating - 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.

Jan 7, 13:37 UTC
Jan 6, 2026
Resolved - This incident has now been resolved.

The Snyk Incident Response has now been stood down.

Jan 6, 07:14 UTC
Monitoring - 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.

Dec 18, 22:38 UTC
Identified - Our Engineers have identified the root cause and are now working on a solution.

We'll keep you updated with our progress.

Dec 18, 15:44 UTC
Investigating - 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

Dec 18, 07:11 UTC
Jan 5, 2026

No incidents reported.

Jan 4, 2026

No incidents reported.

Jan 3, 2026

No incidents reported.