outages.live
Live
GitHubIncident ·

Increased task-related errors for Copilot Mission Control

ResolvedOfficial update
1

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 updates
08:4509:0409:2309:4210:01
DegradedUpdate postedTimes in UTC

Investigating

1 h 17 min 100%

Updates

Times in UTC

As posted by GitHub

Resolved

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.

Investigating

We're continuing to see recovery as rollout continues

Investigating

We've identified the issue with a specific client version and are deploying a mitigation. We are already seeing partial recovery.

Investigating

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.

Investigating

We are investigating reports of impacted performance for some GitHub services.

GitHub in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

51

Days with an incident

37

Median duration

1 h 23 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 23 min
90 days agoToday

Other GitHub incidents

All incidents

GitHub·Incident with Pull Requests, Git Operations and Issues

GitHub reports a partial outage that affects Pull Requests, Git Operations, Issues and Actions. GitHub is investigating the incident, which started at 09:49 UTC.

Partial outage

GitHub·Incident with Git Operations

Git Operations had degraded performance. GitHub reported that the incident is resolved. The incident lasted 1 hour and 45 minutes.

Resolved

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

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