outages.live
Live
GitHubIncident ·

Incident with Git Operations

DegradedOfficial update
0

Git Operations has degraded performance. GitHub reports that it identified the issue and rolled out a mitigation. GitHub continues to monitor the mitigation.

State

Investigating

Started

Ongoing for

1 h 29 min

Worst impact

Degraded

Timeline

3 updates
20:5721:1921:4122:0322:26
DegradedUpdate postedTimes in UTC

Investigating

1 h 29 min 100%

Updates

Times in UTC

As posted by GitHub

Investigating

Our mitigation is rolled out and customers should start seeing improvements to Git Operations. We will continue to provide updates on mitigation status.

Investigating

We have identified the issue impacting Git Operations and are beginning to roll out a mitigation. We will follow up with another update when we begin to see recovery.

Investigating

We are investigating reports of degraded performance for Git Operations

Affected components

1
Git Operations

GitHub in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

49

Days with an incident

36

Median duration

1 h 22 min

This incident

About the median

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

20 h 7 min
median 1 h 22 min
90 days agoToday

Other GitHub incidents

All incidents

GitHub·Incident with API, Git, and Copilot requests

GitHub reports degraded performance for API Requests, Issues, and Copilot. GitHub reports that the incident is resolved. The incident lasted 31 minutes.

Resolved

GitHub·Elevated errors on GPT-5.4 Nano

GPT-5.4 Nano had elevated errors in Copilot products and IDE surfaces. The Copilot AI Model Providers component was affected. GitHub reports the incident resolved after 38 minutes.

Resolved

GitHub·Incident with Dependabot

This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Resolved

GitHub·Incident with Actions, Pages, and Webhooks

This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Resolved

GitHub·Disruption with GitHub services

This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Resolved

Follow GitHub

Your coding agent knows when GitHub is down, and tells you when a failure is theirs, not yours. You can also get GitHub 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 "github" and tell me if GitHub 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=github
Slack
/feed subscribe https://outages.live/feed.xml?providers=github

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane