Minor impactResolvedDevOps

Snyk incident: CLI Test and Monitor Degradation

Snyk reported this minor-impact incident on its official status page on Apr 17, 2026, 20:21 UTC. It was resolved after 2d 19h.

Right now Snyk is operational. Live Snyk status →

🔔 Get alerted when Snyk has issuesFree · email alerts · no credit card
Apr 17, 2026, 20:21 UTC
started
Apr 20, 2026, 16:04 UTC
resolved
2d 19h
duration
Minor
impact

Affected components

  • Snyk AppRisk
  • Snyk Code
  • Snyk Container
  • Snyk IaC
  • Snyk Open Source
  1. resolvedApr 20, 2026, 16:04 UTC

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

  2. monitoringApr 17, 2026, 21:22 UTC

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

  3. identifiedApr 17, 2026, 20:21 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Snyk's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Snyk have incidents?

Snyk reported 17 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 6h 27m. See Snyk's uptime and incident history

Snyk incident on Apr 17, 2026: CLI Test and Monitor Degradation · APIStatus.watch