GitHub is down again • Hacker News Board

Re: GitHub is down again

#191

Post by demothrowaway » Mon, Feb 09, 2026, 5:01 PM UTC

charles_f wrote: post #75

That pink "Unicorn!" joke is something that should be reconsidered. When your services are down you're probably causing a lot of people a lot of stress ; I don't think it's the time to be cute and funny about it. EDIT: my bad, seems to be their server's name.

Even if it is their server name, I completely agree with your point. The image is not appropriate when your multi-billion revenue service is yet again failing to meet even a basic level of reliability, preventing people from doing their jobs and generally causing stress and bad feeling all round.

Re: GitHub is down again

#192

Post by jakub_g » Mon, Feb 09, 2026, 5:01 PM UTC

hnthrowaway0315 wrote: post #52

stefankuehnel wrote: post #49

You can literally watch GitHub explode bit by bit. Take a look at the GitHub Status History; it's hilarious: https://www.githubstatus.com/history .

Someone should make a timeline chart from that, lol.

https://updog.ai/status/github

Re: GitHub is down again

#193

Post by esafak » Mon, Feb 09, 2026, 5:02 PM UTC

Culonavirus wrote: post #21

Azure Screen of Death?

Kids don't even know this. Lucky them.

Re: GitHub is down again

#194

Post by aloisdg » Mon, Feb 09, 2026, 5:02 PM UTC

jbpadgett wrote: post #45

3 outages in 3 months straight according to their own status history. https://www.githubstatus.com/history

Sure it is not vibe coding related

Re: GitHub is down again

#195

Post by Zetaphor » Mon, Feb 09, 2026, 5:03 PM UTC

ewuhic wrote: post #113

pimpl wrote: post #74

What are good alternatives to GitHub for private repos + actions? I'm considering moving my company off of it because of reliablity issues.

Don't listen to the clueless suggesting Gitlab. It's forgejo (not gitea) or tangled, that's it.

Can you offer some explanation as to why Forgejo and Tangled over Gitlab or Gitea?

I personally use Gitea, so I'd appreciate some additional information.

Re: GitHub is down again

#196

Post by nozzlegear » Mon, Feb 09, 2026, 5:03 PM UTC

gowld wrote: post #179

hnthrowaway0315 wrote: post #52

Earlier quoted context omitted.

Someone should make a timeline chart from that, lol.

Light work for an LLM

But not Copilot.

Re: GitHub is down again

#197

Post by koreth1 » Mon, Feb 09, 2026, 5:04 PM UTC

The biggest thing tying my team to GitHub right now is that we use Graphite to manage stacked diffs, and as far as I can tell, Graphite doesn't support anything but GitHub. What other tools are people using for stacked-diff workflows (especially code review)?

Gerrit is the other option I'm aware of but it seems like it might require significant work to administer.

Re: GitHub is down again

#198

Post by jcdcflo » Mon, Feb 09, 2026, 5:04 PM UTC

zurfer wrote: post #32

to be fair, i think usage has increased a lot because of coding agents and some things that worked well for now can't scale to the next 10x level.

Maybe they need to sort things out for people who pay through the nose for it cause I ain't comforted by vibe coders slowing us down.

Re: GitHub is down again

#199

Post by swiftcoder » Mon, Feb 09, 2026, 5:04 PM UTC

arcologies1985 wrote: post #96

throw_m239339 wrote: post #72

Earlier quoted context omitted.

Wait a minute, isn't Git supposed to be... distributed?

Issues, CI, and downloads for built binaries aren't part of vanilla Git. CI in particular can be hard if you make a multi-platform project and don't want to have to buy a new mac every few years.

Probably Worth taking an honest look at whether your CI could just be an SQS queue and a Mac mini running under your desk though

Re: GitHub is down again

#200

Post by literallyroy » Mon, Feb 09, 2026, 5:05 PM UTC

estimator7292 wrote: post #180

jsheard wrote: post #120

Earlier quoted context omitted.

They're in the process of moving from "legacy" infra to Azure, so there's a ton of churn happening behind the scenes. That's probably why things keep exploding.

I don't know jack about shit here, but genuinely: why migrate a live production system piecewise? Wouldn't it be far more sane to start building a shadow copy on Azure and let that blow up in isolation while real users keep using the real service on """legacy""" systems that still work?

That’s a safer approach but will cause teams to need to test in two infrastructures (old world and new) til the entire new environment is ready for prime time. They’re hopefully moving fast and definitely breaking things.