Live data from Hacker News

GitHub appears to be struggling with measly three nines availability

theregister.com

191–200 of 255 posts

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

#191

Earlier 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.

As someone who was impacted by GitHub's git outage in late February, which caused us to cancel a feature release, I am more sensitive to the availability of their git service, than their chatbot.

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

#193

Earlier 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.

If all I want is actual git, I’m pretty sure I could get much much more than 98.98% uptime. The value of GitHub is actions, issues, PRs. To me, if actions is down GitHub is down

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

#194

To be honest, I’m not surprised that GitHub has been having issues. If you have ever operated GitHub Enterprise Server, it’s a nightmare. It doesn’t support active-active. It only supports passive standbys. Minor version upgrades can’t be done without downtime, and don’t support rollbacks. If you deploy an update, and it has a bug, the only thing you can do is restore from backup leading to data loss. This is the sof…

My $JOB ended up giving up on GHES and migrating to GHEC because of these exact issues.

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

#195

To me, Github has always seemed well positioned to be a one-stop solution for software development: code, CI/CD, documentation, ticket tracking, project management etc. Could anyone explain where they failed? I keep hearing that Github is terrible

We use GH and are investing more in the platform features. Codespaces specifically is quite good for agent heavy teams. Launch a full stack runtime for PRs that are agent owned. > keep hearing that Github is terrible I do not doubt people are having issues and I'm sure there have been outages and problems, but none that have affected my work for weeks. GH is many things to many teams and my sense is that some parts o…

We use GitHub actions and we have more build failures from actions than we do any other source.

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

#197
post #25
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.

I don’t know what’s worse - in 2026 someone genuinely suggesting Jenkins as a viable GHA alternative, or me agreeing with that.

Jenkins has possibly the worst user experience of any piece of software I’ve had to use in the last few years. It’s slow, brittle, somehow both heavyweight and has no features, littered with security vulns due to architecture, is impossible to navigate, has absolutely no standardisation for usage.

And yet it’s still more reliable than GHA.

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

#198

Earlier quoted context omitted.

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

Too bad they didn't find an irrational number, could have got infinite nines.

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

#199

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…

This reminds me of when i looked up how many actions runs the openclaw repo triggers. 700k as of now.

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

#200

Earlier quoted context omitted.

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.

* no ipv6 support * no ff merge support * no sha2 commit hash support

to be fair, git itself only supports sha256 (as opposed to all of sha2) and even then it's marked "THIS OPTION IS EXPERIMENTAL" so many are afraid to use it

ff merge support though....what a world that would be

Post reply on HN