Snyk Apps - Degraded Functionality for App Management
Snyk Apps app-management functions have degraded functionality. This issue started at 13:07 UTC on 17 November 2026. Snyk reports that it is investigating the issue and that its Incident Response team is working on it.
State
Investigating
Started
Ongoing for
47 min
Worst impact
Degraded
Timeline
1 updateInvestigating
47 min 100%
Updates
Times in UTCAs posted by Snyk
Some functions affecting managing Snyk Apps configurations are currently experiencing downtime. Existing Snyk Apps are unaffected and continue to be fully operational. The Snyk Incident Response has been initiated and engineers are working on the issue.
Snyk in the last 90 days
Full historyIncidents in 90 days
26
Days with an incident
40
Median duration
14 h 16 min
This incident
94% shorter than the median
Other Snyk incidents
All incidentsSnyk·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.
Snyk·Intermittent failures for Go-based projects
Snyk Open Source and SNYK-US-01 (app.snyk.io) had intermittent failures for Go-based projects on all flows except the CLI flow. Snyk reports that this incident is resolved. It lasted 14 hours and 16 minutes.
Snyk·Issue Resolving Entitlements
Snyk reported failures resolving entitlements. The issue affected Snyk Code, Snyk Container, Snyk IaC, and Snyk Open Source in the SNYK-US-02, SNYK-EU-01, and SNYK-AU-01 regions. Snyk has resolved the issue. It lasted about 17 hours and 45 minutes.
Snyk·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.
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