GitHub reported this critical-impact incident on its official status page on Oct 7, 2026, 16:25 UTC. It was resolved after under a minute.
Right now GitHub is operational. Live GitHub status →
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
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.
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.
The degradation has been mitigated. We are monitoring to ensure stability.
The degradation has been mitigated. We are monitoring to ensure stability.
The degradation affecting Git Operations and Webhooks has been mitigated. We are monitoring to ensure stability.
The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
We are observing partial recovery across all systems. We are continuing to monitor and investigate the root cause of the disruption.
Git Operations is experiencing degraded performance. We are continuing to investigate.
Actions is operating normally.
The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
Webhooks is experiencing degraded performance. We are continuing to investigate.
Git Operations is operating normally.
Pull Requests is experiencing degraded performance. We are continuing to investigate.
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.
Git Operations is experiencing degraded performance. We are continuing to investigate.
Webhooks is experiencing degraded availability. We are continuing to investigate.
Issues is experiencing degraded performance. We are continuing to investigate.
Webhooks is experiencing degraded performance. We are continuing to investigate.
We are investigating reports of degraded availability for Actions, Git Operations and Pull Requests
Overlapping incidents aren't necessarily related.
GitHub reported 67 incidents in the last 90 days, 24 of them major or critical. A typical incident lasted 1h 15m. See GitHub's uptime and incident history