GitHub Accidentally Deletes Slack and Teams Subscriptions

GitHub had a rough afternoon: for nearly two hours, some people trying to use the site got told “nope” even when they were supposed to have access, and Slack and Microsoft Teams updates quietly got knocked offline. The company says the culprit was a newly switched-on setting that was later turned back off, and affected users can now retry or manually reconnect their chat subscriptions. In plain English: a switch got flipped, things got weird, and now people have to clean up the fallout.

But the real fireworks were in the comments, where the mood was less “these things happen” and more “what is going on over there?” One frustrated user called it “one bug after another,” while another roasted GitHub for not even getting the incident title right, branding the whole thing “utter degradation.” That set the tone: less sympathy, more public side-eye. The hottest conspiracy-flavored jab was a snarky “Probably agentic gone wrong again,” a wink toward fears that automated systems are being unleashed before they’re ready.

And yes, the jokes arrived right on schedule. Someone dropped the meme-like link isgithubcooked.com, which pretty much says everything about the vibe. Another commenter delivered the killer line: they were scared to ask how this happened because the answer might be “more disappointing.” Ouch. GitHub may have resolved the outage, but in the court of public opinion, the comments section was still holding a very loud retrial.