Netlify outage, May 2026: Failed & delayed builds due to Github incident
Netlify reported and resolved an incident: Failed & delayed builds due to Github incident. It lasted 2.1 hours.
OKResolved
From Netlify's official status page, in their words.
What happened
- Started
- Resolved
- Duration
- 2.1 hours
- Impact
- major
- Affected
- Build Pipeline
Why it happened
Netlify has not given a cause in its updates. We never guess one.
Timeline
Newest first. From Netlify's official status page, in their words.
- resolved
This incident has been resolved, and builds have returned to functioning normally.
- identified
In addition to delayed builds, we are also experiencing build failures due to the current incident at Github.
- investigating
We are currently experiencing delays in our build pipeline due to a current incident at Github.
What this means for a business (and what to check now)
- Retry anything that failed during the 2.1 hours.
- Enter any payments, bookings or jobs you took another way.
- If a deadline fell inside the window, keep this page as your record of the outage.
The full guide: what to do when a service you rely on is down
Other Netlify incidents
- Delays in build logs appearing in the UI, resolved after 9 hours
- Netlify reports degraded performance, open, identified
- Elevated Build Errors and Agent Runner failures, resolved after 57 minutes
- Delays in build logs appearing in the UI, resolved after 11.3 hours
- Delayed Edge Functions and Functions logs, resolved after 3.9 hours
Hear about the next Netlify incident as it starts
Free email alerts when the official status changes, with what to do while it is down.