Skip to main content

GitHub Copilot · 11h ago

Incident with Actions, Issues, API Requests and Pull Requests

Resolved

Yes — GitHub Copilot had a problem on October 26, 2026, and GitHub Copilot has since marked it resolved. GitHub Copilot's latest word: “On October 26, 2026, between 17:52 and 18:49 UTC, some customers experienced slower response times across the Checks API, Issues, Pull Requests, GraphQL, Notifications, and related services. Impact was limited to requests served from one of our datacenter sites. Some GraphQL requests failed, and some notifications were delayed. Among GraphQL requests served from the affected site, the average error rate was 5.68%, with a peak five-minute error rate of 14.32%. <br /><br />Unusually large requests for contribution history overwhelmed part of our database infrastructure, causing a backlog. Requests continued reaching the slow component rather than being redirected to healthy systems. Restarting the component restored its performance. The incident was marked mitigated at 18:46 UTC and resolved at 18:57 UTC. <br /><br />We are adding limits to these requests, improving alerts to detect overload sooner, and strengthening automatic redirection to healthy systems.”

See GitHub Copilot's live status →

Timeline

Started: 10/26/2026, 6:48:26 PM

Last update: 11/16/2026, 11:15:16 PM

Resolved: 10/26/2026, 6:57:22 PM

Affected: brv1bkgrwx7q, kr09ddfgbfsf, hhtssxt0f5v2, br0l2tvcx85d

GitHub Copilot's official report →

Updates

  • resolved

    On October 26, 2026, between 17:52 and 18:49 UTC, some customers experienced slower response times across the Checks API, Issues, Pull Requests, GraphQL, Notifications, and related services. Impact was limited to requests served from one of our datacenter sites. Some GraphQL requests failed, and some notifications were delayed. Among GraphQL requests served from the affected site, the average error rate was 5.68%, with a peak five-minute error rate of 14.32%. <br /><br />Unusually large requests for contribution history overwhelmed part of our database infrastructure, causing a backlog. Requests continued reaching the slow component rather than being redirected to healthy systems. Restarting the component restored its performance. The incident was marked mitigated at 18:46 UTC and resolved at 18:57 UTC. <br /><br />We are adding limits to these requests, improving alerts to detect overload sooner, and strengthening automatic redirection to healthy systems.

    10/26/2026, 6:57:22 PM

  • monitoring

    We saw elevated latency affecting REST API requests, including Checks, and some Actions, Issues, Pull Requests, and GraphQL functionality. Some requests may have been slow or timed out, and notifications were delayed from 17:59 UTC - 18:40 UTC.<br /><br />We mitigated the issue and all services have recovered.

    10/26/2026, 6:54:04 PM

  • monitoring

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

    10/26/2026, 6:50:58 PM

  • investigating

    We are investigating reports of degraded performance for API Requests, Actions, Issues and Pull Requests

    10/26/2026, 6:48:26 PM

More GitHub Copilot incidents

Is GitHub Copilot down right now?All outage history →