GitHub faces survival fight

GitHub is under pressure at the same time Microsoft is making it more central to its AI software stack. The Verge reported on May 21 that the Microsoft-owned coding platform is dealing with outages, security issues and a talent exodus as competition in AI coding tools intensifies. Microsoft has tied GitHub more closely to its CoreAI organization, the internal group created in January 2025 to build the company’s end-to-end AI platform and tools. Microsoft said that group would build out GitHub Copilot under Jay Parikh, its executive vice president of CoreAI – Platform and Tools. April’s incident record shows why reliability has become part of the story. (theverge.com) GitHub said in a May 14 availability report that it experienced 10 incidents in April that caused degraded performance across services. ### Why does GitHub’s stability matter more now? Microsoft told investors on April 29 that nearly 140,000 organizations now use GitHub Copilot and that enterprise subscribers have nearly tripled year over year. (blogs.microsoft.com) That makes GitHub more than a code-hosting property inside Microsoft’s AI strategy. Satya Nadella said on April 29 that Microsoft was focused on delivering “cloud and AI infrastructure and solutions” for the “agentic computing era.” GitHub sits inside that product push because Copilot is one of Microsoft’s main developer-facing AI products. (github.blog) ### Which outages best capture the problem? GitHub said an April 1 code-search incident left 100% of search queries failing for a period after an infrastructure upgrade to the messaging system behind code search triggered coordination failures between internal services. (microsoft.com) Full recovery took until 23:45 UTC that day, according to the company. (news.microsoft.com) GitHub’s status history shows another notable incident on May 15, when a planned failover in GitHub Actions led to routing problems in a core dependency. At peak impact, 42% of Actions runs failed, and GitHub said downstream services including GitHub Pages and Copilot cloud services were also affected. GitHub said on April 28 that it had begun a plan in October 2025 to increase capacity by 10 times, then concluded by February 2026 that it needed to design for 30 times today’s scale because “agentic development workflows” had accelerated sharply since the second half of December 2025. (github.blog) ### What has GitHub itself said is going wrong? Vlad Fedorov, writing on GitHub’s blog on April 28, said the company was dealing with a system where one pull request can touch storage, mergeability checks, branch protection, Actions, search, notifications, permissions, webhooks, APIs, caches and databases. (githubstatus.com) He said small inefficiencies were compounding at high scale and that GitHub’s priorities were “availability first, then capacity, then new features.” (github.blog) GitHub said it was reducing unnecessary work, improving caching, removing single points of failure, isolating critical services such as git and GitHub Actions, and moving performance-sensitive code out of its Ruby monolith into Go. It also said its migration to Azure had helped it add compute. ### Where does the leadership issue fit in? Thomas Dohmke said in August 2025 that he would step down as GitHub chief by the end of 2025, and Microsoft said GitHub would operate as part of CoreAI rather than under a standalone replacement chief executive. (github.blog) CNBC and GeekWire reported at the time that GitHub leadership would report into Jay Parikh. The Verge’s May 21 report said GitHub is also dealing with internal churn and departures as Microsoft pushes deeper integration with its AI organization. That account is partly consistent with Microsoft’s earlier structural decision to fold GitHub into CoreAI after Dohmke’s exit. ### What should readers watch next? GitHub’s public status page says it will publish root-cause analyses for recent incidents, including a May 20 Actions degradation. (cnbc.com) The company has also started monthly availability reports, which now serve as its main public accounting of service reliability. Microsoft’s next test will come as GitHub supports more Copilot usage inside enterprises already adopting the product at scale. (theverge.com) The next public checkpoint is likely Microsoft’s next earnings update and GitHub’s next monthly availability report. (microsoft.com) (githubstatus.com)