Netlify
Netlify is reporting degraded
Checked 3 min ago Degraded
Partially Degraded Service
History
90 days agoToday
Incidents in 90 days
17
Days with an incident
16
Median duration
51 min
Longest incident
11 h 16 min
Components
42High-Performance Edge Network Operational
90 days ago7 days with an incidentToday
Standard Edge Network Operational
90 days ago4 days with an incidentToday
Origin Servers Operational
90 days agoNo incidentsToday
Build Pipeline Degraded
90 days ago7 days with an incidentToday
Netlify Application UI Degraded
90 days ago4 days with an incidentToday
API Operational
90 days agoNo incidentsToday
Hosted DNS Operational
90 days agoNo incidentsToday
Prerendering Operational
90 days agoNo incidentsToday
Identity Operational
90 days agoNo incidentsToday
Netlify Functions Operational
90 days agoNo incidentsToday
Analytics Operational
90 days agoNo incidentsToday
Log Drains Operational
90 days agoNo incidentsToday
Collaborative Deploy Previews Operational
90 days agoNo incidentsToday
Git Gateway Operational
90 days agoNo incidentsToday
Edge Functions Operational
90 days ago3 days with an incidentToday
Netlify Image CDN Operational
90 days ago2 days with an incidentToday
Netlify Blobs Operational
90 days agoNo incidentsToday
Netlify Observability Operational
90 days agoNo incidentsToday
Netlify Connect Operational
90 days agoNo incidentsToday
Netlify Create API Operational
90 days agoNo incidentsToday
Visual Editor Operational
90 days agoNo incidentsToday
Netlify Forms Operational
90 days agoNo incidentsToday
Netlify Support Forums Operational
90 days agoNo incidentsToday
Netlify Helpdesk Operational
90 days agoNo incidentsToday
Oct 22, 2026
Duration3 h 51 min16:19 to 20:10Delayed Edge Functions and Functions logsDegraded
This incident has been resolved.www.netlifystatus.com
Duration3 h 57 min06:15 to 10:12Delays in build logs appearing in the UIDegraded
The issue causing delays in build logs appearing in the Netlify UI has been resolved.www.netlifystatus.com
Affected components
2- Build PipelineDegraded
- Netlify Application UIDegraded
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.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.
RSS
https://outages.live/feed.xml?providers=netlifySlack
/feed subscribe https://outages.live/feed.xml?providers=netlifyGo from tracking outages to fixing production issues with Polylane.
Try Polylane