Incident with Git Operations, Pull Requests and Actions

Git OperationsPull RequestsActions

1. 7 Oct 16:25 UTCResolvedOn October 7, 2026, GitHub had two outages of write operations with the same cause, totaling about 19 minutes. The first ran from 15:06 to 15:16 UTC (about 10 minutes) and the second from 16:52 to 17:01 UTC (about 9 minutes). In both windows, actions that save or change data failed across Git operations, pull requests, issues, GitHub Actions, the API, webhooks, sign-in and authentication, GitHub Apps and OAuth, code scanning, Codespaces, and Copilot. Reading data was largely unaffected.In the first outage, 5.6% of all web and API requests failed, peaking at 8.9%, and more than 12,000 organizations saw failed requests. Up to 26% of Git authentication requests failed, and 17% of Actions workflow runs failed with infrastructure errors. In the second outage, 6.2% of web and API requests failed, peaking at 9.3%, and more than 11,000 organizations were affected. Up to 25% of Git authentication requests failed, and 19% of Actions workflow runs failed. No databases experienced data loss, and operations retried after recovery succeeded.GitHub relies on an internal service that keeps track of which database servers should receive new and updated data. While replacing machines that run this service as part of regular maintenance, one of the new machines started with an outdated copy of its records, which still listed database servers we had already retired. When this node came online, it incorrectly modified routing configuration with the outdated records, routing write requests to non-existent database servers.Each outage ended when one of our established machines with correct confi…
2. 7 Oct 16:25 UTCResolvedOn October 6, 2026, from 19:44 to 19:50 UTC, GitHub experienced a service outage with elevated error rates peaking at 1.30% of all requests, totaling approximately 1.16 million failed requests. This impacted 12 services across [GitHub.com](http://GitHub.com), including Pull Requests, Webhooks, Repos, OAuth, Git over SSH, Codespaces, and Gists. The incident was triggered by GitHub Enterprise Importer (GEI) making multiple, long duration queries which saturated a database connection pool. Recovery was seen at approximately 19:50 UTC once the migration's calls stopped; GEI migrations were reenabled at 23:32 UTC after a code fix was merged.We have completed a detailed root-cause review and are implementing improved database-health safeguards. We will continue to review and add additional safeguards to prevent future recurrence.
3. 7 Oct 16:25 UTCResolvedThis incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
4. 7 Oct 16:23 UTCUpdateGit Operations, Pull Requests and Actions are fully recovered and stable. The root cause has been identified and mitigations are being applied to prevent a reoccurrence.
5. 7 Oct 15:58 UTCUpdateWe are seeing full recovery across all systems including Git Operations, Pull Requests and Actions. We are continuing to investigate the root cause of the disruption between 15:06 UTC and 15:16 UTC, and will share another update shortly.
6. 7 Oct 15:56 UTCUpdateThe degradation has been mitigated. We are monitoring to ensure stability.
7. 7 Oct 15:49 UTCMonitoringThe degradation has been mitigated. We are monitoring to ensure stability.
8. 7 Oct 15:49 UTCUpdateThe degradation affecting Git Operations and Webhooks has been mitigated. We are monitoring to ensure stability.
9. 7 Oct 15:47 UTCUpdateThe degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
10. 7 Oct 15:41 UTCUpdateWe are observing partial recovery across all systems. We are continuing to monitor and investigate the root cause of the disruption.
11. 7 Oct 15:35 UTCUpdateGit Operations is experiencing degraded performance. We are continuing to investigate.
12. 7 Oct 15:32 UTCUpdateActions is operating normally.
13. 7 Oct 15:31 UTCUpdateThe degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
14. 7 Oct 15:27 UTCUpdateWebhooks is experiencing degraded performance. We are continuing to investigate.
15. 7 Oct 15:27 UTCUpdateGit Operations is operating normally.
16. 7 Oct 15:25 UTCUpdatePull Requests is experiencing degraded performance. We are continuing to investigate.
17. 7 Oct 15:24 UTCUpdateWe observed widespread impact across GitHub services between 15:06 UTC and 15:16 UTC, and are investigating the root cause. We are seeing all systems recover, and will provide another update shortly.
18. 7 Oct 15:21 UTCUpdateGit Operations is experiencing degraded performance. We are continuing to investigate.
19. 7 Oct 15:16 UTCUpdateWebhooks is experiencing degraded availability. We are continuing to investigate.
20. 7 Oct 15:15 UTCUpdateIssues is experiencing degraded performance. We are continuing to investigate.
21. 7 Oct 15:14 UTCUpdateWebhooks is experiencing degraded performance. We are continuing to investigate.
22. 7 Oct 15:14 UTCInvestigatingWe are investigating reports of degraded availability for Actions, Git Operations and Pull Requests

No field changes in the recorded history.

Cite this recorded revision to keep the same title, summary, facts and links when the page changes.

A day selects the latest observation by the end of that UTC day; today's selection can change until midnight. History starts when this installation records it.

• Service status now: every provider ChangeIntel reads, with ongoing incidents first.
• Status RSS feed: new and ended incidents as they happen.
• Everything about GitHub: its changes, known issues and incidents on one timeline.