change is the biggest cause then?

Wait until they go 996!

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/

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.

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.

With management screaming down their necks:

YOU NEED TO USE MOAR AI!

I live in Europe. I've not noticed these constant outages. But I only use GitHub after work.

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.

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 their existing systems have to be re-architected for unanticipated scale, and it won't happen overnight for sure.

They’re on track to 30x volume yoy by their own words

See previous days articles. Agentic coding. Going from 1b annual commits to estimated 14b or more from one year to another.

The faster you move, the more you screw up, almost no company producing software have figured out how to move fast and not screw up. It's so hard, that companies even used to boast about how much they didn't care about screwing up, as long as they moved fast.

Add in new "productivity" tools that help you move even faster, with even less regards for how much you screw up (even though the tool could be used for you to move at the same speed, but with less screw ups), and an engineering culture which boils down to "Why not?", and you get platforms run by Microsoft that are unable to achieve two nines of reliability.

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.

ai

Well, outages seem to be distributed across all days except weekends. So this seems like people fucking around with stuff being a major factor.

Didn't they blame "AI" for the increased load? I'm not sure why AI usage would be more during the week than the weekend, but it could be.

It does look like Friday outages were a bit rarer, which could be due to having a "no deployments on Friday" rule.

Yes