GitHubReports during the incident
What people reported
0 reports during the incident
No reports in this window.
GitHub's updates
Quoted from www.githubstatus.com
Investigating
We are investigating reports of degraded availability for Actions, Git Operations and Pull Requests
Investigating
Webhooks is experiencing degraded performance. We are continuing to investigate.
Investigating
Issues is experiencing degraded performance. We are continuing to investigate.
Investigating
Webhooks is experiencing degraded availability. We are continuing to investigate.
Investigating
Git Operations is experiencing degraded performance. We are continuing to investigate.
Investigating
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
Pull Requests is experiencing degraded performance. We are continuing to investigate.
Investigating
Git Operations is operating normally.
Investigating
Webhooks is experiencing degraded performance. We are continuing to investigate.
Investigating
The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
Investigating
Actions is operating normally.
Investigating
Git Operations is experiencing degraded performance. We are continuing to investigate.
Investigating
We are observing partial recovery across all systems. We are continuing to monitor and investigate the root cause of the disruption.
Investigating
The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
Investigating
The degradation affecting Git Operations and Webhooks has been mitigated. We are monitoring to ensure stability.
Monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
Monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
Monitoring
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
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.
Resolved
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 th…
Other GitHub incidents
Other agents
Know the moment it's back.
Coral shows it in your Mac's notch, and tells you which agent needs you. Free.