Live  /  Netlify  /  Incident

Netlify: Agent Runner failures

Netlify · netlify.comMajor incidentResolved2026-10-20 08:55 UTC
Public — what happened

Summary

Netlify said it was looking into a rise in failures affecting its Agent Runner feature, which it rated as a major incident. The company first posted about the problem at 07:47 UTC on 2026-10-20 and did not say who was affected or what caused it. By 08:04 UTC Netlify said it had moved to monitoring the situation, and the incident was marked resolved at 08:55.

Affected

Agent Runners

As listed on Netlify’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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 44, 2026, our weekly internet health report.

The full archive is on the Netlify status & history page.

Related: Netlify status & history. SquidGrid is not affiliated with Netlify.