What’s Gone Wrong at GitHub?  🔗 **Source:** [What’s Gone Wrong at GitHub?](https://leaddev.com/software-quality/whats-gone-wrong-at-github) > [!note]+ Document Notes > tags: #github #reliability #infrastructure #ai-automation #microsoft > author: Charles Humble > source: LeadDev > reference: https://leaddev.com/software-quality/whats-gone-wrong-at-github > date created: 2024-12-19 09:30 > > # 🏷️ Title: What's gone wrong at GitHub? > <!-- deep-read:sections start --> ## 🧰 Action Inbox - [H1] Investigate GitHub alternatives for critical infrastructure projects — platform reliability assessment #infrastructure - [H2] Review AI workflow scaling impact on CI/CD systems — capacity planning #ai-automation - [H3] Implement incident response improvements based on GitHub's transparency practices — post-mortem analysis #reliability ## 🧭 Table of Contents - [[#📝 Summary]] - [[#📖 Main Content]] - [[#🗒️ Notes]] - [[#📚 References]] - [[#🗣️ Paraphrase]] - [[#📰 Newsletter]] - [[#✅ Action Items]] - [[#🧪 Hypotheses]] - [[#📊 Methodology]] - [[#❓ Questions]] - [[#🔮 Future Research]] - [[#💡 Implications]] - [[#🧠 Learning Styles Assessment]] - [[#📊 Accessibility Assessment]] - [[#🌍 DEIB Assessment]] - [[#✅ Logical Validity]] - [[#🛡️ DARVO Analysis]] - [[#🎯 Conclusion]] ### 🔗 References - [GitHub Status Page](https://www.githubstatus.com) - [Unofficial GitHub Status Tracker by Marek Šuppa](https://github-status.mareksu.com) ## 📝 Summary - GitHub's reliability has dramatically deteriorated, with incidents increasing from 119 in 2024 to 257 between May 2025-April 2026 - AI-driven development workflows are overwhelming GitHub's infrastructure, requiring 30X capacity scaling - High-profile users including Zig programming language and Mitchell Hashimoto are migrating away from the platform - Microsoft's integration of GitHub into CoreAI organization has eliminated independent leadership - GitHub has shifted to "availability first" priorities but faces ongoing competitive pressure to ship Copilot features ## 📖 Main Content GitHub faces an unprecedented reliability crisis driven by the explosive growth of AI-assisted development workflows. The platform that once epitomized reliable developer infrastructure now struggles with weekly major outages and visible user exodus. The scale of the problem is stark. From 119 incidents in 2024, GitHub logged 257 separate incidents between May 2025 and April 2026, with 48 classified as major outages. An unofficial tracker suggests actual uptime has dropped to 84.88% over 90 days, well below the industry standard 99.9%. GitHub CTO Vlad Fedorov acknowledges the platform wasn't built for current scale, describing explosive growth in "agentic development workflows" since December 2025. Repository creation, pull requests, API usage, and automation workloads are all growing rapidly as AI agents generate code at machine speed. The irony is inescapable: GitHub Copilot helped create the AI coding market, and now GitHub buckles under the weight of AI-generated activity it helped enable. Microsoft's strategic focus on Copilot across its software suite creates commercial pressure competing with reliability investments. Organizational changes compound technical challenges. When CEO Thomas Dohmke stepped down in August 2025, Microsoft folded GitHub directly into its CoreAI organization, eliminating independent advocacy for the platform's needs. High-profile departures signal eroding confidence. The Zig programming language migrated to Codeberg citing "rotted" engineering culture. Mitchell Hashimoto documented daily GitHub outages blocking his work before moving his 52,000-star Ghostty project off the platform. ## 🗒️ Notes #### ⏱️ [00:00](https://leaddev.com/software-quality/whats-gone-wrong-at-github#intro) — [H1] GitHub's reliability crisis emerges - Key idea: Platform reliability has dramatically deteriorated over the past year - Evidence: "GitHub logged 119 service incidents in 2024, then 257 between May 2025-April 2026" #### ⏱️ [02:30](https://leaddev.com/software-quality/whats-gone-wrong-at-github#statistics) — [H2] Incident statistics reveal scope of problems - Key idea: Weekly major outages with Actions CI/CD system most affected - Evidence: "48 major outages in 12 months, roughly one significant disruption per week" #### ⏱️ [05:15](https://leaddev.com/software-quality/whats-gone-wrong-at-github#uptime) — [H3] Uptime drops below industry standards - Key idea: Actual measured uptime significantly worse than official figures - Evidence: "Unofficial tracker shows 84.88% uptime vs industry standard 99.9%" #### ⏱️ [07:45](https://leaddev.com/software-quality/whats-gone-wrong-at-github#exodus) — [H1] High-profile users abandon platform - Key idea: Reliability issues driving away major projects and developers - Evidence: "Zig programming language migrated to Codeberg citing 'rotted' engineering culture" #### ⏱️ [10:20](https://leaddev.com/software-quality/whats-gone-wrong-at-github#hashimoto) — [H2] Mitchell Hashimoto documents daily impact - Key idea: Daily outages preventing productive work for serious developers - Evidence: "Almost every day had an X marking GitHub outage impact on work" #### ⏱️ [13:00](https://leaddev.com/software-quality/whats-gone-wrong-at-github#ai-scale) — [H1] AI workflows overwhelm infrastructure - Key idea: Platform wasn't designed for machine-speed AI agent activity - Evidence: "Need to design for future requiring 30X today's scale due to agentic workflows" #### ⏱️ [16:30](https://leaddev.com/software-quality/whats-gone-wrong-at-github#copilot-irony) — [H2] GitHub victim of its own AI success - Key idea: Copilot helped create the AI coding boom now overwhelming the platform - Evidence: "GitHub actively evangelized AI code generation, now buckling under AI-generated activity" #### ⏱️ [19:15](https://leaddev.com/software-quality/whats-gone-wrong-at-github#microsoft-integration) — [H3] Microsoft integration eliminates independence - Key idea: GitHub lost dedicated leadership when folded into CoreAI organization - Evidence: "No longer has anyone at the top whose job is solely to be GitHub's advocate" #### ⏱️ [22:00](https://leaddev.com/software-quality/whats-gone-wrong-at-github#technical-incidents) — [H2] Poor architectural practices compound scaling issues - Key idea: April incidents show engineering problems beyond just AI scaling - Evidence: "Incomplete feature flag caused 2,092 pull requests across 658 repositories to be affected" #### ⏱️ [25:30](https://leaddev.com/software-quality/whats-gone-wrong-at-github#elasticsearch) — [H3] Infrastructure buckling under botnet attacks - Key idea: Core search infrastructure failing under unexpected load patterns - Evidence: "Elasticsearch cluster buckled under botnet attack, causing widespread UI disruption" #### ⏱️ [28:45](https://leaddev.com/software-quality/whats-gone-wrong-at-github#maintainer-focus) — [H2] Platform missing key maintainer visibility features - Key idea: GitHub replacement should focus on project relationship visibility - Evidence: "Nobody is addressing visibility into relationships between projects" #### ⏱️ [31:20](https://leaddev.com/software-quality/whats-gone-wrong-at-github#unique-position) — [H1] GitHub's central role creates unique scaling challenges - Key idea: Unlike other platforms, GitHub sits at center of agentic workflows - Evidence: "PyPI, npm, GitLab handling growth without comparable public meltdowns" #### ⏱️ [34:00](https://leaddev.com/software-quality/whats-gone-wrong-at-github#priorities) — [H3] Availability-first mandate faces commercial pressure - Key idea: Right priorities declared but competitive pressure to ship Copilot features remains - Evidence: "Availability first, capacity second, new features third - whether organization can hold to it remains to be seen" ## 📚 References - [GitHub Status Page](https://www.githubstatus.com) - [Unofficial GitHub Status Tracker](https://github-status.mareksu.com) - [Zig Programming Language Migration Announcement](https://codeberg.org/zig) - [Mitchell Hashimoto's GitHub Exodus Post](https://mitchellh.com/github) ## 🗣️ Paraphrase - GitHub's reliability has collapsed over the past year, with major outages increasing from roughly 2 per month to over 4 per month, driving away high-profile users who can no longer rely on the platform for serious development work - The explosion of AI-powered development tools has created machine-speed workflows that overwhelm GitHub's infrastructure, ironically making the platform a victim of the AI coding revolution it helped create through Copilot - Microsoft's integration of GitHub into its CoreAI organization eliminated independent leadership advocacy, while commercial pressure to expand Copilot features competes with the engineering resources needed for reliability improvements ## 📰 Newsletter **GitHub's Reliability Crisis: What It Means for WordPress Development** GitHub's dramatic reliability decline - from 119 incidents in 2024 to 257 in the past 12 months - highlights critical infrastructure risks for WordPress development teams. With uptime dropping to 84.88% and weekly major outages affecting CI/CD workflows, many projects are reconsidering platform dependencies. **Key Implications:** - **CI/CD Disruption**: GitHub Actions outages freeze entire development workflows, particularly impacting WordPress plugin and theme development pipelines - **AI Workflow Scaling**: The explosion of AI-assisted coding is overwhelming platforms not designed for machine-speed development - **Infrastructure Planning**: High-profile migrations like Zig to Codeberg signal growing demand for reliable alternatives **WordPress-Specific Considerations:** WordPress.org's infrastructure relies heavily on GitHub for core development, plugin reviews, and community contributions. Teams should evaluate backup workflows and consider diversifying critical development infrastructure. **Actionable Steps:** - Audit GitHub dependencies in your WordPress development workflow - Implement local development environments that don't require constant GitHub connectivity - Consider GitLab, Codeberg, or self-hosted alternatives for mission-critical projects - Document incident response procedures for extended GitHub outages The broader lesson: even essential developer infrastructure can become unreliable when scaling challenges meet commercial pressures. WordPress teams should build resilience into their development processes. Resources: [WordPress Core Trac](https://core.trac.wordpress.org/), [WP-CLI](https://wp-cli.org/), [Local Development Guide](https://developer.wordpress.org/advanced-administration/before-install/howto-install/) ## ✅ Action Items #### DevRel - Developer advocacy: Document GitHub alternatives in developer resources, create migration guides, track community sentiment on platform reliability - Education: Workshop on development workflow resilience, CI/CD backup strategies, local development best practices - Developer experience: Audit documentation dependencies on GitHub, implement mirrors for critical resources - Developer marketing: Thought leadership on infrastructure reliability, case studies of successful platform migrations - Community management: Monitor discussions about GitHub reliability, facilitate conversations about alternatives #### OSPO - Policy & Governance: Review vendor dependency policies, establish infrastructure diversity requirements - License Compliance: Audit tools affected by GitHub outages, implement offline compliance checking - Security Management: Assess security implications of GitHub alternatives, review supply chain risk from platform concentration - Software Inventory: Document GitHub dependencies across organization, identify single points of failure - Developer Support: Provide training on alternative platforms, tooling for multi-platform workflows - Community Engagement: Engage with projects considering GitHub migration, support infrastructure diversity initiatives - Strategic Alignment: Develop infrastructure resilience KPIs, report on vendor concentration risks #### Community - Maintainers: Guidance on platform migration decisions, backup hosting strategies, workflow continuity planning - Contributors: Training on multiple platforms, documentation for accessing projects during outages - Sponsors: Funding for infrastructure diversity, support for projects migrating from GitHub - Ecosystem: Cross-platform coordination protocols, shared infrastructure reliability monitoring #### WordPress - Core: Evaluate GitHub dependencies for core development, implement backup workflows for critical processes - Core Performance: Monitor impact of GitHub outages on performance testing workflows - Core AI: Assess how AI development workflows impact infrastructure scaling, implement responsible AI practices - Core Program Team: Develop contingency plans for GitHub outages affecting release cycles - Mobile: Backup CI/CD strategies for app development, alternative code hosting evaluation - Playground: Mirror critical repositories, implement offline development capabilities - Community: Document alternative platforms for meetup coordination, backup communication channels - Training: Create lessons on development workflow resilience, platform diversity best practices - Marketing: Communicate WordPress infrastructure reliability, differentiate from GitHub dependency - Support: Prepare documentation for accessing WordPress resources during GitHub outages - Design: Ensure design systems remain accessible during platform outages - Documentation: Mirror critical documentation, implement multi-platform publishing - Photos: Backup workflows for photo contribution systems - TV: Alternative hosting for video content repositories - Polyglots: Ensure translation workflows remain functional during outages - Accessibility: Test accessibility tools across multiple platforms - Meta: Reduce .org dependencies on GitHub infrastructure, implement redundancy - CLI: Ensure WP-CLI distribution doesn't depend solely on GitHub - Hosting: Coordinate with hosts on development workflow continuity - Tide: Implement backup systems for plugin analysis workflows - Openverse: Diversify infrastructure for content ingestion systems - Themes: Backup review processes independent of GitHub - Plugins: Alternative hosting for plugin development resources #### The WPCC - Programs: Fund infrastructure diversity initiatives, support developers affected by platform migrations - Projects: Governance guidance for platform selection decisions, migration assistance grants - Funding: Support reliable infrastructure alternatives, matched grants for community hosting #### FAIR - Technical independence: Reduce single vendor dependencies, implement infrastructure diversity - Policies: Platform vendor evaluation criteria, infrastructure resilience requirements - Governance artifacts: Vendor dependency disclosures, infrastructure continuity plans ## 🧪 Hypotheses - GitHub's reliability issues will accelerate adoption of decentralized development workflows and alternative platforms within the next 24 months - Organizations heavily dependent on GitHub Actions will implement multi-cloud CI/CD strategies to mitigate outage risks - AI-driven development scaling challenges will force major platforms to redesign architectures for machine-speed workflows - Microsoft's prioritization of Copilot revenue over GitHub reliability will continue driving high-value users to alternatives ### 📊 Methodology - Study design: Track GitHub incident frequency and user migration patterns across open source projects over 18-month period - Data sources: GitHub status pages, alternative platform adoption metrics, developer survey data on platform switching - Experiments: Compare development workflow resilience across GitHub-dependent vs diversified infrastructure setups ### ❓ Questions - How quickly can major WordPress projects migrate critical infrastructure away from GitHub if reliability continues declining? - What infrastructure redundancy strategies should WordPress.org implement to maintain core development velocity during extended GitHub outages? - How will AI agent workflows scale across the broader developer infrastructure ecosystem beyond GitHub? ### 🔮 Future Research - Long-term sustainability models for developer infrastructure platforms under AI scaling pressure - Decentralized development workflow architectures that reduce single platform dependencies - Economic models for funding reliable open source infrastructure alternatives ### 💡 Implications - Practice: Development teams need infrastructure diversity strategies and offline workflow capabilities - Policy: Organizations should establish vendor dependency limits and infrastructure resilience requirements - Security: Platform concentration creates supply chain risks requiring redundancy and backup strategies - Education: Developers need training on multi-platform workflows and infrastructure resilience planning - Funding: Investment needed in reliable infrastructure alternatives and platform diversity initiatives ### 🧠 Learning Styles Assessment Reading level estimate: 12th Grade (Flesch-Kincaid) #### 👀 Visual learners - Present: Timeline of GitHub incidents, uptime statistics, user migration flow charts - Improve: Infrastructure architecture diagrams, capacity scaling visualizations, incident impact maps #### 🔊 Aural learners - Present: Article available in text format for screen readers - Improve: Podcast discussion of infrastructure reliability, audio case studies of platform migrations #### 🗣️ Verbal learners - Present: Clear definitions of technical terms, analogies to physical infrastructure - Improve: Narrative examples of outage impacts, conversational explanations of scaling challenges #### 🧩 Kinesthetic learners - Present: Step-by-step incident descriptions, actionable migration guidance - Improve: Hands-on labs for setting up alternative platforms, workflow redundancy checklists #### 🧠 Logical learners - Present: Statistical analysis of incident trends, cause-and-effect relationships - Improve: Decision trees for platform selection, cost-benefit analysis frameworks #### <!-- deep-read:sections end --> 📄 **Full text:** ![[Full Document Contents/Articles/What’s Gone Wrong at GitHub.md|What’s Gone Wrong at GitHub? by leaddev.com]] ## Highlights - In December 2025, the [Zig programming language](https://leaddev.com/career-development/why-zig-one-hottest-programming-languages-learn) project [migrated to Codeberg,](https://leaddev.com/ai/why-zig-is-moving-on-from-github) a nonprofit alternative, citing not just bugs but what its maintainers called a “rotted” engineering culture. They pointed to a critical bug in GitHub Actions that had hung build servers indefinitely. Having been reported in April 2025, it was fixed months later. ([View Highlight](https://read.readwise.io/read/01kr1ktf14e73mgy9h8hy6f5gb)) - Tags: 👻 ai highlighted