Snyk incident: GitHub Integration Service Degraded

Affected components

• Evo by Snyk
• Snyk AppRisk
• Snyk Code
• Snyk Container
• Snyk IaC
• Snyk Open Source

1. resolvedMay 11, 2026, 14:41 UTC

   The upstream issues at GitHub have been resolved. Our engineering team has verified full recovery, and all Snyk GitHub integrations are operating normally. The Snyk Incident Response has been stood down.

2. identifiedMay 11, 2026, 14:35 UTC

   We are currently experiencing degraded performance with our GitHub integrations due to an ongoing, broader service disruption on GitHub’s end. Our team is actively monitoring the situation and will automatically restore full connectivity as soon as the upstream issue is resolved.

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.

• Confluent Cloud: Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4Major · May 8, 2026, 01:14 UTC
• Netlify: Latency in API & BuildsMajor · May 11, 2026, 13:36 UTC
• Intercom: Investigating: Compromised version of intercom-client npm package and intercom-phpMinor · Apr 30, 2026, 16:58 UTC
• Linode: [DirtyFrag] Linux Privilege Escalation VulnerabilityMinor · May 8, 2026, 13:40 UTC
• Netlify: Build Issues due to Github OutageMinor · May 11, 2026, 14:31 UTC

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