Netlify favicon

Netlify outage on 2026-10-20

netlifystatus.com
October 2026 20 Major incident

Netlify's Agent Runner failed for 1h 12m on 20 October 2026, starting at 07:47 UTC. The fault sat on Netlify's side, in the Agent Runner component, not in anything you control.

Started

07:47 UTC

Duration

Lasted 1h 12m

Source

IsDown

Next time

Netlify is degraded. Is your product working?

An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.

50 monitors for your own websites. No card.

What happened?

Netlify opened an incident at 07:47 UTC titled "Agent Runner failures", saying it was investigating increased failures in that component. At 08:04 it moved to monitoring, and by 08:55 it marked the incident resolved, for a total of 1h 12m. Netlify's status page lists no affected components for this entry, so you cannot tell from the page alone which other services, if any, sat behind Agent Runner. The three updates are the entire public record: no further detail was filed about what caused the failures or how they were fixed. No user reports came in during this window, so there is nothing from outside Netlify to cross check the timeline against. In the past 90 days Netlify has logged 13 incidents with a median duration of 36 minutes, which puts this one longer than typical. Across all time Netlify averages 5.7 incidents a month, 441 total, so a single Agent Runner incident is a routine entry in a long log rather than an anomaly. UptimeRobot's own probes against Netlify's API component, run from EU and NA regions every 60 seconds, stayed at 100% uptime for the day, the week and the month. That is expected: the probes watch the API, not the Agent Runner, so they had nothing to flag here. No post-mortem has been published.

Learning

This incident sat in Netlify's Agent Runner, a specific internal component, while the API that UptimeRobot's probes check kept answering normally throughout, which is why uptime read 100% across 24 hours, 7 days and 30 days even as Netlify's own status page recorded a live incident. Both readings are correct at once: the API being up and the Agent Runner failing are two different facts about two different parts of the same provider. If your product depends on Agent Runner specifically, a clean API probe would never have told you it was degraded, because that probe simply was not looking at the part that broke. This is the general shape of provider outages that uptime checks on your own endpoints miss: the failure is inside a component you call but do not operate, and your side of the integration can look flawless while that call fails. Over the past 30 days UptimeRobot recorded 7 incidents on Netlify with a median duration of 52m, all resolved, context worth having when a short failure like this one shows up again. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.