OMG it's a secret message!
Red Squares – GitHub outages as contributions
131–140 of 175 posts
Re: Red Squares – GitHub outages as contributions
#132Earlier quoted context omitted.
> the GitHub team is shit, their tech stack is shit 1) Criticism of being unable to achieve service is not a fault of the individual; it simply is a fault of the system. You can criticise the system, it's permissible. Especially if they have more resources than many countries and some of the best tech talent in the world on staff. 2) Their tech stack is shit, and they've gone on record for years defending it, quite a…
>not intellectually curious or open This checks out. I once was at a conference where they (Azure) had a giant booth. A fairly well known person in the community brings me over to talk to his manager who is working the booth. "We should hire him, he's really smart." Within a minute of talking to this manager he says "You're a Linux guy? We do Windows." and physically turns away from me, conversation over. You know, f…
Re: Red Squares – GitHub outages as contributions
#133Re: Red Squares – GitHub outages as contributions
#134I wonder how well this corolates with azure incidents. Especially for the US regions.
I live in Europe. I've not noticed these constant outages. But I only use GitHub after work.
Re: Red Squares – GitHub outages as contributions
#135Earlier quoted context omitted.
They were sucking 5 years ago before agents existed. I don’t think this has anything to do with recent changes. https://damrnelson.github.io/github-historical-uptime/
That’s nonsense. GitHub didn’t have 100% uptime before 2020. I remember downtime back then. And Microsoft didn’t make changes that fast. The only thing that changed is the accuracy of their status page. Also go back and look at the unofficial status page from 3 years ago. It’s regularly above 99% and has been dropping steadily since then. Then in the last 3 months has dropped to below 85%.
I’ve been using github pretty much daily since 2010 and I never had a push fail or a repo be unavailable until recently.
Re: Red Squares – GitHub outages as contributions
#136Re: Red Squares – GitHub outages as contributions
#137Earlier quoted context omitted.
Whoa, if that is even remotely accurate then the talk about agents is a complete red herring.
If I remember correctly the status page was not precise before the acquisition - so take with a big grain of salt the 100% pre-acquisition values
I don’t like this whole casting of doubt upon sources without providing superior or even alternate sources.
It makes it hard to discuss when one person presents a source and another says “I’m not sure that is accurate.” In a vague way.
What am I supposed to do with that? Research more sources that may or may not align with how you feel?
Re: Red Squares – GitHub outages as contributions
#138Earlier quoted context omitted.
I suspect it’s caused because Microsoft is using buggy Microsoft tech instead of the original stack. They’re making political decisions based on what they sell vs what’s actually useful for their use case. It’s kind of impossible to find out if this is true though.
That doesn’t track because GitHub Enterprise Cloud has great uptime. This is all load based, vibe coded ai slop code shipped at record numbers from users who will never convert to paid. The real question is what are they doing about that?
Re: Red Squares – GitHub outages as contributions
#139This idea has been around! I made this one in January to help slice and dice uptime by incident category. https://isgithubcooked.com
Re: Red Squares – GitHub outages as contributions
#140LOL! Perfect. one change request: brighter should be more intense. Right now the more intense days are dark red and to a color blind person like me, that doesn't pop out.