Incident with Actions and Pages

GitHub said it was hit by an incident affecting Actions and Pages, with updates escalating from “degraded performance” to a much messier reality: many automated jobs wouldn’t start, downloads were failing, and the company was scrambling to fix authentication problems. In plain English: people who rely on GitHub to build, test, and publish their code suddenly found a major part of their workflow wobbling at once.

But the real fireworks were in the community reaction, where patience was clearly in short supply. One commenter dragged out the receipts, pointing to GitHub’s status page and claiming the last 90 days looked more like “2 nines of uptime” than premium reliability. Another went straight for dark comedy, joking that maybe GitHub had somehow deleted its own Actions account because it was showing up as a “ghost” in pull request comments. Brutal.

Then came the classic outage side effect: the “should we leave?” crowd. One person used the downtime as an open casting call for alternatives, cheerfully recommending SourceHut for private code and Codeberg for public projects. Another piled on with the weary energy of someone who has seen this movie before: “down again today.” And in the most gloriously unhinged take of the thread, someone suggested Anthropic should just buy GitHub after buying bun and everything in between. Serious analysis? Not exactly. Peak comment-section theater? Absolutely.