Snyk Code (SAST) Scan service degraded

What to do

• Check whether you use Snyk Snyk Code. 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 2h it lasted.

  Anything that failed between 2026-06-19 20:13 UTC and 2026-06-19 22:13 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 2

1. investigatingJun 19, 2026, 8:13 PM UTC

   We are currently experiencing an unexpected issue affecting our SAST scans and certain API triggered tests. Our engineering team is actively monitoring the situation to fully understand the impact and isolate the root cause. While we work to restore full functionality, some users may experience intermittent or immediate failures in their running scans and automated test suites. We will provide updates as they become available.

   provider

2. resolvedJun 19, 2026, 10:13 PM UTC

   The issue affecting SAST scans and API-driven automated tests has been successfully resolved, and all services have returned to normal status. Our engineering team identified the root cause as an expensive SQL query that triggered database degradation. The query has been mitigated, and performance has stabilized. Thank you for your patience while we worked through this.

   provider

Corrections

None so far.

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