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
Jan 13, 2026

No incidents reported today.

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
Snyk SCM/API Import Degradation
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
PNPM project testing and import degraded for SCM scans in regional environments
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.

Jan 2, 2026

No incidents reported.

Jan 1, 2026

No incidents reported.

Dec 31, 2025

No incidents reported.

Dec 30, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage