Error accessing Netlify-hosted sites
This incident has been resolved. Sites on our High-Performance Edge Network have returned to normal operation. The incident began at 12:19 UTC and service was restored at 13:14 UTC.
The latest update from Netlify.
State
Resolved
Started
27 d ago
2026-10-05 12:44 UTC
Lasted
50 min
until 2026-10-05 13:34 UTC
Worst impact
Degraded
Timeline
5 updatesInvestigating
33 min 65%
Identified
7 min 14%
Monitoring
11 min 21%
Updates
Times in UTCAs posted by Netlify
This incident has been resolved. Sites on our High-Performance Edge Network have returned to normal operation. The incident began at 12:19 UTC and service was restored at 13:14 UTC.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We are continuing to investigate this issue.
We are investigating reports of errors affecting access to sites on our High-Performance Edge Network. Our engineering team is actively investigating the issue. We will provide additional updates as more information becomes available.
Affected components
1Netlify in the last 90 days
Full historyIncidents in 90 days
16
Days with an incident
15
Median duration
51 min
This incident
About the median
Other Netlify incidents
All incidentsNetlify·Elevated Build Errors and Agent Runner failures
The issue affecting builds and agent runs has been resolved.
Netlify·Delays in build logs appearing in the UI
This incident has been resolved.
Netlify·Delayed Edge Functions and Functions logs
This incident has been resolved.
Netlify·Delays in build logs appearing in the UI
The issue causing delays in build logs appearing in the Netlify UI has been resolved.
Netlify·Agent Runner failures
This incident has been resolved.
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.cc/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.cc/feed.xml?providers=netlify/feed subscribe https://outages.cc/feed.xml?providers=netlifyFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane