GitHub outage on October 7, 2026: Incident with Git Operations, Pull Requests and Actions

GitHub reported an incident affecting GitHub for 1 hour 10 minutes on 7 October 2026, from 15:14 to 16:25 UTC.

github.com All times UTC

Resolved

Official incident reported by GitHub

Started: 15:14; 7 Oct 2026 UTC
Resolved: 16:25; 7 Oct 2026 UTC
Duration: 1h 10m; 1 hour 10 minutes
Impact: Critical; as rated by GitHub
Updates: 20; posted by GitHub

Timeline

All times UTC.

Official incident from GitHub

Incident with Git Operations, Pull Requests and Actions

Resolved Critical impact 7 Oct 2026 15:14 UTC View on GitHub's status page

15:14 Official
Investigating
We are investigating reports of degraded availability for Actions, Git Operations and Pull Requests
15:14 Official
Investigating
Webhooks is experiencing degraded performance. We are continuing to investigate.
15:15 Official
Investigating
Issues is experiencing degraded performance. We are continuing to investigate.
15:16 Official
Investigating
Webhooks is experiencing degraded availability. We are continuing to investigate.
15:21 Official
Investigating
Git Operations is experiencing degraded performance. We are continuing to investigate.
15:24 Official
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.
15:25 Official
Investigating
Pull Requests is experiencing degraded performance. We are continuing to investigate.
15:27 Official
Investigating
Git Operations is operating normally.
15:27 Official
Investigating
Webhooks is experiencing degraded performance. We are continuing to investigate.
15:31 Official
Investigating
The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
15:32 Official
Investigating
Actions is operating normally.
15:35 Official
Investigating
Git Operations is experiencing degraded performance. We are continuing to investigate.
15:41 Official
Investigating
We are observing partial recovery across all systems. We are continuing to monitor and investigate the root cause of the disruption.
15:47 Official
Investigating
The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
15:49 Official
Investigating
The degradation affecting Git Operations and Webhooks has been mitigated. We are monitoring to ensure stability.
15:49 Official
Monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
15:56 Official
Monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
15:58 Official
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.
16:23 Official
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.
16:25 Official
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 this...

"Official" rows are quoted from GitHub's public status page, www.githubstatus.com. Very long posts are shortened.

What our checkpoints saw

HostTracker's checkpoints, which test github.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live GitHub status shows what our checks see right now.

All GitHub incidents Live GitHub status Every service we track

Does your product depend on GitHub?

An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.

You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.

Start monitoring free Check another address

Independent measurement by HostTracker. Not affiliated with GitHub. Official updates are quoted from GitHub's public status page and remain GitHub's own words.