Netlify incident: Build Issues due to Github Outage

Affected components

• Build Pipeline

1. resolvedMay 11, 2026, 15:27 UTC

   This incident has been resolved.

2. monitoringMay 11, 2026, 15:20 UTC

   We are continuing to monitor for any further issues.

3. monitoringMay 11, 2026, 14:47 UTC

   We are monitoring improvements.

4. identifiedMay 11, 2026, 14:35 UTC

   The issue has been identified and posted on Github's status page.

5. investigatingMay 11, 2026, 14:31 UTC

   We are experiencing issues with our build pipeline due to degraded performance in Github

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Netlify'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
• Clerk: Account Portal not RedirectingMajor · May 11, 2026, 15:00 UTC
• Upstash: Fly.io Upstash Redis service distruption (FRA region)Major · May 11, 2026, 15:05 UTC
• Intercom: Investigating: Compromised version of intercom-client npm package and intercom-phpMinor · Apr 30, 2026, 16:58 UTC
• Snyk: Snyk Recurring Tests DelayedMinor · May 6, 2026, 15:32 UTC
• Linode: [DirtyFrag] Linux Privilege Escalation VulnerabilityMinor · May 8, 2026, 13:40 UTC
• Snyk: GitHub Integration Service DegradedMinor · May 11, 2026, 14:35 UTC

How often does Netlify have incidents?

Netlify reported 9 incidents in the last 90 days, 4 of them major or critical. A typical incident lasted 31 min. See Netlify's uptime and incident history