Outage Sphere
Last checked

Is GitHub down? / Nov 2026

GitHub outage of 4 Nov 2026: what happened and how long it lasted

GitHub’s outage of 4 Nov 2026 was open on GitHub’s status page for 2 h, from 09:49 to 11:50 UTC, and affected Git Operations, API Requests, Issues and 2 more.

Last changed . Last checked . Source: stspg.io/18blsgwnbyy6.

GitHub's updatesOldest first, in the vendor's own words. Times are UTC.

  1. We are investigating reports of degraded performance for Git Operations, Issues and Pull Requests

  2. Actions is experiencing degraded performance. We are continuing to investigate.

  3. Pull Requests is experiencing degraded availability. We are continuing to investigate.

  4. We're investigating elevated errors and intermittent failures affecting GitHub including Pull Requests, Git Operations, and Issues. We'll continue to keep users updated as we work toward mitigation.

  5. API Requests is experiencing degraded performance. We are continuing to investigate.

  6. We're currently working on mitigating elevated errors and intermittent failures affecting GitHub, including Pull Requests, Git Operations, and Issues. Some requests may fail or be delayed while we work to restore service. We'll provide another update as more information becomes available.

  7. The degradation affecting API Requests, Git Operations, Issues and Pull Requests has been mitigated. We are monitoring to ensure stability.

  8. The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

  9. n November 4, 2026, between 09:35 UTC and 11:43 UTC, customers experienced intermittent errors and timeouts across GitHub.com, primarily on actions that write data. At peak, about 20% of pull request write operations (such as merging, commenting, and reviewing) failed, along with about 10% of issue creates and edits and 10–15% of project item edits. Git pushes over SSH, REST and GraphQL API requests, code scanning uploads, releases, and package operations were also affected, and about 1% of Actions runs were delayed by more than five minutes or failed to start. Overall, nearly 4% of all requests to GitHub.com failed at the worst point. Reads were largely unaffected, and retrying a failed action a short time later usually succeeded. The incident was triggered by a burst of concurrent updates to the same database record, which tied up all available connections to one of our primary…

CauseIn GitHub's words only

The incident was triggered by a burst of concurrent updates to the same database record, which tied up all available connections to one of our primary databases.

GitHub has not published a post-mortem on its incident page.

Earlier at GitHub

Is GitHub down right now? This page as JSON.