Snyk reported this minor-impact incident on its official status page on Sep 28, 2026, 07:51 UTC. It was resolved after 4h 24m.
Right now Snyk is operational. Live Snyk status →
No further impact has been observed during our monitoring period. The Snyk Incident Response has been stood down.
We've deployed a fix and are now monitoring closely to confirm full resolution.
We've identified an increase in impact. Some Secrets PR checks are still showing as failed, despite the underlying scan completing successfully. We're continuing to investigate and will share more as soon as we have it.
Our Engineers are investigating degradation affecting Snyk Open Source, across our <a href="https://app.snyk.io/">app.snyk.io</a> environment. Customers may see CLI errors on Secrets and dependency graph scans. The Snyk Incident Response has been invoked.
Our 5-minute checks didn't record a change in Snyk's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
Snyk reported 17 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 6h 27m. See Snyk's uptime and incident history