GitHub reports elevated errors hitting pull requests, Git operations, issues and Actions

What happened

GitHub is working through an active incident that is disrupting several of the platform's core services. According to GitHub's status page, the incident covers four systems: Git Operations, Issues, Pull Requests and Actions.

In the most recent update, posted at 10:38 UTC on November 4, GitHub said it was looking into a rise in error rates and intermittent failures across the site, including pull requests, Git operations and issues, and that it would keep users informed as it worked toward a fix. The incident drew wide attention after a link to the status page reached the front page of Hacker News.

How the incident unfolded

The status page shows a picture that worsened over the course of roughly an hour:

• At 09:49 UTC, GitHub first acknowledged reports of slow performance for Git operations, issues and pull requests and opened an investigation.
• At 09:50 UTC, one minute later, the company reported that Actions was also running with degraded performance.
• At 09:53 UTC, the wording for pull requests was changed to degraded availability, indicating the feature was not reliably reachable rather than merely slow.
• At 10:38 UTC, GitHub broadened its description to elevated errors and intermittent failures affecting the platform as a whole, while it continued working toward mitigation.

At the time of writing, no resolution had been announced and the company had not offered any explanation of the underlying cause.

What is affected

Each of the four services named in the incident sits at the centre of how teams build software on GitHub:

• Git Operations covers the version-control traffic between developers and GitHub's servers, meaning the clones, fetches and pushes that move code back and forth.
• Pull Requests are the mechanism teams use to review, discuss and merge changes, so reduced availability stalls code review itself.
• Issues are the main bug-tracking and planning surface attached to repositories.
• Actions is GitHub's continuous integration and delivery platform, which many projects rely on to build, test and deploy code automatically whenever a change lands.

A combination of failures across these four areas is broader than a typical single-service hiccup, because it touches authoring, review, tracking and automation at the same time.

Why it matters

When Git operations fail, work does not just slow down locally: code that cannot be pushed or fetched cannot be shared, reviewed or shipped. A pull request outage blocks the review step that most teams gate their merges behind, and an Actions degradation can freeze CI pipelines, leaving engineers without the automated test and build results they normally depend on before deploying. For organisations that have built their entire workflow on GitHub, an incident spanning all four services effectively interrupts the software delivery process end to end.

The event is also a reminder of how concentrated development infrastructure has become. GitHub hosts a very large share of the world's open-source and private code, so even partial failures ripple outward to dependent projects, mirrored repositories and third-party tooling within minutes, which is presumably why the incident quickly surfaced on Hacker News's front page.

For now, the practical guidance is straightforward: treat build results and Git activity as unreliable until GitHub confirms mitigation, and follow the official status page for updates rather than drawing conclusions from partial or intermittent failures. No estimate of a fix time has been given.