Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub appears to be struggling with measly three nines availability

theregister.com

Post reply on HN
Print view View original

181–190 of 255 posts

Re: GitHub appears to be struggling with measly three nines availability

#181

Post by dijksterhuis »

a-french-anon wrote: post #43
cedws wrote: post #18

While 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…

If you want more ammo for your ranting (no offense meant, I also rant): an issue as massive as https://github.com/orgs/community/discussions/142308 lingering for years should do the trick.

i had something similar with PRs last year. 2x PRs of mine disappeared for me. they were still counted in the total number of PRs and everyone else could see them.

0_o

Re: GitHub appears to be struggling with measly three nines availability

#182

Post by sauercrowd »

astralasia wrote: post #91
sauercrowd wrote: post #82

I'm somewhat surprised with Github's strategy in the AI times. I understand how appealing it is to build an AI coding agent and all that, but shouldn't they - above everything else - make sure they remain THE platform for code distribution, collaboration and alike? And it doesnt need to be humans, that can be agents as well. They should serve the AI agent world first and foremost. Cause if they dont pull that off, an…

Microsoft’s real goal is selling Copilot seats and pushing Azure, not building a neutral playground for third-party agents. There is just no money for them in being the backend for someone else's AI. As for the AI spam, GitHub's internal metrics have always been tied to engagement and PR volume. Blocking all that AI slop would instantly drop their growth numbers, so it is easier for them to just pass the cleanup cost…

No disagreement here. Just very short sighted.

Re: GitHub appears to be struggling with measly three nines availability

#183

Post by stefan_ »

imglorp wrote: post #96
cedws wrote: post #18

While 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…

Public service announcement You can pin actions versions to their hash. Some might say this is a best practice for now. It looks like this, where the comment says where the hash is supposed to point. Old --> uses: actions/checkout@v4 New --> uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4 There is a tool to sweep through your repo and automate this: https://github.com/mheap/pin-github-action

Checkout v4 of course, released in August 2025, which already now pollutes my CI status with garbage warnings about some Node version being deprecated I could absolutely care less about. I swear half the problems of GitHub are because half that organization has some braindead obsession with upgrading everything everywhere all the time, delivering such great early slop experiments as "dependabot".

Re: GitHub appears to be struggling with measly three nines availability

#184

Post by garettmd »

martinald wrote: post #20

I wonder how much of this is down to the massive amount of new repos and commits (of good or bad quality!) from the coding agents. I believe that the App Store is struggling to keep up with (mostly manual tbf) app reviews now, with sharp increases in review times. I find it hard to believe that an Azure migration would be that detrimental to performance, especially with no doubt "unlimited credit" to play with? You c…

I think part of the issue is that Azure has been struggling to reliably provision Linux VMs. Whether that's due to increased load, poor operational execution, or a combination of them, it's hard for anyone on the outside to know.

Re: GitHub appears to be struggling with measly three nines availability

#185

Post by OJFord »

imglorp wrote: post #96
cedws wrote: post #18

While 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…

Public service announcement You can pin actions versions to their hash. Some might say this is a best practice for now. It looks like this, where the comment says where the hash is supposed to point. Old --> uses: actions/checkout@v4 New --> uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4 There is a tool to sweep through your repo and automate this: https://github.com/mheap/pin-github-action

> There is a tool to sweep through your repo and automate this: [third-party]

Dependabot, too.

Re: GitHub appears to be struggling with measly three nines availability

#186

Post by [deleted] »

Anon1096 wrote: post #63

Anyone who used the phrase "measly" in relation to three nines is inadvertently admitting their lack of knowledge in massive systems. 99.9 and 99.95 is the target for some of the most common systems you use all day and is by no means easy to achieve. Even just relying on a couple regional AWS services will put your CEILING at three nines. It's even more embarrassing when people post that one GH uptime tracker that co…

[deleted]

Re: GitHub appears to be struggling with measly three nines availability

#187

Post by hrmtst93837 »

PxldLtd wrote: post #25
Eikon wrote: post #4

As of recently (workflows worked for months) I even have part of my CI on actions that fails with [0] 2026-02-27T10:11:51.1425380Z ##[error]The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled. 2026-02-27T10:11:56.2331271Z ##[error]The operation was canceled. I had to disable the workflows. GitHub support response has been “ We recomme…

We've jumped ship to self-hosted Jenkins. Woodpecker CI looks cool but Jenkins seemed like a safer bet for us. It's been well worth the effort and it's simplified and sped up our CI massively. Once we got the email that they were going to charge for self-hosted runners that was the final nail in the coffin for us. They walked it back but we've lost faith entirely in the platform and vision.

[flagged]

Re: GitHub appears to be struggling with measly three nines availability

#188

Post by dathinab »

kbelder wrote: post #126
dathinab wrote: post #78

Earlier quoted context omitted.

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.

what I meant is having both at the same time

- at most 20min per 3 hour

- and 99.9% uptime on a yearly basis

as in your yearly budged of outage is ~8.76h but that budged shouldn't happen all at once and if there is an outage it at most delays works by 20min at a time, and not directly again after you had a downtime

but I did fumble the 90.21% part, which is ~35.73 days i.e. over 857 hours....

Re: GitHub appears to be struggling with measly three nines availability

#190

Post by maccard »

lucideer wrote: post #151
ARandomerDude wrote: post #134

Earlier quoted context omitted.

I love multiple 9s as much as the next guy but that's only 27 hours per year of downtime. For a mostly free (for me) service, I'm thankful.

Honestly, you're right - 2̶7̵ 87+ (correction from sibling) hours per year is absolutely fine & normal for me & anything I want to run. I personally think it should be fine for everybody. On the other hand the baseline minimal Github Enterprise plan with no features (no Copilot, GHAS, etc.) runs a medium sized company $1m+ per annum, not including pay-per-use extras like CI minutes. As an individual I'm not the targe…

87 hours a year is 1.5 hours a week. If that 1.5 hour window is when you need to use it it matters a hell of a lot more than if it’s 4am on a Sunday.
Post reply on HN