Live / Netlify / Incident
Netlify: Elevated Build Errors and Agent Runner failures
Netlify · netlify.appMajor incidentResolved2026-10-27 08:45 UTC
Public — what happened
Summary
Netlify reported a major incident beginning at 07:48 UTC on 2026-10-27, in which more builds than usual were failing and its Agent Runner feature was also failing. By 08:10 UTC the company said the problem affecting builds and agent runs had been fixed and that it was watching to confirm. Netlify did not state a cause in its updates, and the incident was marked resolved at 08:45.
Affected
Build Pipeline, Agent Runners
Timeline
- Started — 2026-10-27 07:48 UTC
- Investigating — 2026-10-27 07:48 UTC
- Monitoring — 2026-10-27 08:10 UTC
- Resolved — 2026-10-27 08:45 UTC · 57 min after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Netlify against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Netlify: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Netlify report →
More from Netlify
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.