Incident with Git Operations, Pull Requests and Actions
Final update
On 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
Timeline
- Resolved · Oct 7, 16:25 UTC
On 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 no
- Monitoring · Oct 7, 16:23 UTC
Git 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.
- Monitoring · Oct 7, 15:58 UTC
We 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.
- Monitoring · Oct 7, 15:56 UTC
The degradation has been mitigated. We are monitoring to ensure stability.
- Monitoring · Oct 7, 15:49 UTC
The degradation has been mitigated. We are monitoring to ensure stability.
- Investigating · Oct 7, 15:49 UTC
The degradation affecting Git Operations and Webhooks has been mitigated. We are monitoring to ensure stability.
- Investigating · Oct 7, 15:47 UTC
The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
- Investigating · Oct 7, 15:41 UTC
We are observing partial recovery across all systems. We are continuing to monitor and investigate the root cause of the disruption.
- Investigating · Oct 7, 15:35 UTC
Git Operations is experiencing degraded performance. We are continuing to investigate.
- Investigating · Oct 7, 15:32 UTC
Actions is operating normally.
- Investigating · Oct 7, 15:31 UTC
The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
- Investigating · Oct 7, 15:27 UTC
Webhooks is experiencing degraded performance. We are continuing to investigate.
- Investigating · Oct 7, 15:27 UTC
Git Operations is operating normally.
- Investigating · Oct 7, 15:25 UTC
Pull Requests is experiencing degraded performance. We are continuing to investigate.
- Investigating · Oct 7, 15:24 UTC
We 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.
- Investigating · Oct 7, 15:21 UTC
Git Operations is experiencing degraded performance. We are continuing to investigate.