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

131–140 of 195 posts

Re: GitHub Outage Tracker: Is GitHub Cooked?

#131

Post by evilfred »

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…

lol they are Microsoft, and the AI stuff has only multiplied usage like 2x, they haven't had sudden exponential growth

Re: GitHub Outage Tracker: Is GitHub Cooked?

#132

Post by itemize123 »

amelius wrote: post #30
mronetwo wrote: post #25

Earlier quoted context omitted.

We have a business relationship so no we shouldn’t have any sympathy. They sell a service and they’re failing to provide it.

Why? If we have sympathy for Apple then we can have sympathy for Microsoft ...

One, logically, your statement doesn't follow. They're two different companies that have primarily in different market segment. Two, it's not true in the first place - did we side with apple and its cut of the app store revenue for instance?

Re: GitHub Outage Tracker: Is GitHub Cooked?

#133

Post by firesteelrain »

hansvm wrote: post #101
tyre wrote: post #58

Earlier quoted context omitted.

This is uncharitable, rude, and pretty baseless. Unless you have a lot of direct, personal information about GitHub engineers, they’re dealing with a huge spike in traffic. Is their uptime acceptable? No. But personal attacks aren’t necessary or constructive.

The phrasing could have been better, but we've talked as a team about cancelling a $100k/yr contract nearly half a dozen times the last year, and the only thing keeping us from doing so is various "compliance" issues, and to a lesser degree the friction from physically moving. That's a tenuous moat, and if I were a GH PM I'd probably want to know that the current instability is somewhere near critical mass.

You are certainly free to attempt to migrate your workloads to your own or leased data center space in your area then buy your own on prem cloud like Dell Private Cloud and deal with all of the maintenance yourself. I don’t think it would amount to $100k/yr and you would be taking on all the risk.

Re: GitHub Outage Tracker: Is GitHub Cooked?

#134

Post by sleepybrett »

sandeepkd wrote: post #53
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…

I think somewhere down the line you have an answer to problem itself. Its for a while that companies are not into the business of sympathies, we should probably not get into that side for the topic. 1. Github has enterprise users who paid for the service, their day job requires Github to be available and working 2. Github has generous free tier which is the one which is exploring a lot more with the AI generated code…

they could rate limit pushes to free projects.

Re: GitHub Outage Tracker: Is GitHub Cooked?

#135

Post by chanux »

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…

They probably have bad PR because of huge AI push, Sizeable layoffs etc.

It's probably not fair to the people who are left but alas, this is apparently how the world works.

Re: GitHub Outage Tracker: Is GitHub Cooked?

#137

Post by dcow »

firesteelrain wrote: post #133
hansvm wrote: post #101

Earlier quoted context omitted.

The phrasing could have been better, but we've talked as a team about cancelling a $100k/yr contract nearly half a dozen times the last year, and the only thing keeping us from doing so is various "compliance" issues, and to a lesser degree the friction from physically moving. That's a tenuous moat, and if I were a GH PM I'd probably want to know that the current instability is somewhere near critical mass.

You are certainly free to attempt to migrate your workloads to your own or leased data center space in your area then buy your own on prem cloud like Dell Private Cloud and deal with all of the maintenance yourself. I don’t think it would amount to $100k/yr and you would be taking on all the risk.

Self-hosted is not the only alternative...

Re: GitHub Outage Tracker: Is GitHub Cooked?

#138

Post by chanux »

fragmede wrote: post #126
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…

The question is, do we think Google would have the same problems running the service? (I'm biased from having worked there tho.)

I realized they killed Google Cloud Source Repositories and introduced some new product in true Google fashion.

However, YouTube did well where Google Videos did not. Who knows what it would be like if big G bought GH.

Re: GitHub Outage Tracker: Is GitHub Cooked?

#139

Post by stevejb »

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…

I don't know enough about Github or Microsoft to say anything intelligent, but I agree with your sentiment in general. And, one thing is for sure - I have used Github for years, pushing many thousands of commits on personal, private projects. I've burned through as many free action minutes as I can, and I use my own action runners as well. I've done this all for free, so on balance I am grateful for them.
Post reply on HN