Minor impactResolvedDevOps

Snyk incident: Snyk CLI Scans Degraded

Snyk reported this minor-impact incident on its official status page on Sep 28, 2026, 14:26 UTC. It was resolved after 2d 22h.

Right now Snyk is operational. Live Snyk status →

🔔 Get alerted when Snyk has issuesFree · email alerts · no credit card
Sep 28, 2026, 14:26 UTC
started
Oct 1, 2026, 12:33 UTC
resolved
2d 22h
duration
Minor
impact

Affected components

  • Snyk Open Source
  • Snyk Secrets
  1. resolvedOct 1, 2026, 12:33 UTC

    No further impact has been observed during our monitoring period. The Snyk Incident Response has been stood down.

  2. monitoringSep 29, 2026, 12:53 UTC

    During monitoring, we observed a brief recurrence of impact. This has now been resolved, and we're continuing to monitor closely.

  3. monitoringSep 28, 2026, 14:26 UTC

    Our Engineers observed a recurrence of the impact reported in our earlier <a href="https://status.snyk.io/incidents/0mzlplq9xgvn">incident</a>. We've deployed a further fix and are monitoring closely to confirm stability before considering this resolved.

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 Sep 28, 2026: Snyk CLI Scans Degraded · APIStatus.watch