GitHub addresses two recent incidents and says it aims to improve reliability amid AI growth, focusing on “availability first, then capacity, then new features”
or worse, bluesky.@theo:Github has been down for most of the day. I'm so tired of this. Never been so ready to move on. [image]Ahmet /@bruvimtired:we should all get together and finish building gitbruv. i promise it has better downtime than GitHub.Dmitrii Kovanikov /@chshersh:It's never been a better time to finally explore alternatives to git and different version control models like Pijul https://pijul.org/@peer_rich:i honestly think if you let people (somehow) migrate repos including stars; t
The GitHub BlogVlad Fedorov
Context & Ripple Effects
Recent coverage had already tied increased outages to OpenAI's nascent effort to build an alternative, while GitHub's leadership has moved into Microsoft's CoreAI organization. The latest response makes reliability a stated operating priority as GitHub expands AI-oriented products, including the Copilot desktop preview and agent-oriented canvases.
That matters because GitHub is both a core developer workflow service and a distribution point for its Copilot strategy: incidents now bear on confidence in the underlying platform as well as on adoption of new AI features.
First-order effects
GitHub is reordering engineering priorities toward service availability and capacity before feature delivery, which can slow the near-term pace of new product rollouts.
Developers and organizations reliant on GitHub gain a clearer reliability commitment, while GitHub must address outages under heightened scrutiny from users evaluating alternatives.
Second-order effects
A reliability-first posture raises the bar for GitHub's AI launches: new Copilot experiences must compete for infrastructure and operational attention with core-platform resilience.
Outages give credible users—especially large engineering organizations—more reason to assess alternative code-hosting or version-control options; OpenAI's reported internal alternative effort is an immediate example of that pressure.
Third-order effects
If AI-assisted development increases load and workflow centrality at code-hosting platforms, reliability and capacity become competitive differentiators rather than back-office concerns.
The likely structural trend is a migration of the developer-tooling bottleneck from feature availability to dependable operation of the shared platform and its AI agents; whether this leads to meaningful switching depends on how easily repositories and developer workflows can move.
The trend: AI is making developer platforms more operationally critical, pushing infrastructure reliability ahead of feature velocity as a basis for retaining users and enterprise workloads.
I don't work on reliability & scaling at GitHub, but the people who do aren't bad at their jobs. They're dealing with unprecedented scale from agents. It's easy to shit on GitHub from the outside if you're not in charge of 30X-ing capacity within a few months. Have some grace. [i…
@mariorod1 Also, your doc talks about transparency. How is April 23rd's pr history altering issue not represented as a blip somewhere on your status page? Is it because the only true downtime was for the ~230 orgs affected? [image]
@mariorod1 How can we trust you and what you say? I have no idea your tenure as CPO, but if you, the product officer, have a tenure longer than 6 months, I do not see how I can trust a word you say. Get a CEO, leave CoreAI, and maybe we can believe you
@MrAhmadAwais I'm sorry it's been a rocky stretch at GitHub. We know we need to do better. Today we published an update on two recent incidents including the April 27 affecting pull requests, issues, projects, and search-backed experiences. https://github.blog/...
I know i've said bad things on Github stability but honestly I'm sure they are doing an amazing job to keep the infra as stable as possible with this kind of growth
GitHub experiencing exponential growth fueled by AI. “By February 2026, it was clear that we needed to design for a future that requires 30X today's scale.” [image]
Being the foundation for millions of developers means our bar must be higher for availability, reliability, and security. I'm sorry it's been a rocky stretch at GitHub. We know we need to do better. Today we published an update on two recent incidents: one on April 23 involving
Is Github fucking with us again? Can't seem to deploy stuff to our cloud, and Github says we don't have any PRs in this repo, open or closed. The PRs simply are not there. I don't actually know if our last changes are in or not! [image]
Uhhhg. I totally agree...and also kinda don't want to kill Github. I'm quite worried if we throw out Github we'll end up with a balkanized hellscape of half-used Mastadonish fiefdoms with reddit mod vibes — or worse, bluesky.
i honestly think if you let people (somehow) migrate repos including stars; that would be huge haha so much of not moving off of github is this stupid stars vanity metric
One point I keep hearing from folks backing up their belief that agentic coding isn't raising productivity is that they don't see the flood of apps and features it ought to create. …
One big problem with GitHub availability is that they have long outgrown their shonky little data centre in Virginia; they started migrating to Azure properly (not just putting individual services on Azure) last October and they hope to do it in 12 months which is rebuilding the …
This reaffirms my fears, really. Crazy increase in what GitHub politically calls “agentic development”. I feel like that softens the reality a little and it just means a ton of vibe coding is happening. Existing developers using AI does not cause that kind of increase. github.…