GitHub change history

GitHub reported a critical degradation affecting Actions, Git Operations, Issues and Pull Requests, with a recurring write-operation outage from 16:52 to 17:01 UTC. The incident opened at 2026-10-07 17:17 UTC and resolved at 2026-10-07 18:04 UTC, lasting 47 min. GitHub applied mitigations and said both outages shared the same root cause, without specifying it here.

GitHub reported a critical outage affecting write operations across Git Operations, Pull Requests, Issues, Actions, the API, webhooks and authentication. The record starts and resolves at 2026-10-07 16:25 UTC (computed duration: 0 min), although GitHub described two outages totaling about 19 minutes. GitHub said the root cause was identified and preventive mitigations were being applied.

GitHub’s critical incident degraded Pull Requests and Webhooks and paused enterprise migrations, starting 2026-10-06 19:57 UTC and resolving 2026-10-06 23:40 UTC (3 h 43 min). GitHub reported an outage from 19:44 to 19:50 UTC affecting 12 services, with approximately 1.16 million failed requests. It identified GitHub Enterprise Importer as the trigger and reported deploying a mitigation.

GitHub reported a major degradation causing slow loads, timeouts, and errors on organization and enterprise billing, licensing, and settings pages. The incident started at 2026-10-05 23:47 UTC and was resolved at 2026-10-06 01:32 UTC, lasting 1 h 44 min; 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). Runner delays meant 26.5% of GitHub-hosted jobs did not start within five minutes, delaying customer workflows. GitHub applied mitigations, cleared queued jobs, and reported both services operating normally.

GitHub reported a critical Copilot Code Review degradation starting 2026-09-28 21:16 UTC, resolved at 2026-09-28 22:08 UTC (51 min). Approximately 70% of requested reviews did not complete across all environments; affected users needed to re-request reviews. GitHub attributed the issue to a dependent-service change and reported a revert underway before recovery.

GitHub reported a major Gemini 3.8 Flash degradation in Copilot 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; mitigation was reported at 11:45 UTC. Other models were unaffected; users could switch models or use 'Auto'.

GitHub reported critical degradation affecting Actions, API Requests, Issues, Pages and Pull Requests from 2026-09-13 09:16 UTC to 2026-09-13 10:44 UTC (1 h 28 min). Database replication delays increased authorization errors; GitHub reduced cluster load through internal load-shedding and resolved the incident. The final update dates customer impact from 08:43 UTC.

GitHub’s major Copilot code review incident ran from 2026-09-04 20:39 UTC to 2026-09-04 22:26 UTC (1 h 47 min). Affected pull request reviews failed to complete or post comments because an authentication-permissions change blocked submissions to the GitHub API; reverting the change restored normal operation.

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 record started at 2026-08-27 10:04 UTC and 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.

GitHub reported critical Actions and Pages degradation from 2026-08-26 15:11 UTC to 2026-08-26 18:01 UTC (2 h 49 min). Actions jobs failed to start or were delayed; Pages performance degraded. Workflow-trigger database write saturation caused the impact; failover did not fully restore service. At recovery, 3.7% of early larger-runner jobs remained stuck, awaiting cancellation.

GitHub reported a major degradation affecting Claude Fable 5 in Copilot products and IDE surfaces, 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. GitHub attributed it to an upstream provider issue, resolved through the provider’s mitigation.

GitHub’s critical Copilot Cloud Agent incident started at 2026-08-20 14:43 UTC and resolved at 2026-08-21 00:37 UTC, lasting 9 h 54 min. Task status and results were delayed by up to 60 to 90 minutes; 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 2026-08-18 10:23 UTC (46 min). Customers could not run jobs on Actions Larger Runners or view/manage Actions Runners and Runner Groups through the GitHub UI and API; GitHub attributed the failures to backend requests resolving essential metadata.

GitHub reported a critical outage affecting Issues, Pull Requests, APIs, Actions and Copilot, with elevated errors and latency. Peak web/API error rates were approximately 20%; archive and raw-content downloads reached approximately 50%. It started 2026-08-17 13:40 UTC and was resolved at 2026-08-17 21:15 UTC, lasting 7 h 35 min.

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

GitHub Actions experienced critical degraded availability from 2026-08-06 15:22 UTC to 2026-08-07 02:04 UTC (10 h 41 min), causing failed or queued workflows on GitHub-hosted and self-hosted runners. At peak, 71% of runs experienced infrastructure failures. Users with stuck Actions Runner Controller pods could delete them or redeploy the controller to create replacement runners.