I don't really understand why this is happening at this scale, it's not like they just became broke and can't afford a proper server... can someone explain?
They’re on track to 30x volume yoy by their own words
Red Squares – GitHub outages as contributions
31–40 of 175 posts
Re: Red Squares – GitHub outages as contributions
#32The memes are really painful now. I feel for the team that's is trying to survive underwater.
With management screaming down their necks:
YOU NEED TO USE MOAR AI!
Re: Red Squares – GitHub outages as contributions
#33I don't really understand why this is happening at this scale, it's not like they just became broke and can't afford a proper server... can someone explain?
I suspect it’s caused because Microsoft is using buggy Microsoft tech instead of the original stack.
They’re making political decisions based on what they sell vs what’s actually useful for their use case.
It’s kind of impossible to find out if this is true though.
Re: Red Squares – GitHub outages as contributions
#34All these companies brag about being hyperscalers and cannot scale github.
Similarly, i see google releasing advancement after advancement in LLM yet i see antigravity sub where people are crying all time.
Re: Red Squares – GitHub outages as contributions
#35Setup my self-hosted Forgejo last night. Very pleased so far.
Re: Red Squares – GitHub outages as contributions
#36Weekends are the untapped frontier. Still room to scale.
change is the biggest cause then?
Re: Red Squares – GitHub outages as contributions
#37I don't really understand why this is happening at this scale, it's not like they just became broke and can't afford a proper server... can someone explain?
Agents are shipping code faster all over the world and in some cases 24 hours a day. Additionally, some significant number of non-developers are now developers i.e. they are also shipping to github regularly. This is not limited to just pushing code but all the bells and whistles that github added as features under the assumption of some predictable growth are now exceeding the original plans. I suspect a lot of thei…
They were sucking 5 years ago before agents existed. I don’t think this has anything to do with recent changes.
Re: Red Squares – GitHub outages as contributions
#38I don't really understand why this is happening at this scale, it's not like they just became broke and can't afford a proper server... can someone explain?
Agents are shipping code faster all over the world and in some cases 24 hours a day. Additionally, some significant number of non-developers are now developers i.e. they are also shipping to github regularly. This is not limited to just pushing code but all the bells and whistles that github added as features under the assumption of some predictable growth are now exceeding the original plans. I suspect a lot of thei…
[flagged]
Re: Red Squares – GitHub outages as contributions
#39Setup my self-hosted Forgejo last night. Very pleased so far.
Yeah me too. I moved all my public projects to codeberg and my internal repos to self-hosted forgejo.
Hosting forgejo is really easy as well. It being a single binary makes it really easy to handle with almost zero maintenance.
Re: Red Squares – GitHub outages as contributions
#40Earlier quoted context omitted.
Agents are shipping code faster all over the world and in some cases 24 hours a day. Additionally, some significant number of non-developers are now developers i.e. they are also shipping to github regularly. This is not limited to just pushing code but all the bells and whistles that github added as features under the assumption of some predictable growth are now exceeding the original plans. I suspect a lot of thei…
They were sucking 5 years ago before agents existed. I don’t think this has anything to do with recent changes. https://damrnelson.github.io/github-historical-uptime/
Whoa, if that is even remotely accurate then the talk about agents is a complete red herring.