‹ Back to incident history

Incident with API, Git, and Copilot requests

ResolvedMinor incidentGitHub
Tuesday, November 3, 2026 21:25 – Tuesday, November 3, 2026 21:56 (30 min)
Affected components
API Requests
Issues
Copilot
Updates
ResolvedTuesday, November 3, 2026 21:56

On November 3, 2026, between 12:34 and 13:51 UTC, some users experienced authentication failures and errors with the REST and GraphQL APIs, pull requests, Issues, and GitHub Copilot. On average, the error rate was 0.46% and peaked at 0.98% of API requests. Copilot API errors averaged 2.0% and peaked at 3.1%.<br /><br />This was caused by a bug in our process for replacing control-plane servers in one of our compute clusters. When a replacement server did not receive a timely response from the existing cluster, it incorrectly created a separate cluster. This stopped traffic from reaching much of the cluster's capacity and overloaded the authentication servers that were still handling requests.<br /><br />We mitigated the incident by removing the incorrectly configured server.<br />We are also fixing the replacement logic and adding safeguards to prevent servers in this state from serving traffic.

MonitoringTuesday, November 3, 2026 21:54

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

InvestigatingTuesday, November 3, 2026 21:52

API Requests is operating normally.

MonitoringTuesday, November 3, 2026 21:51

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

InvestigatingTuesday, November 3, 2026 21:43

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

InvestigatingTuesday, November 3, 2026 21:42

Issues is experiencing degraded performance. We are continuing to investigate.

InvestigatingTuesday, November 3, 2026 21:25

We are investigating reports of degraded performance for Copilot

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