Live data from Hacker News

Red Squares – GitHub outages as contributions

red-squares.cian.lol

41–50 of 175 posts

Re: Red Squares – GitHub outages as contributions

#41
post #23

I wonder how well this corolates with azure incidents. Especially for the US regions.

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

Re: Red Squares – GitHub outages as contributions

#44
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/

Pretty damning. Would also be interesting to see the number of commits overlayed. The graph tells a great story about the correlation with MS's takeover, but I wonder if at the same time that uptime went to shit, MS was shifting over large numbers of enterprise contracts to github. That would be a more complete story IMO.

None of which excuses this. Can you imagine someone's reaction in 2017 if you told them that github would be below 90% uptime in 2026? It would be unimaginable.

Re: Red Squares – GitHub outages as contributions

#46
post #40
post #37

Earlier quoted context omitted.

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.

If I remember correctly the status page was not precise before the acquisition - so take with a big grain of salt the 100% pre-acquisition values

Re: Red Squares – GitHub outages as contributions

#49
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

The missing status page [1] treats it as downtime any time any component of the system is down, and calculates the overall uptime based on the time that doesn't overlap with any individual category outages, and the overall downtime as any time overlapping with at least one individual category outage to avoid double-counting They show 24h of minor outage on that date.

I'm guessing that this site is taking the downtime in a given day across all services and adding it up, which would mean the worst possible day has 10 days of downtime (a day of downtime for each major category).

1: https://mrshu.github.io/github-statuses/

Post reply on HN