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

An update on GitHub availability

github.blog

Post reply on HN
Print view View original

161–170 of 266 posts

Re: An update on GitHub availability

#161

Post by alper »

0xy wrote: post #149
rwmj wrote: post #132

Earlier quoted context omitted.

It's entirely possible the move to Azure has made the availability problems worse. Dedicated hardware is much more predictable than cloud. "Let's not move to Azure and instead buy a few more racks" was likely a decision beyond the pay grade of github's management.

Azure is easily the least reliable and least secure of the 3 hyperscalers, which is crazy because GCP was an also-ran underdog not that long ago.

This entire exercise if anything is a huge indictment of Azure.

But that doesn't matter because the kind of person that buys Azure, just like the kind of person that buys MS Teams, is entirely driven by price and does not care about anything else.

Re: An update on GitHub availability

#162

Post by alper »

embedding-shape wrote: post #115
benterix wrote: post #111

Earlier quoted context omitted.

> Seems they themselves realized this after they started moving I guess most people at Github knew exactly it makes no sense but they didn't really have a choice. Maybe some voiced their statement, got "we hear you" in response and were told to proceed anyway.

Yeah, I don't know how it went down, but I also know exactly how it went down: Microsoft Execs: Everyone needs to move to Azure! GitHub developers: But Azure is not gonna be able to handle our load, we literally have our own data centers! Microsoft Execs: Sure, but you're Microsoft now, please publish blog post about how in half a year you'll be 100% on Azure. Few months later... GitHub Developer: We've tried our bes…

Azure is the MS Teams of clouds.

Re: An update on GitHub availability

#164

Post by PunchyHamster »

maccard wrote: post #13

It's kind of hard to read this with a straight face. The unlabelled graph with big numbers on top, the priorities that don't match with what we're experiencing, and a list of things that they're doing without a real acknowledgement of the _dire_ uptime over the last 12 months....

You mean since GH acquisition 6 years ago https://damrnelson.github.io/github-historical-uptime/

Re: An update on GitHub availability

#165

Post by [deleted] »

johndough wrote: post #83
georgyo wrote: post #36

Earlier quoted context omitted.

These are not the worst graphs in the world... Sure the bottom left axis is not labeled, but it still conveys the point correctly. The growth between 2023->2024->2025->2026 is growing quickly. And that in the end/beginning of 2026 they say more growth than the three years before, combined! You don't need to know the bottom left axis number. We do have to assume the graph is linear, and not some kind of negative expon…

> You don't need to know the bottom left axis number. We very much do. The graph suggests an insane growth in PRs from almost zero to 90M. Now compare this misleading graph with this much clearer one, which shows that the growth over the last three years has been less than 80%: https://github.blog/wp-content/uploads/2025/10/octoverse-202...

[deleted]

Re: An update on GitHub availability

#166

Post by PunchyHamster »

mijoharas wrote: post #16
jasoncartwright wrote: post #9

Earlier quoted context omitted.

Seems pretty sensible to not rely on a single provider for their large complex system?

I mean, amazon (shopping, along with prime video e.t.c.) runs on AWS.

It was more "we built AWS to run our stuff and figured out we can sell it too".

While Azure feels like Temu clone of Cloud

Re: An update on GitHub availability

#167

Post by tracker1 »

OtherShrezzing wrote: post #40
ncruces wrote: post #26

Earlier quoted context omitted.

More numbers: https://x.com/kdaigle/status/2040164759836778878 What's the question here, you don't believe growth is currently exponential, or do you think it shouldn't be hard to scale, when 10x YoY is not enough?

As a business user, our costs have gone up while service has gone down dramatically. Meanwhile our marginal cost to GitHub has hardly changed. Where our costs to them have increased, they mostly charge us per cpu minute, so obviously aren’t making any kind of loss on our account. I’m sure they’re experiencing scaling issues across the platform, but it’s unacceptable for that to have a negative impact on us when we're…

I'm curious how Azure DevOps reliability has been for comparison. My current job is managing stories in DevOps with SCC in GitHub ent. While I like Github slightly more, have been curious about the decision.

Re: An update on GitHub availability

#168

Post by vinc »

BlackFingolfin wrote: post #74

GitHub stability has been bad for me. And recently even the data they show me in the web has been unreliably. Since yesterday, me and several colleagues noticed that the pull request lists on the website are incomplete, across many repositories. For example, on https://github.com/gap-system/gap/pulls it says "Pull requests 78" in the "tab list", but the PR list view reports "35 open" (the number 78 is correct, and co…

I noticed the same thing and indeed the status page is not reporting the issue. I could find the missing PRs by browsing the branches page.

Re: An update on GitHub availability

#169

Post by PunchyHamster »

icy wrote: post #18

I'm biased (founder of tangled.org), but the future really should be federated forges. Host repositories on sovereign infra with global identity + federated "metadata" (issues, pulls, etc.). Global indices for this should be trivial to spin up so availability is never a concern (we're working towards this!).

It's cute idea but most people don't want to host their own stuff.

And if they are using 3rd parties to host their stuff, inevitable 1-3 big players will show up offering that as a service.

And even if you do host your own stuff to avoid availability problems, the big actors can still fail just like GH and you can't do shit coz your dependencies need it.

So the solution is same as it is now, proxy or mirror everything you use

Post reply on HN