Netlify lists these components: GitHub API Requests, GitHub Git Operations.

When did the incident start and end?

It started at 2026-11-04 10:03 UTC. This page shows the end time when Netlify marks it resolved.

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

Q: What happened?

Netlify reported "Partially Degraded Service" on its status page at 2026-11-04 10:03 UTC. GitHub Git Operations do not work correctly on Netlify. This causes partially degraded service. Netlify reports that the issue is still open.

DegradedOfficial update

GitHub Git Operations do not work correctly on Netlify. This causes partially degraded service. Netlify reports that the issue is still open.

State

Components degraded

Started

Ongoing for

1 h 16 min

Worst impact

Degraded

Timeline

1 update

10:0310:2210:4111:0011:19

DegradedUpdate postedTimes in UTC

Components degraded

1 h 16 min 100%

Updates

Times in UTC

As posted by Netlify

Components degraded

Affected components

GitHub API RequestsGitHub Git Operations

Netlify in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

54 min

This incident

1.4× the median

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

11 h 16 min

median 54 min

90 days agoToday

Other Netlify incidents

All incidents

Netlify·Partially Degraded Service

Netlify reported a partially degraded service. GitHub Git Operations were affected. Netlify reports that the incident is resolved. The incident lasted 102 minutes.

Resolved

Netlify·Delays in build logs appearing in the UI

Netlify build logs did not appear in the Netlify Application UI on time. The Build Pipeline and the Netlify Application UI were affected. Netlify reports that the incident is resolved. It lasted about nine 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.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