Live

Errors accessing Netlify-hosted sites

This incident has been resolved.

The latest update from Netlify.

State

Resolved

Started

41 d ago

2026-09-21 15:12 UTC

Lasted

1 h 25 min

until 2026-09-21 16:37 UTC

Worst impact

Partial outage

Timeline

5 updates
15:1215:3315:5516:1616:37
Partial outageUpdate postedTimes in UTC

Investigating

33 min 39%

Identified

7 min 8%

Monitoring

45 min 53%

Updates

Times in UTC

As posted by Netlify

Resolved2026-09-21 16:37 UTC

This incident has been resolved.

Monitoring2026-09-21 15:52 UTC

A fix has been implemented and we are monitoring the results. We will provide another update as we continue to monitor recovery.

Identified2026-09-21 15:45 UTC

We have identified the issue and are working to restore normal service. We will provide another update as more information becomes available.

Investigating2026-09-21 15:30 UTC

We are continuing to investigate this issue. Customers may also experience issues accessing the Netlify application and its features.

Investigating2026-09-21 15:12 UTC

We are investigating reports of errors affecting access to Netlify-hosted sites. Our engineering team is actively investigating the issue. We will provide additional updates as more information becomes available.

Affected components

2
High-Performance Edge NetworkStandard Edge Network

Netlify in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

16

Days with an incident

15

Median duration

51 min

This incident

1.7× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

11 h 16 min
median 51 min
90 days agoToday

Other Netlify incidents

All incidents

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.

Prompt
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.

RSS
https://outages.cc/feed.xml?providers=netlify
Slack
/feed subscribe https://outages.cc/feed.xml?providers=netlify

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane