Snyk experienced a critical incident on January 7, 2026 affecting Snyk Code and Snyk Container and 1 more component, lasting 50m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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.
- 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.
- 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.