GitHub appears to be struggling with measly three nines availability
GitHub's availability is plummeting, with some services struggling to hit even two nines, much less the promised three. This decline is attributed by many to Microsoft's ownership, a push for AI features, and the migration to Azure, sparking widespread concern and frustration among developers reliant on the platform.
The Lowdown
GitHub, a foundational platform for software development, is reportedly facing significant challenges with its service availability, often failing to meet even a "three nines" (99.9%) uptime standard across its various offerings. Recent incidents have highlighted a trend of instability, prompting questions about its operational integrity.
- In early February 2026, GitHub experienced multiple outages impacting critical services such as Actions, pull requests, notifications, and Copilot.
- The company's status page has been criticized for making it harder to ascertain overall platform reliability, though unofficial trackers reveal periods of uptime falling below 90% in 2025.
- The article also touches on related controversies, including GitHub's consideration of an AI "kill switch" for pull requests, a retracted plan to charge for self-hosted runners, and the departure of projects like Zig due to Microsoft's AI focus.
- Despite a 99.9% uptime SLA for Enterprise Cloud customers, individual GitHub services frequently fall short, leading to operational challenges for users.
- The broader implication is a growing necessity for organizations to build resilience against potential downtime of essential cloud-based development tools.
The ongoing reliability issues raise concerns within the developer community about GitHub's strategic direction under Microsoft and the balance between rapid feature development (especially AI) and maintaining a stable, dependable core service.
The Gossip
The Perilous Plunge in Performance
Commenters extensively debate GitHub's actual availability. While the article cites "three nines," many argue that real-world experience, often backed by unofficial status pages, reveals significantly worse reliability, sometimes falling to a single nine for critical services. There's a strong sentiment that the official metrics may be misleading, particularly when combining varied service uptimes.
Microsoft's Midas Touch (or Lack Thereof)
A dominant theme is the attribution of GitHub's declining reliability and perceived strategic missteps to its acquisition by Microsoft. Many commenters believe Microsoft's corporate priorities, such as the mandated Azure migration and heavy investment in AI (like Copilot), are detrimental to GitHub's core stability and user experience, drawing comparisons to the 'enshittification' of other Microsoft-acquired products like Skype.
Feature Creep and Core Decay
Many in the community feel GitHub's relentless pursuit of new features, particularly AI-driven ones and a shift to React-based frontends, has come at the expense of maintaining the reliability and performance of its foundational services. Concerns also extend to the security vulnerabilities inherent in GitHub Actions, with some calling it "Swiss cheese" due to flaws like mutable references and supply chain risks.
Beyond the 'Nines': Impact and Alternatives
The discussion often shifts to the tangible impact of GitHub's instability on developer productivity, especially for enterprise users for whom downtime translates directly to lost work. This leads to a conversation about the practical limitations of relying heavily on a single, centralized platform and a growing interest in exploring self-hosting or decentralized alternatives to mitigate risk and regain control over critical infrastructure.