Live data from Hacker News

GitHub appears to be struggling with measly three nines availability

theregister.com

81–90 of 255 posts

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

#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, and dont pull off building one of the best coding agents - whcih so far they didnt - there isn't much left.

There's so many new features needed in this new world. Really unclear why we hear so little about it, while maintainers smack the alarm bell that they're drowning in slop.

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

#83

Have 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

Well then clearly you haven't taken a look at https://status.claude.com .

I get the email notifications from Anthropic’s status monitor, and I think they might be my most frequent emailer these days.

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

#85
post #27

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

> Copilot [has] seen a 96.47% uptime

That’s… one 9 of reliability. You could argue the title understates the problem.

> You don't need every single service to be online in order to use GitHub.

Well that’s how they want you to use it, so it’s an epic failure in their intended use story. Another way to put this is ”if you use more GitHub features, your overall reliability goes down significantly and unpredictably”.

Look, I have never been obsessed with nines for most types of services. But the cloud service providers certainly were using it as major selling/bragging points until it got boring and old because of LLMs. Same with security. And GitHub is so upstream that downstream effects can propagate and cascade quite seriously.

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

#86

Have 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

It looks this bad because that includes 'degraded performance,' not just outrage.

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

#87
post #27

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

96% is horrible uptime though

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

#88

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…

[deleted]

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

#89

Earlier quoted context omitted.

Did react render better than turbo or the opposite? I assume a well-optimized turbo page would perform better

React destroyed perf and used more resources than turbo

Was there any discussion to use something other than react?

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

#90

Earlier quoted context omitted.

This was before Actions and a whole lot of other non-git related stuff. There was years (maybe even a decade?) where GitHub essentially was unchanged besides fixes and small incremental improvements, long time ago :)

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

> The improvements to PR review have been nice though

I dunno, probably the worst UX downgrade so far, almost no PRs are "fully available" on page load, but requires additional clicks and scrolling to "unlock" all the context, kind of sucks.

Used to be you loaded the PR diff and you actually saw the full diff, except really large files. You could do CTRL+F and search for stuff, you didn't need to click to expand even small files. Reviewing medium/large PRs is just borderline obnoxious today on GH.

Post reply on HN