GitHub is down again, and this time it's hitting almost everything

Ripple effect: GitHub is experiencing a widespread outage this morning affecting many of the services developers rely on to build, review, and ship software, including its website, API, Pull Requests, Webhooks, and Copilot. The Microsoft-owned company acknowledged the incident at 13:40 UTC on Monday, saying it was investigating reports of performance problems across several GitHub services. Within minutes, API Requests and Actions were marked as degraded, followed by Webhooks, Issues, and Pull Requests. The disruption is substantial but not a complete GitHub blackout. GitHub reported error rates of roughly 20% across its web interface and API traffic, while archive downloads and raw repository content were failing at rates closer to 50%. Copilot joined the list of affected services, while GitHub Pages later began experiencing degraded performance. Git Operations, Packages, and Codespaces remained operational as of writing. The breadth of the outage illustrates how much GitHub has evolved beyond simply hosting source code. Actions powers automated testing and deployments, Webhooks connect GitHub to external services, Pull Requests underpin code review, and GitHub's APIs are embedded in countless development tools. Even when basic Git operations continue working, failures elsewhere can effectively halt an organization's software pipeline. The incident also arrives amid growing questions about GitHub's reliability. GitHub recorded eight incidents that degraded its services during July alone, following nine in May and six in June. Just over a week ago, GitHub Actions suffered a particularly lengthy disruption in which workflow runs failed or remained queued for hours. GitHub subsequently described that outage as unacceptable and said it was accelerating work to improve isolation and resiliency within Actions. The company is also continuing a broader infrastructure migration toward Azure intended to reduce shared failure points and make individual outages easier to contain. That makes Monday's broad failure particularly unfortunate. Rather than affecting one isolated component, the current incident has simultaneously touched APIs, authentication, collaboration tools, automation, and AI services. GitHub has not yet disclosed the root cause of this latest outage.