Live data from Hacker News

Red Squares – GitHub outages as contributions

red-squares.cian.lol

51–60 of 175 posts

Re: Red Squares – GitHub outages as contributions

#51
post #28

A graph I have to question is even accurate. > Across 170 days with at least one incident · worst day Thu, Nov 20, 2025 (1.1 days) 1.1 days total how is that possible? Scrolling over that day doesn't indicate the math behind the scenes - 1.3 hours single bullet point. Also Nov 19 has a bullet point 1.3 day outage but total is 8.1 hours

I see a bullet point for "1.0 days of 1.3 days", and when I mouse over the previous day (Wedensday 2025-11-19), I see "7.8 hours of 1.3 days".

I haven't actually checked any sources to confirm there really was downtime on those days, but if we assume those numbers are true 7.8 hours + 1 day is about 1.3 days.

Re: Red Squares – GitHub outages as contributions

#54
post #41
post #23

Earlier quoted context omitted.

I also bet my money on Azure. Someone who allegedly worked there recently posted an article here on the numerous problems with Azure. Sadly I didn’t bookmark it.

The article you are thinking of was likely written by Axel Rietschin who worked on Azure core compute team. https://isolveproblems.substack.com/p/how-microsoft-vaporize... HN thread: https://news.ycombinator.com/item?id=47616242

Wow. Yikes. I never liked Azure, but this level of dysfunction is just astonishing.

Re: Red Squares – GitHub outages as contributions

#55
post #37
post #30

Earlier 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/

That’s nonsense. GitHub didn’t have 100% uptime before 2020. I remember downtime back then. And Microsoft didn’t make changes that fast. The only thing that changed is the accuracy of their status page.

Also go back and look at the unofficial status page from 3 years ago. It’s regularly above 99% and has been dropping steadily since then. Then in the last 3 months has dropped to below 85%.

Re: Red Squares – GitHub outages as contributions

#57
Contrast between official [0] and third party status pages [1] is huge. How their terms of service for SLA are legal if they are so different from real world usage of their product? I really like GitHub and their services but every time when it’s broken and their status page is green something screams inside me.

[0] https://www.githubstatus.com/ [1] https://mrshu.github.io/github-statuses/

Re: Red Squares – GitHub outages as contributions

#58
post #33

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?

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.

That doesn’t track because GitHub Enterprise Cloud has great uptime. This is all load based, vibe coded ai slop code shipped at record numbers from users who will never convert to paid. The real question is what are they doing about that?
Post reply on HN