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

Red Squares – GitHub outages as contributions

red-squares.cian.lol

Post reply on HN
Print view View original

161–170 of 175 posts

Re: Red Squares – GitHub outages as contributions

#161

Post by bastardoperator »

dijit wrote: post #76
u_fucking_dork wrote: post #61

Every time one of these vibe coded meme sites gets posted there’re endless comments about how it’s not actually because of load, the GitHub team is shit, their tech stack is shit, Microsoft is shit, Azure is shit, etc. Just compare the GitHub status page for public GitHub vs the enterprise cloud pages. Enterprise has much better numbers and I’ve personally can’t remember the last time there was an outage that prevent…

> 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…

Wrap it up, this guy doesn't like the database (they use two), azure is terrible despite being the cash cow for msft, and OP could easily build a more scalable scm service with their pinky and half their brain because they know better then thousands of engineers. I don't know whats more comical, GH going down everyday, or watching bros trying to flex.

Re: Red Squares – GitHub outages as contributions

#162

Post by user_7832 »

jrumbut wrote: post #94
ahstilde wrote: post #77

Earlier quoted context omitted.

yup! When i did an analysis last month, GitHub is up 89.3% on weekdays and 96.5% on weekends. Incidents touch 62% of weekdays and 11% of weekends. Claude shows the same pattern: 92.5% weekday, 97.8% weekend. Tuesday through Thursday is the danger zone. Sunday is practically a different service. https://www.aakash.io/tech-chase/github-and-claude-are-down-...

I had an occasion recently where I was working a lot of late nights/early mornings with AI use. And I'd be getting these instant, beautiful responses, and then, as soon as the sun started coming in the windows, it would take longer and fail more, and by the time the clock struck 9 AM, every LLM had turned back into a pumpkin.

Which service(s) were you using, if you don't mind sharing?

I'm curious if most of the big players including eg Google do this thing of nerfing models or it's limited to more "smart" (read: black box models like ChatGPT.

Re: Red Squares – GitHub outages as contributions

#165

Post by sarchertech »

prepend wrote: post #135
sarchertech wrote: post #55

Earlier quoted context omitted.

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%.

This is coming from github’s status page. You need to reconcile memory of downtime with github’s official record. I’ve been using github pretty much daily since 2010 and I never had a push fail or a repo be unavailable until recently.

I can tell you that graph is full of shit because you can go back through recorded incidents here

https://www.githubstatus.com/history

And immediately find that there are numerous incidents that would show up on the modern status board as an issue but are reported with 100.00000% uptime on that graph.

One example:

https://www.githubstatus.com/incidents/bzj1hc2cnfkc

2018-07-16 17:32:53 - We are investigating reports of elevated error rates.

2018-07-16 17:34:27 - We are investigating reports of service unavailability.

2018-07-16 18:04:38 - We've discovered the issue causing connectivity failures and are remediating.

2018-07-16 18:26:48 - We're monitoring the site as systems recover. Some delays are expected as we process backlogged data.

2018-07-16 18:37:26 - We're continuing to monitor and work on further remediation efforts as the site recovers.

2018-07-16 18:54:21 - The site is stable. We are continuing to monitor and work through follow-up remediation efforts.

And there are other incidents with connection failures or elevated error rates during July 2018, but the linked graph shows "average uptime of all components 100.00000%" during July 2018.

Another from October (that also shows 100.0000% uptime)

2018-10-21 23:09:19 - We are investigating reports of elevated error rates.

2018-10-21 23:13:31 - We are investigating reports of service unavailability.

2018-10-21 23:43:55 - We're investigating problems accessing GitHub.com.

2018-10-22 00:05:37 - We're failing over a data storage system in order to restore access to GitHub.com.

2018-10-22 00:23:54 - We're continuing to work on migrating a data storage system in order to restore access to GitHub.com.

2018-10-22 00:43:12 - We continue to work on migrating a data storage system in order to restore access to GitHub.com.

2018-10-22 01:02:49 - We continue to migrate a data storage system in order to restore full access to GitHub.com.

2018-10-22 01:22:22 - We continue to work to migrate a data storage system in order to restore access to GitHub.com.

2018-10-22 01:41:19 - We are continuing to work to migrate a data storage system in order to restore access to GitHub.com.

>I’ve been using github pretty much daily since 2010 and I never had a push fail or a repo be unavailable until recently.

Looking back at their downtime history. Unless recently is within the last 3 years, it seems like you got really lucky.

Re: Red Squares – GitHub outages as contributions

#167

Post by etruong42 »

linsomniac wrote: post #101
dijit wrote: post #76

Earlier 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…

Your story (and the other posts commenting on lack of intellectual curiosity) fits into a larger model of the world that I prescribe to. Being labeled "well-known" or "smart" doesn't seem to require intellectual openness anymore. In fact, openness seems to be penalized. Being open means potentially exposing yourself to scenarios where you are not the smartest/authoritative, and that reduces your authority, so you avoid those scenarios to preserve your authority. Even when you are not "the authority", being open could be a threatening signal to the authority, where you and your "openness" could be a vector that introduces ideas/scenarios that reduces their authority. So long as authority is solidified by this lack of openness, actually being open could limit your career potential.

Seeing this happen in real time is helping me understand how authoritarian regimes/institutions/movements rise to power.

Re: Red Squares – GitHub outages as contributions

#169

Post by tiagod »

u_fucking_dork wrote: post #61

Every time one of these vibe coded meme sites gets posted there’re endless comments about how it’s not actually because of load, the GitHub team is shit, their tech stack is shit, Microsoft is shit, Azure is shit, etc. Just compare the GitHub status page for public GitHub vs the enterprise cloud pages. Enterprise has much better numbers and I’ve personally can’t remember the last time there was an outage that prevent…

I don't find your conclusion that obvious. They could also be deploying changes to their regular infrastructure before updating enterprise, shielding it from some mistakes.

Re: Red Squares – GitHub outages as contributions

#170

Post by pojzon »

ahstilde wrote: post #77
sd9 wrote: post #9

Weekends are the untapped frontier. Still room to scale.

yup! When i did an analysis last month, GitHub is up 89.3% on weekdays and 96.5% on weekends. Incidents touch 62% of weekdays and 11% of weekends. Claude shows the same pattern: 92.5% weekday, 97.8% weekend. Tuesday through Thursday is the danger zone. Sunday is practically a different service. https://www.aakash.io/tech-chase/github-and-claude-are-down-...

Inference results for Copilot are also a lot better during weekends than workdays. Its my personal experience so take it with a grain of salt, but I work on personal projects only on weekends mostly due to that brain drain mon-fri of copilot.
Post reply on HN