‹ Back to incident history

Increased task-related errors for Copilot Mission Control

ResolvedMinor incidentGitHub
Wednesday, November 4, 2026 16:45 – Wednesday, November 4, 2026 18:01 (1 hr 16 min)
Updates
ResolvedWednesday, November 4, 2026 18:01

On November 4, 2026, between approximately 03:40 UTC and 10:01 UTC, some Copilot agent users experienced errors listing and creating agent tasks. On average, 1.22% of requests were failed, with a peak of 2.68% over a ten-minute interval.<br /><br />The issue occurred when increased task-list traffic and expensive queries exhausted shared database capacity. We mitigated the broader impact by disabling a client experiment and temporarily restricting task-list requests from the affected client. Task-list requests remained restricted after the wider service recovered; we removed the blanket restriction on November 6 and continued a gradual rollout.<br /><br />We’ve since improved task-list queries, moved rate limiting to separate infrastructure and added capacity monitoring. We’re continuing to reduce unnecessary client requests and validate capacity before expanding the rollout to reduce the chance of recurrence.

MonitoringWednesday, November 4, 2026 18:01

The degradation has been mitigated. We are monitoring to ensure stability.

InvestigatingWednesday, November 4, 2026 17:50

We're continuing to see recovery as rollout continues

InvestigatingWednesday, November 4, 2026 17:11

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

InvestigatingWednesday, November 4, 2026 16:47

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.

InvestigatingWednesday, November 4, 2026 16:45

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

Incident data from the GitHub official status page:Read the official incident

About this data

Where does the incident data for GitHub come from?

Data comes from the GitHub official status page, syncs every 5 minutes, and covers 90 days. The detail page links to the original report.

How do I read the component status bars?

Each block is one day. Green means no issue was reported, yellow means degraded performance, red means a major outage, and gray means no data. Availability covers the last 90 days.

Why is history missing for some services?

Only services with a public official status page are included.

How is duration calculated?

Duration runs from the official start time to recovery, or to the current time for ongoing incidents. Incidents spanning multiple days appear on each affected day.

See the full service list and live status in the status overview