outages.live
Live
SnykIncident · 2026-11-02 19:43 UTC

Issue Resolving Entitlements

Partial outageOfficial update
0

Snyk entitlements do not resolve for Snyk Code, Snyk Container, Snyk IaC, and Snyk Open Source in the US-02, EU-01, and AU-01 regions. Snyk has identified the cause. Snyk released a fix for AU-01 and continues the fix for EU-01 and US-02.

State

Identified

Started

2 h ago

2026-11-02 19:43 UTC

Ongoing for

2 h 1 min

Worst impact

Partial outage

Timeline

2 updates
19:4320:1320:4321:1321:44
Partial outageUpdate postedTimes in UTC

Investigating

1 h 17 min 64%

Identified

44 min 36%

Updates

Times in UTC

As posted by Snyk

Identified2026-11-02 21:00 UTC

Snyk engineers have identified the cause of the failures and have pushed a fix to Mult-Tenant AU. The fix is in progress for MT-EU and MT-US. We will update you once this is completed.

Investigating2026-11-02 19:45 UTC

Snyk engineers are investigating an issue impacting Multi-Tenant US-02, Multi-Tenant EU, and Multi-Tenant AU. Customers may experience failures resolving entitlements. The Snyk Incident response has been enacted.

Affected components

16
Snyk CodeSnyk ContainerSnyk IaCSnyk Open SourceSNYK-US-02 (app.us.snyk.io) - Snyk CodeSNYK-US-02 (app.us.snyk.io) - Snyk ContainerSNYK-US-02 (app.us.snyk.io) - Snyk IaCSNYK-US-02 (app.us.snyk.io) - Snyk Open Source

Snyk in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

27

Days with an incident

41

Median duration

8 h 4 min

This incident

75% shorter than the median

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

5 days
median 8 h 4 min
90 days agoToday

Other Snyk incidents

All incidents

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.

Resolvedresolved 4 d ago

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.

Resolvedresolved 8 d ago

Snyk·Snyk Support portal degradation

There have been no further interruptions to our service, declaring the incident as resolved.

Resolvedresolved 10 d ago

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.

Resolvedresolved 8 d ago

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.

Resolvedresolved 13 d ago

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