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.
The latest update from Snyk.
State
Resolved
Started
10 d ago
2026-10-22 21:53 UTC
Lasted
3 days
until 2026-10-26 07:44 UTC
Worst impact
Partial outage
Timeline
5 updatesIdentified
3 days 98%
Monitoring
1 h 48 min 2%
Updates
Times in UTCAs posted by Snyk
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.
We have had to reverse the mitigation applied earlier to protect other services in the SNYK-US-01 environment. As a result, customers may again experience intermittent errors when importing projects. Retrying the operation may succeed. Our engineers are continuing work to restore full service, and we will keep you updated with our progress.
Our Engineers have taken steps to mitigate the impact, and we are seeing service improve for Snyk Container within our SNYK-US-01 environment. Customers may still experience the occasional error when importing projects. Retrying the operation may succeed. We will continue to monitor throughout the weekend and will post an update on Monday, 26th October.
Our engineers are continuing work to restore full service to Snyk Container within our SNYK-US-01 environment. Customers may continue to experience intermittent errors when importing projects. Retrying the operation may succeed. We will keep you updated with our progress.
Snyk Engineers identified a degradation that affected Snyk Container in SNYK-US-01 Multi-Tenant environment. Customers may experience intermittent errors when executing imports. Our engineers are aware, and recovery efforts are underway.
Affected components
2Snyk in the last 90 days
Full historyIncidents in 90 days
27
Days with an incident
41
Median duration
7 h 1 min
This incident
12× 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·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.
Snyk·Snyk Code Performance Degraded in SNYK-US-02
All services remain stable during our monitoring period. The Snyk Incident Response has been stood down.
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