CLI Test and Monitor Degradation

What to do

• Check whether you use Snyk Snyk AppRisk, Snyk Code, Snyk Container, Snyk IaC and 1 more 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 2d 19h it lasted.

  Anything that failed between 2026-04-17 20:21 UTC and 2026-04-20 16:04 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. identifiedApr 17, 2026, 8:21 PM UTC

   We are investigating reports of degraded performance affecting CLI tests within the Snyk-US-01 multi-tenant environment. Our incident response process has been activated, and we have identified specific mitigation steps. We will provide further updates as we work toward a resolution.

   provider

2. monitoringApr 17, 2026, 9:22 PM UTC

   Snyk Engineers have successfully deployed a mitigation. We will continue to monitor the environment throughout the weekend to ensure ongoing stability and performance.

   provider

3. resolvedApr 20, 2026, 4:04 PM UTC

   A fix has been implemented for the Snyk Code Test failures. The service for Code Scans (SAST) has returned to normal operations.

   provider

Corrections

None so far.

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