31–40 of 150 posts
[1]: https://www.reddit.com/r/ProgrammerHumor/comments/1p204nx/ac... [2]: https://news.ycombinator.com/item?id=47230704
In many companies I worked for, there were a bunch of infrastructure astronauts who made everything very complicated in the name of zero downtime and sold them to management as “downtime would kill pur credibility and our businesses ”, and then you have billion dollar companies everyone relies on (GitHub, Cloudflare) who have repeated downtime yet it doesn't seem to affect their business in any way.
Of course, once you have the momentum it doesn't matter nearly as much, at least for a while. If it happens too much though, people will start looking for alternatives.
The key to remember is Momentum is hard to redirect, but with enough force (reasons), it will.
In many companies I worked for, there were a bunch of infrastructure astronauts who made everything very complicated in the name of zero downtime and sold them to management as “downtime would kill pur credibility and our businesses ”, and then you have billion dollar companies everyone relies on (GitHub, Cloudflare) who have repeated downtime yet it doesn't seem to affect their business in any way.
The reality is that consumers don't really care about downtime unless it's truly frequent.
And the frequency they can tolerate is surprisingly high given that we're talking about the 20th or so outage of 2026 for github. (See: https://news.ycombinator.com/from?site=githubstatus.com)
How reliable is githubstatus.com? I know that status pages are generally not updated until Leadership and/or PR has a chance to approve the changes; is that the case here? Our health check checks against githubstatus.com to verify 'why' there may be a GHA failure and reports it, e.g. Cannot run: repo clone failed — GitHub is reporting issues (Partial System Outage: 'Incident with Copilot and Actions'). No cached mani…
Right now the page says Copilot and Actions are affected but I can't even push anything to a repo from the CLI.
[flagged]
> a lot of infrastructure quietly assumes GitHub is always available Which is really baffling when talking about a service that has at least weekly hicups even when it's not a complete outage. There's almost 20 outages listed on HN over the past two months: https://news.ycombinator.com/from?site=githubstatus.com so much for “always available”.
codeberg might be a little slower on git cli, but at least it's not becoming a weekly 'URL returned error: 500' situation...
These days it feels like people have simply forgotten that you could also just have a bare repository on a VPS and use it over ssh.
How many 9s is GitHub at now? 2?
https://mrshu.github.io/github-statuses/
Most individual services have two nines... but not all of them.