Imports and PR Checks Degraded

What to do

• Check whether you use Snyk Snyk Code, Snyk Code, Snyk Code, Snyk Code and 6 more. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 2h 25m it lasted.

  Anything that failed between 2026-09-09 14:37 UTC and 2026-09-09 17:02 UTC may need a replay.

• Subscribe to Snyk's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=snyk works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Snyk 4

1. investigatingSep 9, 2026, 2:37 PM UTC

   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.

   provider

2. investigatingSep 9, 2026, 3:29 PM UTC

   Our investigations remain ongoing. We will keep you updated with our progress.

   provider

3. identifiedSep 9, 2026, 3:47 PM UTC

   Snyk engineers have identified the root cause of the issue and are now deploying a mitigation across all affected environments.

   provider

4. resolvedSep 9, 2026, 5:02 PM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.