Glonce

GitHub outage degrades Pull Requests, Git Operations and Issues for about two hours

infrastructureThe Glonce editorsHacker News🔥62Glonce rating62Impact55Novelty30Relevance75Surprise40Players60Credibility95

GitHub's status page records an incident on Nov 4, 2026 that began at 09:49 UTC, when the company said it was investigating reports of degraded performance for Git Operations, Issues and Pull Requests. It was marked resolved at 11:50 UTC, about two hours later.

The scope grew during the first hours. At 09:50 UTC GitHub reported degraded performance for Actions. At 09:53 UTC it said Pull Requests was experiencing degraded availability, a stronger wording than the one used for the other services. At 10:38 UTC it described the problem as elevated errors and intermittent failures affecting GitHub, including Pull Requests, Git Operations and Issues, and said it would keep users updated as it worked toward mitigation. At 11:11 UTC API Requests was added to the list, again with degraded performance.

At 11:17 UTC GitHub said it was working on mitigating the errors and failures. It warned that some requests may fail or be delayed while it worked to restore service. Recovery was reported in two steps. At 11:30 UTC the degradation affecting API Requests, Git Operations, Issues and Pull Requests was reported as mitigated, with monitoring to ensure stability. At 11:43 UTC the same was said of the degradation affecting Actions. The incident was declared resolved at 11:50 UTC, with thanks to users for their patience and understanding.

The final status lists five affected components: Git Operations, API Requests, Issues, Pull Requests and Actions. GitHub says a detailed root cause analysis will be shared as soon as it is available. The status page gives no cause, no count of affected users or failed requests, and no date for that analysis.

Key facts

  • The incident ran from the first report at 09:49 UTC to resolution at 11:50 UTC on Nov 4, 2026.
  • Five components were listed as affected: Git Operations, API Requests, Issues, Pull Requests and Actions.
  • Pull Requests was described as having degraded availability; Actions and API Requests were described as having degraded performance.
  • Mitigation came in two steps: 11:30 UTC for API Requests, Git Operations, Issues and Pull Requests, and 11:43 UTC for Actions.
  • GitHub promises a detailed root cause analysis but gives no cause and no date for it.

Why it matters

GitHub is where code is pushed, reviewed and tracked, and this incident touched all of that at once: Git Operations, Pull Requests, Issues, API Requests and Actions. For about two hours GitHub reported degraded performance or availability across those services, with errors and intermittent failures that could make requests fail or arrive late.

Who it affects

The status page names the affected components, not the affected people. Anyone relying on GitHub for Git operations, pull requests, issues, API calls or Actions workflows could have seen errors or delays during the window. GitHub does not name regions or customer segments, and gives no count of affected users or repositories.

How to use it

There is nothing to install or configure. The practical point is that GitHub's status page carries timestamped updates for each stage of the incident, from the first investigation at 09:49 UTC to the resolution at 11:50 UTC. The detailed root cause analysis GitHub promised is the next thing to look for once it is published.

How solid is it

This is GitHub's own status page, so the timeline and the list of affected components are first-party. The page is the operator's account, though, and it is short: it gives no root cause, no error rates and no figures on failed requests. The cause stays unknown until the promised analysis appears.

Risks and caveats

The source does not say whether any data was lost. It also does not say whether the Actions problem and the Pull Requests, Git Operations and Issues problem shared a cause. Both resolution steps came with monitoring for stability, and no date is given for the root cause analysis. Until that analysis is out, any explanation of why this happened would be guesswork.

“Some requests may fail or be delayed while we work to restore service.”

— GitHub status page, Nov 4, 2026, 11:17 UTC