Thousands of developers woke up to disruptions on April 23, 2026, as GitHub reported widespread outages, while the platform simultaneously faced growing scrutiny over its decision to pause new Copilot sign-ups. The back-to-back problems have put Microsoft’s developer platform under an uncomfortable spotlight — raising serious questions about reliability and the limits of AI-driven coding tools.
More than 2,000 users had reported problems with GitHub by 7:49 a.m. PT on April 23, according to Downdetector, the outage-tracking site that aggregates status reports from multiple sources. Most complaints centered on website access issues. GitHub’s own status page confirmed that Copilot, Codespaces, and Packages were experiencing degraded performance, and the company said it was continuing to investigate.
A Pattern of Outages Taking Shape
The April 23 disruption was not an isolated event. GitHub has publicly acknowledged a string of availability problems dating back to earlier this year, attributing the incidents to rapid growth, architectural coupling, and infrastructure limitations under heavy load.
The most significant disruptions occurred on February 2, February 9, and March 5, during a period of sharply accelerated usage growth that exposed weaknesses in the platform’s infrastructure. On March 3, for example, a bug in a caching mechanism caused mass cache expiration, and at the peak of that incident, roughly 40% of requests to github.com were failing. The February 9 outage was triggered by an overloaded database cluster responsible for authentication and user management — a failure that cascaded across tightly connected services.
GitHub acknowledged that it failed to meet its own reliability standards during this period. The company identified systemic issues, including insufficient isolation between components and inadequate mechanisms to protect the system under stress, meaning failures in one area could quickly ripple into repositories, APIs, and automation pipelines.
In response, GitHub has outlined a series of fixes: decoupling critical services, improving traffic management, enhancing load-shedding capabilities, and investing more deeply in system observability and incident response. The company also stressed the need for stricter change management practices to prevent configuration errors from snowballing.
GitHub Rebuilds Its Status Page for More Transparency
Amid the reliability concerns, GitHub announced a series of changes to how it communicates outages to users. The company is rolling out a new “Degraded Performance” state for its status page, sitting alongside the existing Partial Outage and Major Outage classifications to create a three-tier system that more accurately reflects the range of issues that can affect services.
GitHub is also publishing per-service uptime metrics and adding a dedicated “Copilot AI Model Providers” component to give clearer visibility into disruptions related to AI model availability. The company framed the changes as part of a broader commitment to transparency, acknowledging that GitHub has become critical infrastructure for developer teams worldwide.
Copilot Sign-Ups Paused as AI Costs Surge
While the platform was wrestling with stability, a separate crisis was brewing around GitHub Copilot’s economics. Effective April 20, GitHub paused new sign-ups for its Copilot Pro, Pro+, and Student plans and tightened usage limits across all individual tiers.
The reason, according to GitHub’s VP of product Joe Binder, is that agentic coding workflows — long-running, parallelized AI sessions where agents tackle complex problems autonomously over extended periods — are now routinely consuming more compute than users pay for in a single month. “It’s now common for a handful of requests to incur costs that exceed the plan price,” Binder wrote.
Following the pause, Copilot Free is the only plan still accepting new individual sign-ups. Existing users keep their current access, but GitHub has given no timeline for when subscriptions will reopen. Pro and Pro+ subscribers who contact support between April 20 and May 20 can cancel and receive a refund, with no charge for April.
The usage changes are structured to push heavier users toward the pricier Pro+ tier, priced at $39 per month, which now offers more than five times the limits of the $10-per-month Pro plan. Anthropic’s compute-intensive Opus models are also being removed from the Pro plan entirely, with the most capable models migrating exclusively to Pro+. Usage warnings are being added to VS Code and the Copilot CLI so developers can spot approaching limits before hitting them mid-workflow.
Context: Developers Growing Frustrated
The sign-up pause arrived at an already tense moment for GitHub’s relationship with its user base. Just weeks before, the platform faced significant backlash after developers discovered that Copilot had been inserting promotional “tips” — including an advertisement for a productivity app — into pull requests, in some cases making it appear as though the developer had written them. More than 11,000 pull requests were affected before the feature was disabled.
Broader developer sentiment, documented across social platforms, reflects mounting frustration with the frequency and impact of platform disruptions, particularly as modern development workflows have grown deeply dependent on always-available platforms. Independent tracking has documented continued service degradations into late March 2026, including issues affecting billing and other platform features.
Industry analysts say the Copilot pricing shift is structural, not temporary. Forrester vice president and principal analyst Charlie Dai noted that agent-driven coding is shifting workloads toward longer-running and parallel sessions that create higher and less predictable compute demand. “Cost structures built for lightweight assistance no longer hold,” Dai said.
Whether GitHub can stabilize its infrastructure and recalibrate its pricing fast enough to retain developers — before competitors like Cursor, Claude Code, and Codeium absorb frustrated users — is the pressing question now facing the platform.
