Hmm this is quite an incident, I haven't seen Github reject all pushes to all repos like this in quite some time.... hopefully not SSH key related
GitHub issue - resolved
61–70 of 169 posts
Re: GitHub issue - resolved
#62ok this makes sense i was just trying to push
Re: GitHub issue - resolved
#63Why GitHub is down so often? Why is it not possible to keep it up 100% of time (without counting physical failure)?. I haven't seen any down time for my system (it has hundreds of thousands of users online) in months since I have completed the setup.
ChatGPT overloading it... (scanning repos)
Re: GitHub issue - resolved
#64Earlier quoted context omitted.
I'm sure your scale is similar.
Google search is basically never down. AWS is basically never down. WhatsApp is basically never down. Time for GitHub to grow up?
RO system is generally probably easier to keep up than a RW system that is constantly innovating.
Re: GitHub issue - resolved
#65HN should really have a “Down HN” category, as this is the most reliable place to get this information.
I find downdetector to be quite reliable. You can pick up on a spike of reports very quickly. HN though comes with all the commentary.
Except for ISPs. Whenever a major website goes down, people blame their ISPs. When their own provider goes down, they don't remember which one they use and blame every other one in their region as well.
Re: GitHub issue - resolved
#66Earlier quoted context omitted.
I find downdetector to be quite reliable. You can pick up on a spike of reports very quickly. HN though comes with all the commentary.
Except for ISPs. Whenever a major website goes down, people blame their ISPs. When their own provider goes down, they don't remember which one they use and blame every other one in their region as well.
Hahah yes. It’s useless for tracking my ISP. Luckily my ISP is super nerdy and respond within minutes on their dslreports forum.
Re: GitHub issue - resolved
#67Earlier quoted context omitted.
I understand the point you're making here, but I feel it is being made in an effort to prove hakanderyal technically wrong rather than to evaluate the practicality of single points of failure, which is what they're trying to promote. I this this conversation would be much more helpful and insightful if it was kept on that evaluation track rather than trying to have a final word.
I don't think "GitHub is down" threads are known for the quality of their conversation, but sure. I also agree with reducing (increasing?) single points of failure. I'm not trying to be pedantic, but rather observing that in practice, it's not nearly as easy as spinning up a backup Git server (which is already hard enough). Maintaining two classes of build infrastructure throughout all your dependencies is probably n…
True, but there are other ways to go about it. Rather than trying to challenge someone's setup, which (I assume, apologies if incorrectly) you aren't familiar with, you can start by asking them about the setup and how they keep it independent from GH. Let them expose either the success of the endeavor or its shortcomings. Such an approach is a constructive one, whereas trying to challenge someone is an antagonistic approach. We're all in this together, so let's keep our discussions constructive, and focus on learning from each other rather than try to tear each other down.
Re: GitHub issue - resolved
#68Earlier quoted context omitted.
I'm sure your scale is similar.
Google search is basically never down. AWS is basically never down. WhatsApp is basically never down. Time for GitHub to grow up?
Great question: Google's homepage revenue is directly 1:1 matches to its uptime. Its user retention is also loosely tied to its uptime, as the value is mostly a replaceable commodity (is Bing worse? sure, but it has results). This leads to the organization investing huge amounts of time and money in ensuring its uptime. I can recall a single outage in the past several years.
On the other hand, GitHub's revenue is mostly monthly/annual licensing and their have great stickiness as it's not trivial to migrate to an equivalent service provider (excluding minor projects who only use a couple of features). They can increase profits through feature development and cost saving, a lot more than through uptime. Is there a limit to this? Of course.
Re: GitHub issue - resolved
#69Earlier quoted context omitted.
I'm sure your scale is similar.
Google search is basically never down. AWS is basically never down. WhatsApp is basically never down. Time for GitHub to grow up?
Google loses money when search is down because they can not serve ads. Does Github actually lose money when they are down? I think that because everyone is on subscription they do not lose money by the second, rather instead they lose reputation and long term they could lose customers, but Github's income isn't quite as sensitive to downtime as Googles in general, thus less investment in DevOps in comparison.
Re: GitHub issue - resolved
#70https://www.githubstatus.com/incidents/52z0j6phhnjs
Seems better done than a lot of status pages, runs on separate infra, updated, has a way to subscribe, etc. However, saying "degraded performance" when you know it's "down for everyone" is an industry phrasing thing that's irritating. AWS also has "elevated response times" when everyone is seeing 5xx errors, or infinite response times.
It seems accurate to me - after some time, several "degraded performance" flags have been changed to "major outage".