Partial Degradation of SCA Test Flows (Multi-tenant US-01)
Snyk Open Source SCA test flows are degraded in the Multi-tenant US-01 environment (app.syk.io) for customers who use isolated builds. Imports, PR Checks, and Recurring Tests are affected. Snyk reports the status as investigating.
State
Investigating
Started
Ongoing for
58 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
58 min 100%
Updates
Times in UTCAs posted by Snyk
We have identified the scope of impact. Open source tests for Python, .NET, and Go projects are currently degraded, along with Fix PRs for npm and Yarn. Customers may experience test failures, with Recurring Tests being the most affected. Our engineering team is actively working toward a resolution.
Snyk engineers are investigating a partial degradation impacting SCA test flows, including Imports, PR Checks, and Recurring Tests, for customers using isolated builds in the Multi-tenant US-01 environment. Incident Response has been initiated and engineers are working to resolve the issue. Further updates will be posted here.
Affected components
2Snyk in the last 90 days
Full historyIncidents in 90 days
28
Days with an incident
41
Median duration
6 h 39 min
This incident
85% shorter than the median
Other Snyk incidents
All incidentsSnyk·Snyk EVO Login Issues
Login to the Snyk Evo UI did not work in the SNYK-US-01 (app.snyk.io) and SNYK-AU-01 (app.au.snyk.io) environments. Snyk reports that the incident is resolved and that services are stable. The outage lasted about 6 hours and 39 minutes.
Snyk·Snyk Open Source Degraded
Snyk Open Source had degraded performance in the SNYK-AU-01 (app.au.snyk.io) region. Snyk reports that the incident is resolved. It lasted about 2 hours and 20 minutes.
Snyk·Snyk Open Source and Container Degradation
Between 13:20 and 13:35 UTC, customers within our app.snyk.io environment may have experienced errors when importing projects, monitoring projects and viewing issues in Snyk Open Source and Snyk Container. Services have since returned to normal. Recurring tests will retry automatically. Any imports or monitor runs that failed during this time should complete as normal when re-run.
Snyk·Snyk Apps - Degraded Functionality for App Management
Snyk App management functions had degraded functionality. Existing Snyk Apps continued to work. Snyk reports that the incident is resolved. It lasted about 2 hours and 43 minutes.
Snyk·Snyk Services Degraded
Snyk Code, Snyk Container, and Snyk Open Source are degraded in the SNYK-US-01 (app.snyk.io) environment. Snyk reports that the incident is resolved. The outage lasted 19 minutes.
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.live/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.live/feed.xml?providers=snyk/feed subscribe https://outages.live/feed.xml?providers=snykFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane