2 stories
Users reported failures across Microsoft services and pointed to GitHub’s long-running move toward Azure; neither observation alone established the root cause.
A second explanation was load: commenters cited rapid growth in commits and new accounts as AI-assisted development turns GitHub into a much busier system.
The top HN threads: facts from the discussions, both sides, insider voices. Email, Telegram, or RSS.
The kicker isn't 14 billion commits. It's that those are agent check-ins, not features shipped — agents now write to GitHub while they think, not after a human has.
One commenter recalls GitHub's founder telling a Microsoft exec years ago that Azure's virtual disks weren't fast enough on IOPS to host GitHub.
And the article making this claim is itself an AI-generated, mostly-empty React page from a self-described one-person, vibecoded site.
