yeah, between github and claude they're's an outage 75% of the time:
https://www.aakash.io/tech-chase/github-and-claude-are-down-...
GitHub appears to be struggling with measly three nines availability
241–250 of 255 posts
Re: GitHub appears to be struggling with measly three nines availability
#242when GitHub moved to react instead of server rendered pages ie erb/turbolinks/pjax was the start to the end. the pages got slower, rendering became a nightmare. then they introduced GitHub actions (half baked) - again very unreliable then they introduced Copilot - again not very reliable it's easy to see why availability has gone down the drain. are they still on the rails monolith ? they speak about it less these da…
I’m not disagreeing, but I think you have the order wrong. Half baked actions was released before they moved to react. I’m talking about the version that used hcl for config instead of yaml.
Re: GitHub appears to be struggling with measly three nines availability
#243Earlier quoted context omitted.
GH Actions was good for them as another billable feature, but I'm skeptical we actually gained much over external CI providers The improvements to PR review have been nice though
Don't forget the security implications if you host your own actions runner.
What are these?
Re: GitHub appears to be struggling with measly three nines availability
#244Earlier quoted context omitted.
You're right that labelling any outage as "Github is down" is an overgeneralisation, & we should focus on bottlenecks that impact teams in a time sensitive matter, but that isn't the case here. Their most stable service (API) has only two 9s (99.69%). They're not even struggling to get their average to three 9s, they're struggling to get ANY service to three 9s. They're struggling to get many services to two 9s. Copi…
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.
Those 27 hours only seem to happen during the workday when I’m trying to push branches, run CI pipelines or otherwise use GitHub (I don’t use Copilot). Whatever the yearly figure, it’s been a pain in the ass these last few months and it’s unacceptable, free or no (my company pays for GitHub).
Re: GitHub appears to be struggling with measly three nines availability
#245Earlier quoted context omitted.
You're right that labelling any outage as "Github is down" is an overgeneralisation, & we should focus on bottlenecks that impact teams in a time sensitive matter, but that isn't the case here. Their most stable service (API) has only two 9s (99.69%). They're not even struggling to get their average to three 9s, they're struggling to get ANY service to three 9s. They're struggling to get many services to two 9s. Copi…
ONLY TWO NINES! Meanwhile vital government services here have a whopping 25% availability.
Which services have 25% uptime?
Re: GitHub appears to be struggling with measly three nines availability
#246From GitHub CTO in 2025 when they announced they're moving everything to Azure instead of letting GitHub's infrastructure remain independent: > For us, availability is job #1, and this migration ensures GitHub remains the fast, reliable platform developers depend on That went about as well as everyone thought back then. Does anyone else remember back in ~2014-2015 sometime, when half the community was screaming at Gi…
GitHub have not really got much better at adding new features either though :(
They’ve really improved Projects! If your team is entirely technical, this can replace Jira.
Re: GitHub appears to be struggling with measly three nines availability
#247Re: GitHub appears to be struggling with measly three nines availability
#248It's time to look for a decentralized Non-Hub alternative.
https://tangled.org builds on atproto for the social features.
Re: GitHub appears to be struggling with measly three nines availability
#249Earlier quoted context omitted.
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]
CI is basically a glorified shell script executor with some env variable/credential injection. We don't use many of the plugins aside from the docker and the agent shell one.
I'm not sure I'm sold on this argument considering the docker image for GH Actions is made by "myoung34" and half the actions are community written, have terrible documentation and feel like abandonware too.
Re: GitHub appears to be struggling with measly three nines availability
#250Earlier quoted context omitted.
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…
Yep, I went through the exact same pains. We desperately wanted to move to something else and I kept steering us away from Jenkins as I'd experienced its pains at a previous role. We evaluated tons of different options and begrudgingly settled on Jenkins too.