Partially Degraded Service
Netlify reports degraded service on the Atlassian Bitbucket API, Webhooks, and SSH components. Netlify reports that this incident is resolved. The incident lasted 105 minutes.
State
Resolved
Started
Lasted
1 h 45 min
Worst impact
Degraded
Timeline
2 updatesComponents degraded
1 h 45 min 100%
Updates
Times in UTCAs posted by Netlify
Affected components
3Netlify in the last 90 days
Full historyIncidents in 90 days
32
Days with an incident
24
Median duration
43 min
This incident
2.4× the median
Other Netlify incidents
All incidentsNetlify·Delayed Support Email Delivery to Microsoft 365 and Outlook Mailboxes
Netlify support email responses to Microsoft 365 and Outlook mailboxes had delivery delays. The Netlify Helpdesk component was affected. Netlify reports that the incident is resolved. The incident lasted about 19 hours and 24 minutes.
Netlify·Partially Degraded Service
Netlify reported a degraded service that affected GitHub Webhooks. Netlify reports that this incident is resolved. The incident lasted 36 minutes.
Netlify·Increase in errors for drag and drop deploys
Between 2026-11-12 09:00 UTC and 2026-11-13 17:27 UTC, a high number of drag and drop deploys were failing. The issue is now resolved.
Netlify·Partially Degraded Service
Netlify reported that GitHub Webhooks had degraded performance. Netlify reports that the issue is resolved. The interruption lasted 18 minutes.
Netlify·Partially Degraded Service
Netlify reported a partially degraded service for GitHub Webhooks. Netlify resolved the incident. The outage lasted 3 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