Live

Partial Degradation of SCA Test Flows (Multi-tenant US-01)

0

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 updates
16:5217:0617:2117:3617:50
DegradedUpdate postedTimes in UTC

Investigating

58 min 100%

Updates

Times in UTC

As posted by Snyk

Investigating

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.

Investigating

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

2
Snyk Open SourceSNYK-US-01 (app.snyk.io) - Snyk Open Source

Snyk in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

28

Days with an incident

41

Median duration

6 h 39 min

This incident

85% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

5 days
median 6 h 39 min
90 days agoToday

Other Snyk incidents

All incidents

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=snyk
Slack
/feed subscribe https://outages.live/feed.xml?providers=snyk

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane