"oh shit, here we go again"
Incident with Github.com [resolved]
581–590 of 1001 posts
Re: Incident with Github.com [resolved]
#582This is starting to feel like Twitter. For a variety of reasons, we had a centralized place where everyone of a particular set of persuasions could connect, and this had outsize benefits for the community as a whole. That place is becoming untenable, and with the loss of goodwill and stability, the community’s started to dissipate. But there isn’t one obvious transition candidate, so the diaspora is finding itself sp…
Personally I don't agree at all that these centralized monoliths are a good thing.
On the contrary, I believe it's been detrimental to the open internet and only serves to control us by the powerful.
I never trusted Github and never will.
Re: Incident with Github.com [resolved]
#583Earlier quoted context omitted.
The CTO said otherwise: https://github.blog/news-insights/company-news/addressing-gi...
https://damrnelson.github.io/github-historical-uptime/
First, that source is unreliable, particularly for before the acquisition. (We don’t know whether the data is accurate, it’s based on GitHub’s own self reporting.)
Secondly, the scale is WAY off and makes it look far worse than it is. It makes it look like 99.5% availability is practically zero availability.
Finally, GitHub’s availability is not a binary all-or-nothing proposition. They report incidents on a granular level, for example, webhook firing can be impaired while Git hosting may be working fine.
Re: Incident with Github.com [resolved]
#584Is there any scenario in which Github doesn't start yanking features out of the free tier to protect the core service for paying users?
Re: Incident with Github.com [resolved]
#585Earlier quoted context omitted.
Selection bias then as the majority of European companies are for sure not hosting their own Forgejo or GitForge.
Where I work we're hosting our own gitlab instance and the previous company I worked for hosted their own Bitbucket. For most developers I know it's either a self hosted git platform instance or Github enterprise.
[deleted]
Re: Incident with Github.com [resolved]
#586I don't understand why Github hasn't solved this problem with pricing updates. My understanding is they are getting hammered with LLM generated code growing their traffic by over an order of magnitude. So why not rate limit non-paying users and charge for whatever scarce resource is being consumed that is causing them to constantly fall-over? This seems like a basic economics problem.
I have wondered the same thing. Even a small fee like $50 a year would get rid of a lot of AI slop that justs eats up resources.
I would gladly pay that fee if it means Github is reliable for paying customers.
Re: Incident with Github.com [resolved]
#587Re: Incident with Github.com [resolved]
#588"degraded performance" is the new 2026 term to say that your platform is down unusable.
On my side it is funny,I'm encountering the following errors: "no server available to process your request".
Maybe azure is out of capacity in its datacenters... Or they didn't pay the server bill.
Re: Incident with Github.com [resolved]
#589I recall reading years ago that cloud services were expected to run with a reliability of 3 or 4 '9's and that if they didn't competing services would quickly overtake them in adoption. The industry was supposed to be that cut throat. Has big tech reached a similar status like banks in that they are "too big to fail" i.e. when they do fail we all just look the other way and say: "well everyone else is out too". Didn'…
People overestimate how much they care about stuff. Moving off GitHub would be more costly for us than having 5% downtime. Obviously there’s a tipping point, but it shows people are tolerant given the price tags.
Re: Incident with Github.com [resolved]
#590> We are seeing an approximate 20% error rate across numerous experiences including Pull Requests, Issues, and others. Investigations are currently under way and we will be posting updates as they become available Well it's 100% down for me, so does this mean 20% of all users are fully down?
If you load an issue page, you'll see 1 failed request to:
/project/product/issues/
/in-product-messaging/copilot-budget-request-banner
/in-product-messaging/code-scanning-ai-findings-preview-banner
/github-copilot/chat
/_private/browser/stats