Snyk incident

Imports and PR Checks Degraded

Resolved after 2 hours 25 minutes, affecting Snyk Code and Snyk Code and 1 more, on September 9, 2026.

resolved Sep 09, 2026, 05: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.

Started
Sep 09, 2026, 02:37 PM UTC
Resolved
Sep 09, 2026, 05:02 PM UTC
Duration
2h 25m
Detected by Pingoru
Sep 09, 2026, 02:37 PM UTC

Affected components

Snyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open Source

Update timeline

  1. investigating Sep 09, 2026, 02: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.

  2. investigating Sep 09, 2026, 03:29 PM UTC

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

  3. identified Sep 09, 2026, 03:47 PM UTC

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

  4. resolved Sep 09, 2026, 05: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.

Your product runs on more than Snyk

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →