Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • It’s ironic that the SCM that 2026 software engineers landed on, is one with a complicated distributed usage model and is slow/down because of a centralised service
  • Is GitHub Cooked? Decidedly yes.

    Migrating to something else has been raised as a concern during every engagement with clients and prospective clients in the past year.

    "Do you use GitHub?"

    "Yes though we'd like to move to something else, we just don't know what yet."

    As soon as the next big thing shows up, they're done. And they know it.

  • If backend GitHub services are anything like GHES then I’m surprised it even managed to scale this much.
  • I feel for the team having to deal with these problems at github today. Its also beyond me how those in charge for years wouldn't have seen this coming.

    Github was bought by Microsoft, whether they wanted to acknowledge that internally or not. Microsoft went deep on LLMs, and specifically on LLMs for coding use cases. They must have recognized that LLM generated code and PRs would effectively DDoS GitHub.

    I can only assume they simply didn't care, likely driven by greed.

  • > "GitHub has had 1125 incidents since February 2016, implying a monthly incident rate of 24"

    1125 incidents / 126 months ≈ 8.9 incidents per month, not 24

    still terrible, but why such an obvious error in the first sentence...

  • Given that the outages are caused by record traffic, so far they are only cooked in the Yogi Berra sense of “Nobody goes there anymore, it’s too crowded”
  • Near the end of the 8.5 years that I worked at GitHub as an enterprise support engineer, I asked in an all hands if a "GitHub Classic" product had been considered. Much like World of Warcraft Classic, I imagined it would be a rewrite focused on matching the simpler feature set of the past.

    I was basically given the same response that blizzard gave that question; "you think you want that but you don't".

  • I think we need to have a little more sympathy for GitHub. You could justify the jabs when we could all blame any outage on the migration to Azure, but then they shared numbers around the scale they're dealing with now that everyone is constantly building and pushing with AI.

    I think it's commendable that they're not limiting access to the site or (intentionally) throttling newcomers. Yes, they need to get this figured out, but a little sympathy goes a long way. I personally wish them the best and hope their on-call people can go back to getting normal amounts of sleep soon.

Explore Birbla archives

GitHub Outage Tracker: Is GitHub Cooked? · Birbla