Snyk CLI Scans Degraded

What to do

• Check whether you use Snyk Snyk Open Source, Snyk Secrets. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 4h 24m it lasted.

  Anything that failed between 2026-09-28 07:51 UTC and 2026-09-28 12:15 UTC may need a replay.

• Subscribe to Snyk's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=snyk works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Snyk 4

1. investigatingSep 28, 2026, 7:51 AM UTC

   Our Engineers are investigating degradation affecting Snyk Open Source, across our app.snyk.io environment. Customers may see CLI errors on Secrets and dependency graph scans. The Snyk Incident Response has been invoked.

   provider

2. investigatingSep 28, 2026, 8:36 AM UTC

   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.

   provider

3. monitoringSep 28, 2026, 11:15 AM UTC

   We've deployed a fix and are now monitoring closely to confirm full resolution.

   provider

4. resolvedSep 28, 2026, 12:15 PM UTC

   No further impact has been observed during our monitoring period. The Snyk Incident Response has been stood down.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.