Netlify reported "Partially Degraded Service" on its status page at 2026-11-03 21:03 UTC. Netlify reported degraded service for GitHub Git Operations. Netlify resolved the incident after 6 minutes.

Netlify lists these components: GitHub Git Operations.

When did the incident start and end?

It started at 2026-11-03 21:03 UTC and ended at 2026-11-03 21:09 UTC. It lasted 6 min.

How do I get alerts for Netlify?

Subscribe to the Netlify live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Netlify. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

NetlifyIncident ·

Partially Degraded Service

ResolvedOfficial update

Netlify reported degraded service for GitHub Git Operations. Netlify resolved the incident after 6 minutes.

State

Resolved

Started

Lasted

6 min

Worst impact

Degraded

Timeline

2 updates

21:0321:0421:0621:0721:09

DegradedUpdate postedTimes in UTC

Components degraded

6 min 100%

Updates

Times in UTC

As posted by Netlify

Resolved

Components degraded

Affected components

GitHub Git Operations

Netlify in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

51 min

This incident

88% shorter than 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

Netlify·Partially Degraded Service

Netlify reports degraded service for GitHub Git Operations. The state is degraded, and the incident started 1 minute ago. Netlify has not published an update yet.

Degraded

Netlify·Delays in build logs appearing in the UI

Netlify build logs had delays in the Netlify Application UI. The Build Pipeline was also affected. Netlify reports that the incident is resolved. It lasted about 9 hours.

Resolved

Netlify·Elevated Build Errors and Agent Runner failures

The issue affecting builds and agent runs has been resolved.

Resolved

Netlify·Delays in build logs appearing in the UI

This incident has been resolved.

Resolved

Netlify·Delayed Edge Functions and Functions logs

This incident has been resolved.

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.

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=netlify

Slack

/feed subscribe https://outages.live/feed.xml?providers=netlify

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane