Snyk CLI Scans Degraded
No further impact has been observed during our monitoring period. The Snyk Incident Response has been stood down.
The latest update from Snyk.
State
Resolved
Started
35 d ago
2026-09-28 07:51 UTC
Lasted
4 h 24 min
until 2026-09-28 12:15 UTC
Worst impact
Degraded
Timeline
4 updatesInvestigating
3 h 25 min 77%
Monitoring
1 h 23%
Updates
Times in UTCAs posted by Snyk
No further impact has been observed during our monitoring period. The Snyk Incident Response has been stood down.
We've deployed a fix and are now monitoring closely to confirm full resolution.
We've identified an increase in impact. Some Secrets PR checks are still showing as failed, despite the underlying scan completing successfully. We're continuing to investigate and will share more as soon as we have it.
Our Engineers are investigating degradation affecting Snyk Open Source, across our app.snyk.io environment. Customers may see CLI errors on Secrets and dependency graph scans. The Snyk Incident Response has been invoked.
Affected components
4Snyk in the last 90 days
Full historyIncidents in 90 days
27
Days with an incident
41
Median duration
7 h 1 min
This incident
37% shorter than the median
Other Snyk incidents
All incidentsSnyk·BitBucket Cloud Integrations Degraded
Bitbucket Cloud integrations are working as expected across all Snyk environments, and no further impact has been observed throughout our monitoring period. The Snyk Incident Response has been stood down.
Snyk·Snyk Test Down in SNYK-US-01
Services have remained stable throughout the weekend, and we do not expect any further impact. The Snyk Incident Response has been stood down.
Snyk·Snyk Support portal degradation
There have been no further interruptions to our service, declaring the incident as resolved.
Snyk·Snyk Container Degradation in SNYK-US-01
Services have recovered, and Snyk Container is operating normally in SNYK-US-01 . Services have remained stable throughout our monitoring period. The Snyk Incident Response has been stood down.
Snyk·PR Check Invalid Credential Error
Post-mitigation monitoring confirms that all Snyk services are operating normally and remain stable. The incident response team has stood down, and this incident is now resolved.
Follow Snyk
Your coding agent knows when Snyk is down, and tells you when a failure is theirs, not yours. You can also get Snyk incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "snyk" and tell me if Snyk has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=snyk/feed subscribe https://outages.cc/feed.xml?providers=snykFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane