Pretty soon, the only 9 they’re going to have is the 9 8s…
GitHub appears to be struggling with measly three nines availability
121–130 of 255 posts
Re: GitHub appears to be struggling with measly three nines availability
#122Not owned by companies that help the US Federal Government illegally spy on their own citizens and murder children overseas: Gitlab Bitbucket Sourceforge Forgejo Codeberg Radicle Launchpad Owned by companies that help the US Federal Government illegally spy on their own citizens and murder children overseas: Github
Codeberg is nice.
Re: GitHub appears to be struggling with measly three nines availability
#123Re: GitHub appears to be struggling with measly three nines availability
#124While GitHub obsess over shoving AI into everything, the rest of the platform is genuinely crumbling and its security flaws are being abused to cause massive damage. Last week Aqua Security was breached and a few repositories it owns were infected. The threat actors abused widespread use of mutable references in GitHub Actions, which the community has been screaming about for years, to infect potentially thousands of…
I worry that CI just got overcomplicated by default when providers started rocking up with templated YAML and various abstractions over it to add dynamic behaviour, dependencies, and so on. Perhaps mixing the CI with the CD made that worse because usually deployment and delivery has complexities of its own. Back in the day you'd probably use Jenkins for the delivery piece, and the E2E nightlies, and use something mor…
You could use these shell script versions of pipelines in GHA though, right? There is nothing stopping you from triggering a bash script via a "run" step in YAML.
These reusable actions are nothing but a convenience feature. This discussion isn't much different than any other supply chain, dependency, or packaging system vulnerability such as NPM, etc.
One slight disclaimer here is the ability of someone to run their own updated copy of an action when making a PR. Which could be used to exfil secrets. This one is NOT related to being dependent on unverified actions though.
(re-reading this came across as more harsh than I intended.. my bad on that. But am I missing something or is this the same issue that every open-source user-submitted package repository runs in to?)
Re: GitHub appears to be struggling with measly three nines availability
#125Have anyone checked out the status page? It's actually way worse than I thought, I believe this is the first time I am actually witnessing a status page with truly horrible results. https://mrshu.github.io/github-statuses
Especially compared to its archive page: https://web.archive.org/web/20190510070456/https://www.githu...
1-4 incidents per month compared to about 1 daily.
Re: GitHub appears to be struggling with measly three nines availability
#126Earlier quoted context omitted.
Well then clearly you haven't taken a look at https://status.claude.com .
At that 3rd party side GH is currently noticeable worse then claude ... Like they are down to one 9 availability and very very close to losing that to (90.2x%). This also fit more closely to my personal experience, then the 99.900-99.989 range the article indicates... Through honestly 99.9% means 8.76h downtime a year, if we say no more then 20min down time per 3 hours (sliding window), and no more then 1h a day, and…
You may have fumbled the calculator at one point. 20Min per 3 hours is 88.8% uptime. 99.9% uptime is 11 seconds down.
Re: GitHub appears to be struggling with measly three nines availability
#127Just to add a little bit of nuance to this not because I'm trying to defend GitHub, they definitely need to up their reliability, but the 90% uptime figure represents every single service that GitHub offers being online 90% of the time. You don't need every single service to be online in order to use GitHub. For example, I don't use Copilot myself and it's seen a 96.47% uptime, the worst of the services which are tra…
Here is the same thing in 2019: https://web.archive.org/web/20190510070456/https://www.githu...
It seems that the same metric is about a magnitude worse than before.
Re: GitHub appears to be struggling with measly three nines availability
#128Earlier quoted context omitted.
And notably, that page makes this post's title inaccurate. As of this morning, it says `90.21% uptime`, which is a _single_ 9, not 3 (though that's for the platform as a whole, no individual component appears to achieve three 9s.)
Note that it gets 90% largely off Copilot going down and Actions not working. Actual git has 98.98%, which is still just one 9 but a lot better.
> 98.98%
it's the 2 nines they aimed for
Re: GitHub appears to be struggling with measly three nines availability
#129Just to add a little bit of nuance to this not because I'm trying to defend GitHub, they definitely need to up their reliability, but the 90% uptime figure represents every single service that GitHub offers being online 90% of the time. You don't need every single service to be online in order to use GitHub. For example, I don't use Copilot myself and it's seen a 96.47% uptime, the worst of the services which are tra…
more context -- their enterprise SLA is 99.9% (3x9) uptime for individual services
https://github.com/customer-terms/github-online-services-sla
> GitHub commits to maintain at least 99.9% Uptime for the applicable GitHub service.
... and none of the individual services have hit 99.9% uptime in the last 90 days according to this site. 0_o
Re: GitHub appears to be struggling with measly three nines availability
#130Just to add a little bit of nuance to this not because I'm trying to defend GitHub, they definitely need to up their reliability, but the 90% uptime figure represents every single service that GitHub offers being online 90% of the time. You don't need every single service to be online in order to use GitHub. For example, I don't use Copilot myself and it's seen a 96.47% uptime, the worst of the services which are tra…
the basic git services are at one nine of availability