GitHub is once again down

GitHub stumbled again, and the developer internet went full soap opera. The company said multiple features—logins, pull requests (requests to merge code), Actions (automated tasks), webhooks, and even cloud dev rooms—were glitching before things started recovering and later resolved. That didn’t stop users from lighting up the comments: MattIPv4 reported “500” errors (that’s a server faceplant) when trying to push code and open pull requests. One fed‑up user yelled, “You have GOT to be kidding me,” while another dropped the Windows-style punchline that GitHub should be renamed to “Your Repository Needs To Restart To Apply Updates.”

Then came the heat. The spiciest theory blamed AI bloat: rvz argued this keeps happening “at least once a week,” pointing at Copilot and old Microsoft chatbot chaos as culprits and even joked about a prediction market paying out on weekly outages. Others mocked uptime bragging rights, saying GitHub isn’t “five nines” (near‑perfect reliability) but “one nine”—a brutal burn linked here for receipts: one nine. The vibe was a split between “corporate AI gone wild” and “it’s the internet, outages happen,” but everyone agreed on one thing: this hurts. When the world’s coding hub hiccups, work freezes and memes multiply. GitHub promises a root-cause report; the commenters promise more jokes—and they’ve already got them locked and loaded.