Snyk Open Source and Container Degradation

What to do

• Check whether you use Snyk Snyk Container, Snyk Open Source. 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 21h 5m it lasted.

  Anything that failed between 2026-10-08 10:03 UTC and 2026-10-09 07:08 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 3

1. investigatingOct 8, 2026, 10:03 AM UTC

   Our engineers are investigating degraded performance affecting Snyk Open Source and Snyk Container for customers within our app.au.snyk.io environment. Customers may experience longer response times when importing projects, running tests, and monitoring projects through both SCM integrations and the Snyk CLI. Retrying the operation may succeed. The Snyk Incident Response has been invoked. We will keep you updated with our progress.

   provider

2. monitoringOct 8, 2026, 11:24 AM UTC

   Our engineers have applied a fix, and services have recovered across our app.au.snyk.io environment. If any project imports, tests or monitor runs failed or were blocked earlier, they should now complete as normal when re-run. We are continuing to monitor performance closely and will post here if anything changes.

   provider

3. resolvedOct 9, 2026, 7:08 AM UTC

   Services have remained stable throughout our monitoring period, and 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.