Snyk reported this major-impact incident on its official status page on Oct 23, 2026, 14:10 UTC. It was resolved after 2d 19h.
Right now Snyk is operational. Live Snyk status →
Services have remained stable throughout the weekend, and we do not expect any further impact. The Snyk Incident Response has been stood down.
Snyk engineers have mitigated the underlying cause of the Snyk Test failures. Tests are now succeeding within normal durations across the environment. Snyk Engineers will continue monitoring system stability.
We have identified that the failures are linked to elevated load on a backend data service in our <a href="https://app.snyk.io/">SNYK-US-01</a> environment. This is causing Snyk Test and other dependency and container scan operations to fail, time out or return errors. Following further investigation, we have confirmed that Snyk Code and Snyk IaC are not affected. The impact is limited to Snyk Open Source and Snyk Container. Our engineers are applying mitigations to restore normal service. We will keep you updated with our progress.
Snyk engineers are observing a degradation affecting Snyk Test in the SNYK-US-01 multi-tenant environment. Customers may observe timeouts and errors with Snyk Test. Our engineers are aware, and the incident response has been enacted.
Overlapping incidents aren't necessarily related.
Snyk reported 23 incidents in the last 90 days, 4 of them major or critical. A typical incident lasted 17h 45m. See Snyk's uptime and incident history