Imports and PR Checks Degraded
Snyk engineers have deployed the mitigation to all environments, which has resolved the Invalid Credentials errors for customers using the GitHub Cloud integration. No further errors observed during the monitoring period. The incident has been stood down.
The latest update from Snyk.
State
Resolved
Started
53 d ago
2026-09-09 14:37 UTC
Lasted
2 h 25 min
until 2026-09-09 17:02 UTC
Worst impact
Degraded
Timeline
4 updatesInvestigating
1 h 10 min 48%
Identified
1 h 16 min 52%
Updates
Times in UTCAs posted by Snyk
Snyk engineers have deployed the mitigation to all environments, which has resolved the Invalid Credentials errors for customers using the GitHub Cloud integration. No further errors observed during the monitoring period. The incident has been stood down.
Snyk engineers have identified the root cause of the issue and are now deploying a mitigation across all affected environments.
Our investigations remain ongoing. We will keep you updated with our progress.
We're currently investigating reports of degradation affecting some Imports and PR Checks across the Snyk platform. Full impact analysis is currently underway, we will provide further details as the incident progresses. The Snyk Incident Response has been invoked.
Affected components
12Snyk in the last 90 days
Full historyIncidents in 90 days
27
Days with an incident
41
Median duration
7 h 1 min
This incident
65% shorter than 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·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.
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.
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