Earlier quoted context omitted.
change is the biggest cause then?
Or usage
I imagine that it could be usage, but it also could be fewer people caring to report issues on the weekends too for that matter.
Red Squares – GitHub outages as contributions
111–120 of 175 posts
Re: Red Squares – GitHub outages as contributions
#112Every time one of these vibe coded meme sites gets posted there’re endless comments about how it’s not actually because of load, the GitHub team is shit, their tech stack is shit, Microsoft is shit, Azure is shit, etc. Just compare the GitHub status page for public GitHub vs the enterprise cloud pages. Enterprise has much better numbers and I’ve personally can’t remember the last time there was an outage that prevent…
> the GitHub team is shit, their tech stack is shit 1) Criticism of being unable to achieve service is not a fault of the individual; it simply is a fault of the system. You can criticise the system, it's permissible. Especially if they have more resources than many countries and some of the best tech talent in the world on staff. 2) Their tech stack is shit, and they've gone on record for years defending it, quite a…
The avalanche of same comments to every meme tier post about this is the opposite of curious.
Very little discussion of any merit happens on these posts. It’s mostly bandwagoning and repeating the same comments they read on the last iteration.
Re: Red Squares – GitHub outages as contributions
#113> Disruption with Gemini 2.5 Pro model > Disruption with Grok Code Fast 1 in Copilot > Incident with Copilot Grok Code Fast 1 > Claude Opus 4 is experiencing degraded performance It doesn't seem fair to blame Github for this? There's nothing they can do about it?
The pattern recently is to collect every individual service degradation and present them as all equally significant. Erase the severity and then present them all as “GitHub outages” or reduce it to an uptime graph. I’m not happy with GitHub’s recent major outages either, but there is an ugly side of the pile-on where we’re getting these vibecoded attention seeking websites and social media posts to collect upvotes, l…
Every time a github outage is posted I start wondering more and more what % of hacker news commenters have actually worked on a system with >10k active hosts and have seen what it takes to run them and how internal dashboards are presented. So much of the criticism just makes 0 sense especially the third party uptime pages.
Re: Red Squares – GitHub outages as contributions
#114Every time one of these vibe coded meme sites gets posted there’re endless comments about how it’s not actually because of load, the GitHub team is shit, their tech stack is shit, Microsoft is shit, Azure is shit, etc. Just compare the GitHub status page for public GitHub vs the enterprise cloud pages. Enterprise has much better numbers and I’ve personally can’t remember the last time there was an outage that prevent…
> the GitHub team is shit, their tech stack is shit 1) Criticism of being unable to achieve service is not a fault of the individual; it simply is a fault of the system. You can criticise the system, it's permissible. Especially if they have more resources than many countries and some of the best tech talent in the world on staff. 2) Their tech stack is shit, and they've gone on record for years defending it, quite a…
> It's a waste of time to rewrite the UI and push AI tools when you can't even keep the site lit.
This is a flawed argument. There are many designers and frontend engineers there who have zero role in improving site reliability. They might as well keep doing their jobs, instead of having the CSS wizards and art school grads team up and try to crack Azure.
Re: Red Squares – GitHub outages as contributions
#115Wow, that’s a great visualization. How many 7s of uptime is that?
Re: Red Squares – GitHub outages as contributions
#116Every time one of these vibe coded meme sites gets posted there’re endless comments about how it’s not actually because of load, the GitHub team is shit, their tech stack is shit, Microsoft is shit, Azure is shit, etc. Just compare the GitHub status page for public GitHub vs the enterprise cloud pages. Enterprise has much better numbers and I’ve personally can’t remember the last time there was an outage that prevent…
We are using the entreprise offering. We are seeing the problems.
Re: Red Squares – GitHub outages as contributions
#117Funny how it's less during weekends, as if by them working on it it gets worse and when they leave it alone it's solid.
Re: Red Squares – GitHub outages as contributions
#118Earlier quoted context omitted.
What do you mean by enterprise cloud? The default GitHub enterprise cloud plan is hosted on the same infra as “public github.” Do you have a link to what you mean?
Interested in this difference as well. It'd make sense if there was a "you get what you pay for" attitude at MS re: public GitHub. It's not a good position for the free users, but, what else are you gonna do? Stand up your own? Retrain yourself on your SDLC in a new platform? They need a competitor.
GitLab
Re: Red Squares – GitHub outages as contributions
#119Earlier quoted context omitted.
> the GitHub team is shit, their tech stack is shit 1) Criticism of being unable to achieve service is not a fault of the individual; it simply is a fault of the system. You can criticise the system, it's permissible. Especially if they have more resources than many countries and some of the best tech talent in the world on staff. 2) Their tech stack is shit, and they've gone on record for years defending it, quite a…
> It's a waste of time to rewrite the UI and push AI tools when you can't even keep the site lit. This is a flawed argument. There are many designers and frontend engineers there who have zero role in improving site reliability. They might as well keep doing their jobs, instead of having the CSS wizards and art school grads team up and try to crack Azure.
The implication here is that after 8 years of having issues management has not intentionally hired UX designers or programmers to work on AI features over people who could help build more reliability.
We've reframed this argument from the original "stop punching down" to, now "well, managements allocation of resources is fine because they have staff that would otherwise do nothing".
Thing is, I agree with the base of your argument, over the course of a quarter (or 3, or even 5..) the release of a feature does not mean that resources have been taken from the core.
However... it's been a really long time, and now we're hitting a critical point where the added load of AI, the rot that has been allowed to set in at the core, and the fact that they haven't been allocating staff to improving those pieces is hitting an inflection point.
I can't say for sure, as I don't work there, but I think if the trend is going lower for literally years: management could have changed course.
Those frontend designers didn't hire themselves and normal turnover is something like 5% for a healthy org: there was a conscious effort there. And those feature designers on AI can definitely have done work on reliability.
Re: Red Squares – GitHub outages as contributions
#120Funny how it's less during weekends, as if by them working on it it gets worse and when they leave it alone it's solid.
Kind of normal I think, at the companies I've worked for, most outages were caused by a change in production, for which the impact was not properly assessed.