Increased task-related errors for Copilot Mission Control
Copilot Mission Control had increased errors in listing and creating tasks. GitHub reports that the incident is resolved. The incident lasted about 77 minutes.
State
Resolved
Started
Lasted
1 h 17 min
Worst impact
Degraded
Timeline
5 updatesInvestigating
1 h 17 min 100%
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.
We're continuing to see recovery as rollout continues
We've identified the issue with a specific client version and are deploying a mitigation. We are already seeing partial recovery.
Copilot Mission Control is experiencing increased error rates (approx 2.5%) in listing and creating tasks due to upstream database throttling. We are investigating two potential mitigations.
We are investigating reports of impacted performance for some GitHub services.
GitHub in the last 90 days
Full historyIncidents in 90 days
51
Days with an incident
37
Median duration
1 h 23 min
This incident
About the median
Other GitHub incidents
All incidentsGitHub·Incident with Pull Requests, Git Operations and Issues
GitHub reports problems with Git Operations, Issues, Pull Requests and Actions. The impact is a partial outage. GitHub is investigating the issue and reports degraded performance in Actions and degraded availability in Pull Requests.
GitHub·Incident with Git Operations
Git Operations had degraded performance. GitHub reports that the incident is resolved. The incident lasted 104 minutes.
GitHub·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.
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