Minor impactResolvedDevOps

Snyk incident: Imports and PR Checks Degraded

Snyk reported this minor-impact incident on its official status page on Sep 9, 2026, 14:37 UTC. It was resolved after 2h 25m.

Right now Snyk is operational. Live Snyk status →

🔔 Get alerted when Snyk has issuesFree · email alerts · no credit card
Sep 9, 2026, 14:37 UTC
started
Sep 9, 2026, 17:02 UTC
resolved
2h 25m
duration
Minor
impact

Affected components

  • Snyk Code
  • Snyk Open Source
  1. resolvedSep 9, 2026, 17:02 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.

  2. identifiedSep 9, 2026, 15:47 UTC

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

  3. investigatingSep 9, 2026, 15:29 UTC

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

  4. investigatingSep 9, 2026, 14:37 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Snyk's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Snyk have incidents?

Snyk reported 17 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 6h 27m. See Snyk's uptime and incident history

Snyk incident on Sep 9, 2026: Imports and PR Checks Degraded · APIStatus.watch