Incident with Git Operations
Git Operations has degraded performance. The incident started at 20:57 UTC and continues. GitHub reports that the degradation is mitigated and GitHub is monitoring for stability.
State
Monitoring
Started
Ongoing for
1 h 43 min
Worst impact
Degraded
Timeline
4 updatesInvestigating
1 h 42 min 99%
Monitoring
1 min 1%
Updates
Times in UTCAs posted by GitHub
The degradation affecting Git Operations has been mitigated. We are monitoring to ensure stability.
Our mitigation is rolled out and customers should start seeing improvements to Git Operations. We will continue to provide updates on mitigation status.
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.
We are investigating reports of degraded performance for Git Operations
Affected components
1GitHub in the last 90 days
Full historyIncidents in 90 days
49
Days with an incident
36
Median duration
1 h 22 min
This incident
1.3× the median
Other GitHub incidents
All incidentsGitHub·Incident with API, Git, and Copilot requests
GitHub reports degraded performance for API Requests, Issues, and Copilot. GitHub first reported the issue as investigating and then mitigated each component. GitHub says the incident is resolved and it lasted 31 minutes.
GitHub·Elevated errors on GPT-5.4 Nano
GPT-5.4 Nano had elevated errors and degraded availability in Copilot products and IDE surfaces. The Copilot AI Model Providers component was affected. GitHub reported the issue as resolved. The incident lasted 38 minutes.
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.
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.
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.
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.
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 "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.
https://outages.cc/feed.xml?providers=github/feed subscribe https://outages.cc/feed.xml?providers=githubFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane