GitHub Copilot change history

GitHub reported a critical incident affecting Actions, Git Operations, Issues and Pull Requests, opened at 2026-10-07 17:17 UTC and resolved at 2026-10-07 18:04 UTC (47 min). Actual write-operation disruption occurred from 16:52 UTC to 17:01 UTC, recurring from an earlier outage with the same root cause; mitigations were applied.

GitHub reported critical write-operation failures affecting Git Operations, Pull Requests, Issues, Actions, API, webhooks and authentication. Incident metadata lists start and resolution at 2026-10-07 16:25 UTC (computed duration: 0 min), while the vendor described two outage windows totaling about 19 minutes. GitHub reported recovery and an identified root cause, without specifying the cause.

GitHub reported a critical outage affecting Pull Requests, Webhooks and other services, with approximately 1.16 million failed requests. The incident started at 2026-10-06 19:57 UTC and resolved at 2026-10-06 23:40 UTC, lasting 3 h 43 min. Enterprise migrations remained paused after other services recovered; GitHub reported deploying a mitigation.

GitHub reported a major degradation affecting organization and enterprise billing, licensing, and settings pages, with slow loads, timeouts, and errors. The incident started at 2026-10-05 23:47 UTC, lasted 1 h 44 min, and was resolved at 2026-10-06 01:32 UTC; GitHub cited a networking failure and reported deploying a mitigation.

GitHub reported critical Actions and Pages degradation starting 2026-10-05 19:11 UTC, resolved at 2026-10-05 22:49 UTC (3 h 37 min). GitHub-hosted runner jobs were delayed or failed; 26.5% did not start within five minutes. GitHub applied mitigations, cleared queued jobs, and reported both services operating normally.

GitHub Copilot reported a critical Code Review outage starting 2026-09-28 21:16 UTC, resolved at 2026-09-28 22:08 UTC (51 min). Approximately 70% of requested reviews failed across all environments; failed reviews were not automatically retried, so users needed to re-request them from their pull requests. GitHub attributed the issue to a dependent-service change and reported a rollback underway.

GitHub Copilot reported major degraded availability for Gemini 3.8 Flash starting 2026-09-16 07:20 UTC, resolved at 2026-09-16 17:48 UTC (10 h 27 min). Requests failed at an average rate of 6.4% due to a capacity issue; other models were unaffected, and users could switch models or use 'Auto'.

GitHub reported critical degraded availability affecting Actions, API Requests, Issues, Pages and Pull Requests from 2026-09-13 09:16 UTC to resolution at 2026-09-13 10:44 UTC (1 h 28 min). Database replication delays on collab increased authorization and system-wide errors; GitHub reduced cluster load through internal load-shedding and observed recovery.

GitHub reported a major Copilot code review outage: affected reviews failed to complete or post comments. Tracked from 2026-09-04 20:39 UTC to 2026-09-04 22:26 UTC (1 h 47 min), the final report places failures from 20:04 UTC. An authentication-permissions change blocked review submissions to the GitHub API; reverting it restored service.

GitHub reported a critical degradation affecting Kimi K3 in Copilot products and IDE surfaces, with elevated error rates; no other models were impacted. The incident started at 2026-08-27 10:04 UTC and was resolved at 2026-08-27 12:12 UTC, lasting 2 h 8 min. GitHub attributed it to an upstream provider issue, resolved through the provider’s mitigation.

Critical Actions and Pages degradation lasted 2 h 49 min, from 2026-08-26 15:11 UTC to 2026-08-26 18:01 UTC. Actions jobs failed to start, then experienced delays exceeding five minutes; Pages performance degraded. Saturated database-primary writes triggered the disruption; failover did not fully restore service. Queues recovered, but 3.7% of early larger-runner jobs remained stuck pending cancellation.

GitHub Copilot reported a major degradation affecting Claude Fable 5, with elevated errors and requests failing mid-response; no other models were impacted. The incident started at 2026-08-24 07:12 UTC and was resolved at 2026-08-24 07:58 UTC, lasting 46 min. An upstream provider issue caused the disruption, and the provider applied a mitigation.

GitHub Copilot reported a critical incident starting 2026-08-20 14:43 UTC, resolved 2026-08-21 00:37 UTC (9 h 54 min). Some Copilot Cloud Agent users saw task status/results delayed up to 60–90 minutes, while tasks continued running and completing. GitHub cited a regional third-party cloud database outage and deployed a fix.

GitHub reported a major Actions outage starting 2026-08-18 09:36 UTC, resolved at 10:23 UTC (46 min). Its update separately cited 05:02 UTC–11:30 UTC: customers could not run Actions Larger Runners jobs or view/manage Actions Runners and Runner Groups through the GitHub UI/API. The vendor attributed this to failed backend requests resolving essential metadata.

GitHub reported a critical outage affecting Copilot authentication and multiple GitHub.com services, with elevated errors and latency. It started at 2026-08-17 13:40 UTC and resolved at 2026-08-17 21:15 UTC (7 h 35 min); mitigations addressed sporadic Copilot authentication failures, while Copilot usage via the GitHub CLI and GitHub App remained unaffected.

GitHub reported a major disruption affecting login pages and Release Asset downloads, starting 2026-08-12 21:39 UTC and resolved at 2026-08-12 22:56 UTC (1 h 17 min). Some logged-out requests received HTTP 5xx errors because an unusual traffic pattern repeatedly overloaded infrastructure serving those requests.

GitHub Actions had critical degraded availability starting 2026-08-06 15:22 UTC, resolved at 2026-08-07 02:04 UTC; recorded duration was 10 h 41 min. Workflows failed or remained queued on GitHub-hosted and self-hosted runners, with infrastructure failures affecting 71% of runs at peak. Recovery instructions for stuck Actions Runner Controller pods were deletion or application redeployment.