Live / Snyk / Incident
Snyk: Snyk CLI Scans Degraded
Snyk · snyk.ioMinor incidentResolved2026-10-01 12:33 UTC
Public — what happened
Summary
Snyk reported a minor problem affecting scans run through its CLI tool, beginning on 2026-09-28 at 14:26 UTC, which it described as the same trouble seen in an earlier incident coming back. The company said it had rolled out an additional fix and was watching the service, then noted another short return of the issue on 2026-09-29 that it said was addressed. Snyk did not name a cause, and the incident was marked resolved on 2026-10-01 at 12:33.
Timeline
- Started — 2026-09-28 14:26 UTC
- Monitoring — 2026-09-28 14:26 UTC (2 updates)
- Resolved — 2026-10-01 12:33 UTC · 3 days after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Snyk against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Snyk: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Snyk report →
More from Snyk
Covered in The Squid’s Ink, Week 41, 2026, our weekly internet health report.