Scan and Recurring Test Degradation

What to do

• Check whether you use Snyk Snyk Code, Snyk Open Source in us. 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 14h 58m it lasted.

  Anything that failed between 2026-05-19 17:08 UTC and 2026-05-20 08:06 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. investigatingMay 19, 2026, 5:08 PM UTC

   Snyk engineers are currently tracking Code Scan and Open Source Reachability scan failures—including Recurring Tests—within the Multi-tenant Snyk-US-01 environment. Our incident response team has been activated, and we are actively working to resolve the issue.

   provider

2. investigatingMay 19, 2026, 8:09 PM UTC

   We have successfully mitigated the issue impacting Open Source Reachability Scans and are actively monitoring the environment to ensure continued stability. Meanwhile, our engineering team is continuing to investigate the performance degradation affecting Code Scans. We will provide further updates as they become available.

   provider

3. resolvedMay 20, 2026, 8:06 AM UTC

   We observed no further impact during our monitoring period. The Snyk Incident Response has now 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.