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

GitHub Outage Tracker: Is GitHub Cooked?

isgithubcooked.com

Post reply on HN
Print view View original

191–195 of 195 posts

Re: GitHub Outage Tracker: Is GitHub Cooked?

#191

Post by KronisLV »

kashnote wrote: post #12

I think we need to have a little more sympathy for GitHub. You could justify the jabs when we could all blame any outage on the migration to Azure, but then they shared numbers around the scale they're dealing with now that everyone is constantly building and pushing with AI. I think it's commendable that they're not limiting access to the site or (intentionally) throttling newcomers. Yes, they need to get this figur…

> You could justify the jabs when we could all blame any outage on the migration to Azure, but then they shared numbers around the scale they're dealing with now that everyone is constantly building and pushing with AI.

Does nobody use GitLab or Bitbucket or whatever? Why aren't those full of high profile outages as much?

> I think it's commendable that they're not limiting access to the site or (intentionally) throttling newcomers.

I'd kind of expect that for all non-paid members will get rate limited in some ways, sooner or later. Same as what happened with DockerHub, they're probably just trying to hold out due to the reputational hit such a change would carry.

Re: GitHub Outage Tracker: Is GitHub Cooked?

#193

Post by olivewong »

kashnote wrote: post #12

I think we need to have a little more sympathy for GitHub. You could justify the jabs when we could all blame any outage on the migration to Azure, but then they shared numbers around the scale they're dealing with now that everyone is constantly building and pushing with AI. I think it's commendable that they're not limiting access to the site or (intentionally) throttling newcomers. Yes, they need to get this figur…

also this site and the news's measure of github's single 9 availability (1 service at all down even copilot) is a bit harsh https://mrshu.github.io/github-statuses/

Re: GitHub Outage Tracker: Is GitHub Cooked?

#194

Post by queenkjuul »

chris_money202 wrote: post #117
robcohen wrote: post #114

Earlier quoted context omitted.

Start charging more, cut down on CI, figure it out. You don't NEED to give away so much if it means your service is going down.

There isn’t mission critical work being done on GH. You start charging more and the people in charge of finance at companies paying for GH will actually start paying attention. Those finance people don’t care rn because GH is affordable and helps get stuff done. There’s a threshold that exist at every company and once it’s crossed the people who can make money decisions start asking questions

There is absolutely mission critical work being done on GitHub... There are enterprises paying them for their CI and deployment pipelines

Re: GitHub Outage Tracker: Is GitHub Cooked?

#195

Post by queenkjuul »

flohofwoe wrote: post #154
chris_money202 wrote: post #104

Earlier quoted context omitted.

So your proposal is for Microsoft to invest their free cash in helping support a bunch of AI coders maintain their pet projects? Sounds like you should be a CEO!

You don't need to be a CEO to come to the conclusion that throttling to discourage excessive usage is probably a good idea.

You need to be a CEO to come to the opposite conclusion, apparently
Post reply on HN