Elevated build and deploy failures
Netlify build and deploy failures affected the Build Pipeline. Netlify identified the issue and resolved it. The incident lasted about 6 minutes.
State
Resolved
Started
Lasted
6 min
Worst impact
Degraded
Timeline
2 updatesIdentified
6 min 100%
Updates
Times in UTCAs posted by Netlify
This incident has been resolved.
We’ve identified an issue at 16:43 UTC that can cause some builds to fail while functions deploy. These affected builds can fail with a system error during the deploy step. Our team is adding capacity and working on a fix.
Affected components
1Netlify in the last 90 days
Full historyIncidents in 90 days
23
Days with an incident
18
Median duration
51 min
This incident
89% shorter than the median
Other Netlify incidents
All incidentsNetlify·Partially Degraded Service
Netlify reported partially degraded service for GitHub Webhooks. Netlify reports that the incident is resolved. The incident lasted 33 minutes.
Netlify·Partially Degraded Service
Netlify reported partially degraded service for GitHub API Requests and GitHub Git Operations. Netlify reports that the issue is resolved. The outage lasted 3 minutes.
Netlify·Partially Degraded Service
Netlify reported partially degraded service for GitHub API Requests and GitHub Git Operations. Netlify reports that the incident is resolved. The incident lasted 90 minutes.
Netlify·Partially Degraded Service
Netlify reported degraded service for GitHub Git Operations. Netlify later reported that the incident is resolved. The outage lasted 93 minutes.
Netlify·Partially Degraded Service
Netlify reported degraded service for GitHub Git Operations. Netlify resolved the incident after 6 minutes.
Follow Netlify
Your coding agent knows when Netlify is down, and tells you when a failure is theirs, not yours. You can also get Netlify incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "netlify" and tell me if Netlify has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=netlify/feed subscribe https://outages.live/feed.xml?providers=netlifyFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane