News for hackers. Stuff that matters.
Re:Another day another GitHub incident by haute_cuisine on Monday October 19, 2026 @12:34PM (#50154477)
Their infra is under constant DDoS + they provide a lot of free stuff for open source projects. There's also a constant churn of dependencies, patches, abandoned libraries, etc. We should give them some appreciation, dealing with this stuff is hard.
Re:Another day another GitHub incident by ianm218 on Monday October 19, 2026 @01:13PM (#50155040)
I think you are giving them way too much leeway. For the service they provide there’s no technical reason it can’t be infinitely scalable. For example their “pull request” page constantly goes down. Serving that kind of workload at high burst load is a fully solved problem.

If they are genuinely compute constrained on CI they should obviously reduce the free offerings rather than take down all their paying customers constantly.

Re:Another day another GitHub incident by dewey on Monday October 19, 2026 @02:16PM (#50155880)
You are basically saying that you, from the outside, have solved the problem perfectly and the whole team of engineers at GitHub just don't know about this one simple solution you are proposing.

Have you considered that you don't have the full context of the problem and it's not "just" a few small tweaks?

Re:Another day another GitHub incident by ianm218 on Monday October 19, 2026 @02:50PM (#50156327)
My guess is that the problem is internal politics and incentives. Yes I think it is a fully solved problem for a company worth trillions to have an infinitely scalable "pull requests" page.

For example, Microsoft is known to pay significantly less than their competitors. I am guessing they just don't have the systems internally to say "This problem is worth literally billions to us in revenue per year, so we will pay millions to IC's to get it fixed and clear internal roadblocks".

It's not "just" small tweaks it is likely that people who are entrenched need to be moved and they need people with the right incentives in place to get it done.

Re:Another day another GitHub incident by dewey on Monday October 19, 2026 @02:55PM (#50156411)
> and they need people with the right incentives in place to get it done

Their c-levels wrote blog posts about the current state and why it happens, pretty sure they know what's going on.

Re:Another day another GitHub incident by ianm218 on Monday October 19, 2026 @04:29PM (#50157652)
I think we just fundamentally disagree here. I'm sure they know the current state and that it doesn't work. I think it's likely that they need entirely different people knowing about these problems and working on them in a totally different reporting structure to get the job done. It's a hard job and they're not up for the task.

I think the reason they can't make that change is that Microsoft is a slow moving rigid culture and doesn't have the kind of org that can adapt to a 10x or 100x increase in usage compared to companies like Google or the AI Labs that handled much more difficult scaling problems.

Have you seen this legendary email thread from 2003 https://www.osnews.com/story/19921/full-text-an-epic-bill-ga...? This isn't a new problem at Microsoft.

Re:Another day another GitHub incident by simoncion on Monday October 19, 2026 @04:31PM (#50157677)
> Their c-levels wrote blog posts about the current state and why it happens, pretty sure they know what's going on.

Having read many of the formal statements from the C*Os in the BigCos I've worked for, I can say with confidence that that is not at all a safe bet to be making.

Re:Another day another GitHub incident by awakeasleep on Monday October 19, 2026 @01:25PM (#50155224)
Even without out the free stuff, no one in this thread seems to have experience managing a self-hosted git environment in even a medium sized company.

It is also constant outages, and then it's your job to diagnose and fix it- and the technical work of that is the easiest part.

It's broken because a team figured out a new way to abuse the company's git infra to get around some process or limitation, and now you have to argue with their manager and then their director about why their team needs to stop using your VCS as a docker registry or whatever.

Re:Another day another GitHub incident by privacyishuman on Monday October 19, 2026 @12:35PM (#50154493)
Agreed. I don't think people realize how much more people are using their free services. It's staggering.
Re:Another day another GitHub incident by Chyzwar on Monday October 19, 2026 @12:38PM (#50154537)
Then just reduce free tier if they cannot handle. I paying for a service but I get best effort freeware quality.
Re:Another day another GitHub incident by boredatoms on Monday October 19, 2026 @12:36PM (#50154515)
They need to cut back on the free tiers if it’s causing outages for paying customers
Re:Another day another GitHub incident by esseph on Monday October 19, 2026 @06:45PM (#50159056)
What if it's the paying customers causing the outages...