8 ms·
3 outages in 3 months straight according to their own status history. https://www.githubstatus.com/history https://www.githubstatus.com/history
by jbpadgett 8mo ago
3 outages in 3 months straight according to their own status history.
https://www.githubstatus.com/history https://www.githubstatus.com/history
- hnthrowaway0315 8mo agoI wonder who left the team recently. Must be someone bagged with shadow knowledge. Or maybe they send devops/devs work to another continent.
- perdomon 8mo agoI think it's more likely the introduction of the ability to say "fix this for me" to your LLM + "lgtm" PR reviews. That or MS doing their usual thing to acquired products.
- arccy 8mo agonah, they're just showing us how to vibecode your way to success
- hnthrowaway0315 8mo agoIf the $$$ they saved > the $$$ they lose then yeah it is a success. Business only cares about $$$.
- collingreen 8mo agoDefinitely. The devil is in the details though since it's so damn hard to quantify the $$$ lost when you have a large opinionated customer base that holds tremendous grudges. Doubly so when it's a subscription service with effectively unlimited lifetime for happy accounts. Business by spreadsheet is super hard for this reason - if you try to charge the maximum you can before people get angry and leave then you're a tiny outage/issue/controversy/breach from tipping over the wrong side of that line.
- hnthrowaway0315 8mo agoYeah, but who cares about long-term? In the long term we are all dead. CEO only needs to be good for 5-10 max years, pop up stock prices and get applause every where and called as the smartest guy in the world.
- jsheard 8mo agoThey're in the process of moving from "legacy" infra to Azure, so there's a ton of churn happening behind the scenes. That's probably why things keep exploding.
- hnthrowaway0315 8mo agoAre they just going to tough through the process and whatever...
- estimator7292 8mo agoI don't know jack about shit here, but genuinely: why migrate a live production system piecewise? Wouldn't it be far more sane to start building a shadow copy on Azure and let that blow up in isolation while real users keep using the real service on """legacy""" systems that still work?
- throwway120385 8mo agoWhy would you avoid a perfect opportunity to test a bunch of stuff on your customers?
- literallyroy 8mo agoThat’s a safer approach but will cause teams to need to test in two infrastructures (old world and new) til the entire new environment is ready for prime time. They’re hopefully moving fast and definitely breaking things.
- paulddraper 8mo agoA few reasons: 1. Stateful systems (databases, message brokers) are hard to switch back-and-forth; you often want to migrate each one as few times as possible. 2. If something goes sideways -- especially performance-wise -- it can be hard to tell the reason if everything changed. 3. It takes a long time (months/years) to complete the migration. By doing it incrementally, you can reap the advantages of the new infra, and avoid maintaining two things. --- All that said, GitHub is doing something wrong.
- 8mo ago
- persedes 8mo agorumors I've heard was that github is mostly run by contractors? That might explain the chaos more than simple vibe coding (which probably aggravates this)
- bartread 8mo agoI think the last major outage wasn't even two weeks ago. We've got about another 2 weeks to finish our MVP and get it launched and... this really isn't helpful. I'm getting pretty fed up of the unreliability.
- aloisdg 8mo agoSure it is not vibe coding related