GitHub Actions and Pages are experiencing degraded availability
GitHub Actions and Pages suffered significant degraded availability, disrupting development workflows for countless users. This incident sparked widespread frustration among developers, many of whom are increasingly reliant on these services for critical operations. The Hacker News community debated GitHub's declining reliability, questioning its management and the impact of frequent outages on productivity.
The Lowdown
On August 6, 2026, GitHub experienced a major incident impacting the availability of its Actions and Pages services. The incident led to workflow failures, delayed job runs, and errors in the Actions API, affecting users including those running migrations with GitHub Enterprise Importer. Despite engineers applying several mitigations, the issues persisted for hours.
- Actions Impact: Workflow runs failed or were significantly delayed, and requests to the Actions API returned errors. Some users also experienced unexpected rate limiting.
- Pages Impact: GitHub Pages initially reported degraded performance, which later resolved but then resurfaced, raising questions about its underlying dependencies.
- Mitigation Efforts: GitHub engineers identified the source of the disruption and were actively working on fixes and recovery throughout the incident.
- Duration: The incident spanned several hours during a critical workday, causing significant disruption.
The repeated updates from GitHub's status page indicated a prolonged struggle to restore full service, highlighting ongoing reliability challenges for their core developer tools.
The Gossip
Declining Dependability: GitHub's Faltering Fortunes
Many users expressed exasperation over the frequent and prolonged outages affecting GitHub Actions and Pages, questioning the platform's reliability and perceived decline in quality since the Microsoft acquisition. Comments lamented the routine nature of these incidents, suggesting GitHub no longer operates as a "serious company" and speculating on its tarnished reputation, with some humorously suggesting GitHub is running on "zero nines" of uptime.
Operational Obstacles and Options
The outage caused significant disruption to developer workflows, preventing PR merges and delaying CI/CD pipelines. Users voiced frustration at the practical impact, such as self-hosted runners being affected by API issues, and the lack of reliable alternatives for specific needs like free cloud-hosted Windows runners. The discussion also included the increasing argument against "dogfooding" critical paths with GitHub Actions, with some advocating for self-hosting or switching to competitors like GitLab.
Puzzling Performance and Presumed Causes
Commenters speculated on the underlying causes of the recurring issues, often pointing to GitHub's intense focus on AI/Copilot features or perceived neglect by Microsoft of core infrastructure. There was bewilderment over how static services like GitHub Pages could suffer degraded performance, with some connecting it to Actions dependencies. Users also criticized the vague error messages provided during outages and the inability to pay for priority access as signs of broader systemic issues, hinting at a lack of incentive for improvement.