Weekends are the untapped frontier. Still room to scale.
skor 12 minutes ago [-]
change is the biggest cause then?
jve 16 minutes ago [-]
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
figmert 47 minutes ago [-]
Far fewer outages during the weekends. Perfect, wasn't gonna do any work then anyway.
elAhmo 23 minutes ago [-]
Funny to see this closely match contribution graphs with effectively no downtime on weekends.
jpb0104 12 minutes ago [-]
Setup my self-hosted Forgejo last night. Very pleased so far.
hosteur 5 minutes ago [-]
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.
lnenad 54 minutes ago [-]
The memes are really painful now. I feel for the team that's is trying to survive underwater.
renegade-otter 14 minutes ago [-]
With management screaming down their necks:
YOU NEED TO USE MOAR AI!
pards 33 minutes ago [-]
This design is perfect irony. I love it.
bharxhav 51 minutes ago [-]
Would be interesting to see if this correlated with their release cycles.
hosteur 45 minutes ago [-]
Well, outages seem to be distributed across all days except weekends. So this seems like people fucking around with stuff being a major factor.
samlinnfer 36 minutes ago [-]
Surely it just means more people working, resulting in more load, resulting in more outages?
pwagland 19 minutes ago [-]
Or even both. In any kind of continuous deployment, you'd expect outages at the point of deployment, or shortly thereafter as the unintended consequences ripple.
Then the load during the working days makes those ripples larger and into outages.
embedding-shape 20 minutes ago [-]
Most outages are caused by changes by humans ("actors"?), very rarely are things "People just dig our stuff so much we can't keep up" but more often "We didn't think about this performance drawback when we built thing X, now it's hurting us", and of course, more outages when you try to fix those issues without fully considering the scope and impact.
korrectional 26 minutes ago [-]
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?
fareesh 15 minutes ago [-]
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.
prepend 12 minutes ago [-]
They were sucking 5 years ago before agents existed. I don’t think this has anything to do with recent changes.
Whoa, if that is even remotely accurate then the talk about agents is a complete red herring.
potatoman22 9 minutes ago [-]
[flagged]
prepend 13 minutes ago [-]
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.
plufz 23 minutes ago [-]
See previous days articles. Agentic coding. Going from 1b annual commits to estimated 14b or more from one year to another.
baq 14 minutes ago [-]
They’re on track to 30x volume yoy by their own words
embedding-shape 22 minutes ago [-]
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.
dicksent 17 minutes ago [-]
ai
faangguyindia 13 minutes ago [-]
All 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.
danfritz 42 minutes ago [-]
I wonder how well this corolates with azure incidents. Especially for the US regions.
p2detar 23 minutes ago [-]
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.
hosteur 2 minutes ago [-]
The article you are thinking of was likely written by Axel Rietschin who worked on Azure core compute team.
I live in Europe. I've not noticed these constant outages. But I only use GitHub after work.
airstrike 28 minutes ago [-]
can you correlate this to data on # of commits, actions, etc?
cyanydeez 58 minutes ago [-]
double entendre: Is it load based or github-employee based that weekends are sparser.
or just a multifactor of both.
globular-toast 52 minutes ago [-]
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.
mirekrusin 29 minutes ago [-]
From the chart it seems they should have policy to deploy on weekends only.
Shoetp 54 minutes ago [-]
Yes
ramon156 32 minutes ago [-]
Please tell me this makes sense
This website has no overused ai-generated animations and... I quite enjoy it. The original website[1] has a fade-in animation, big round cards, shadows, all the jazz you can think of, it's there.
This site is very readable, very honest and sober. I don't need to sift through buzzwords to figure out tiny details.
> 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
Hosting forgejo is really easy as well. It being a single binary makes it really easy to handle with almost zero maintenance.
YOU NEED TO USE MOAR AI!
Then the load during the working days makes those ripples larger and into outages.
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.
https://damrnelson.github.io/github-historical-uptime/
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.
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.
Similarly, i see google releasing advancement after advancement in LLM yet i see antigravity sub where people are crying all time.
https://isolveproblems.substack.com/p/how-microsoft-vaporize...
HN thread: https://news.ycombinator.com/item?id=47616242
or just a multifactor of both.
It does look like Friday outages were a bit rarer, which could be due to having a "no deployments on Friday" rule.
This website has no overused ai-generated animations and... I quite enjoy it. The original website[1] has a fade-in animation, big round cards, shadows, all the jazz you can think of, it's there.
This site is very readable, very honest and sober. I don't need to sift through buzzwords to figure out tiny details.
Thank you, OP!
1: https://mrshu.github.io/github-statuses/
[0] https://news.ycombinator.com/item?id=22867803