Snyk incident

GitHub Integration Degradation

Minor Resolved View vendor source →
Started
Feb 09, 2026, 05:04 PM UTC
Resolved
Feb 09, 2026, 05:43 PM UTC
Duration
38m
Detected by Pingoru
Feb 09, 2026, 05:04 PM UTC

Affected components

Snyk AppRiskSnyk AppRiskSnyk AppRiskSnyk AppRiskSnyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk CodeSnyk ContainerSnyk ContainerSnyk ContainerSnyk ContainerSnyk ContainerSnyk IaCSnyk IaCSnyk IaCSnyk IaCSnyk IaCSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open SourceSnyk Open Source

Update timeline

  1. identified Feb 09, 2026, 05:04 PM UTC

    Snyk engineers identified service degradation across all GitHub integrations, caused by a third-party incident that began at 16:34 UTC. The Snyk incident response has been activated, and engineers are actively monitoring the issue.

  2. resolved Feb 09, 2026, 05:43 PM UTC

    All services have recovered and are operating normally after the third party took mitigation steps to restore services. The Snyk Incident response has been stood down.

Looking to track Snyk downtime and outages?

Pingoru polls Snyk's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Snyk reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Snyk alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Snyk for free

5 free monitors · No credit card required