Disruption with some GitHub services
GitHub reported a disruption with some GitHub services. GitHub says the incident is resolved and lasted 71 minutes. GitHub states that the degradation is mitigated.
State
Resolved
Started
Lasted
1 h 11 min
Worst impact
Degraded
Timeline
4 updatesInvestigating
39 min 55%
Monitoring
32 min 45%
Updates
Times in UTCAs posted by GitHub
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.
The degradation has been mitigated. We are monitoring to ensure stability.
Starting around 18:02 UTC on November 5, GitHub web sessions stopped being renewed based on recent activity, so users were signed out when their sessions expired due to inactivity. These sign-outs were caused by a bug in session renewal, not due to a security incident. We believe we fixed the bug at 05:23 UTC on November 19, and sessions created since then should renew as usual. We’re continuing to monitor the situation. If you had an inactive session from that period, you may still find that you’re signed out when you return to GitHub. If that happens, all you need to do is sign back in.
We are investigating reports of impacted performance for some GitHub services.
GitHub in the last 90 days
Full historyIncidents in 90 days
69
Days with an incident
45
Median duration
1 h 11 min
This incident
About the median
Other GitHub incidents
All incidentsGitHub·Degraded availability for GPT-6 Luna in Copilot
The GPT-6 Luna model has degraded availability in Copilot products and IDE surfaces and affects Copilot AI Model Providers. GitHub reports that the incident is resolved. It lasted 41 minutes.
GitHub·Degraded Availability for MAI Code 2 Flash in Copilot
GitHub reports degraded availability for the MAI Code 2 Flash model in Copilot products and IDE surfaces, and this affects Copilot AI Model Providers. The incident is resolved and lasted 34 minutes. GitHub stated a workaround during the incident: choose another model or select Copilot Fusion.
GitHub·Incident with Pull Requests
GitHub Pull Requests and Actions had degraded performance. Some users had difficulty merging pull requests. GitHub reports that the incident is resolved. It lasted 4 hours and 27 minutes.
GitHub·Copilot experiencing degraded model availability for some GPT models
GitHub Copilot has degraded availability for the GPT models gpt-5.6-sol-fast, gpt-5.6-sol, gpt-6.1-terra, and gpt-6-luna in Copilot products and IDE surfaces. GitHub reports that the incident is resolved. The outage lasted about 74 minutes. GitHub stated that an upstream model provider caused the issue.
GitHub·Incident with Pull Requests
GitHub Pull Requests had degraded availability. Some merge attempts timed out. GitHub reported the incident as resolved. The incident lasted about 2 hours and 42 minutes.
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.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.
https://outages.live/feed.xml?providers=github/feed subscribe https://outages.live/feed.xml?providers=githubFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane