Netlify's build pipeline failed for 57 minutes on 27 October, with builds and Agent Runner jobs erroring out before they could finish. The fault sat on Netlify's side of the pipeline, not in your code or your monitoring.
Started
07:48 UTC
Duration
Lasted 57m
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.
Affected components: Build Pipeline
What happened?
At 07:48 UTC, Netlify opened an incident titled "Elevated Build Errors and Agent Runner failures", covering its Build Pipeline component. The description was plain: builds were failing, and Agent Runner jobs were failing alongside them. This is the part of Netlify that actually compiles and deploys your site, so a failure here means your changes stop reaching production, not that your live site goes down immediately. By 08:10 Netlify said the issue was resolved and moved to monitoring, then closed it fully at 08:45, putting the total window at 57 minutes. Netlify published three updates across that window and nothing more. There is no post-mortem on record, so the cause of the build and Agent Runner failures is not on the record beyond "resolved". No user reports were filed during the window, which on a build-pipeline issue is not unusual since it mainly affects people actively pushing deploys at that hour. This is Netlify's only incident for the day, and it fits a familiar shape for the service: Netlify logs 16 such incidents in the past 90 days with a median duration of 54 minutes, so this one ran close to typical length. At 445 incidents all time and roughly 5.8 a month, build pipeline disruptions are a known, recurring feature of running on Netlify rather than a rare event.
Learning
UptimeRobot's own probes watch Netlify's api component from both the EU and North America, polling every 60 seconds, and they showed 100% uptime across the 24 hour, 7 day and 30 day windows, including through this incident. That is not a contradiction. The probes check whether the API answers requests, and it did. They do not run a build or kick off an Agent Runner job, so they had no way to see a pipeline that accepts the trigger but fails during the build step itself. This is the general shape of a build-pipeline failure: the surface you can ping stays up while the deeper process that turns your commits into a live deploy breaks underneath it. Over the last 30 days UptimeRobot recorded 8 such Netlify incidents, all resolved, with a median duration of 1h 5m, so this pattern of short, self-resolving build failures is consistent rather than a one-off. If you only watch your own site's uptime, an incident like this can pass unnoticed until someone asks why a deploy never went out. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.