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

GitHub is down again

githubstatus.com

Post reply on HN
Print view View original

361–370 of 425 posts

Re: GitHub is down again

#361

Post by mynameisvlad »

munk-a wrote: post #349
Anon1096 wrote: post #345

Earlier quoted context omitted.

> It looks like they are down to a single 9 at this point across all services That's not at all how you measure uptime. The per area measures are cool but the top bar measuring across all services is silly. I'm unsure what they are targeting, seems across the board it's mostly 99.5+ with the exception of Copilot. Just doing math, 3 (independent, which I'm aware they aren't fully) 99.5 services brings you down to an o…

It depends whether the outages are overlapped or not. If the outages are not overlapped then that is indeed how you do it since some of your services being unavailable means your service is not fully available.

I mean, there's a big difference between primary Git operations being down and Copilot being down. Any SLAs are probably per-service, not as a whole, and I highly doubt that someone just using a subset of services cares that one of the other services is down.

Copilot seems to be the worst offender, and 99% of people using Github likely couldn't care less.

Re: GitHub is down again

#362

Post by shimman »

tapoxi wrote: post #4

Is it really that much better than alternatives to justify these constant outages?

Yes, for personal projects I just self-host an instance of forgejo with dokploy. Everything else I deploy on codeberg, which is also an instance of forgejo.

Re: GitHub is down again

#363

Post by lelanthran »

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.

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

Dunno about actions[1], but I've been using a $5/m DO droplet for the last 5 years for my private repo. If it ever runs out of disk space, an additional 100GB of mounted storage is an extra $10/m

I've put something on it (Gitea, I think) that has the web interface for submitting PRs, reviewing them, merging them, etc.

I don't think there is any extra value in paying more to a git hosting SaaS for a single user, than I pay for a DO droplet for (at peak) 20 users.

----------------------

[1] Tried using Jenkins, but alas, a $5/m DO droplet is insufficient to run Jenkins. I mashed up shell scripts + Makefiles in a loop, with a `sleep 60` between iterations.

Re: GitHub is down again

#364

Post by throwaway5752 »

showerst wrote: post #7

If you'd have asked me a few years ago if anything could be an existential threat to github's dominance in the tech community I'd have quickly said no. If they don't get their ops house in order, this will go down as an all-time own goal in our industry.

This is Microsoft. They forced a move to Azure, and then prioritized AI workfloads higher. I'm sure the traing read workloads on GH are nontrivial.

They literally have the golden goose, the training stream of all software development, dependencies, trending tool usage.

In an age of model providers trying train their models and keep them current, the value of GitHub should easily be in the high tens of billions or more. The CEO of Microsoft should be directly involved at this point, their franchise at risk on multiple fronts now. Windows 11 is extremely bad. GitHub going to lose their foundational role in modern development shortly, and early indications are that they hitched their wagon to the wrong foundational model provider.

Re: GitHub is down again

#365

Post by jeffrallen »

12_throw_away wrote: post #262
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 .

14 incidents in February! It's February 9th! Glad to see the latest great savior phase of the AI industrial complex [1] is going just as well as all the others! [1] https://www.theverge.com/tech/865689/microsoft-claude-code-a...

At this point they are probably going to crash their status system. "No one ever expected more than 50 incidents in a month!"

Re: GitHub is down again

#366

Post by toastal »

babo wrote: post #183
sgt wrote: post #136

Earlier quoted context omitted.

Is there any reason why Github needs 99.99% uptime? You can continue working with your local repo.

As an example, Go build could fail anywhere if a dependency module from Github is not available.

Does go build not support mirrors so you can define a fallback repository? If not, why?

Re: GitHub is down again

#367

Post by twistedpair »

MattIPv4 wrote: post #2

Status page currently says the only issue is notification delays, but I have been getting a lot of Unicorn pages while trying to access PRs. Edit: Looks like they've got a status page up now for PRs, separate from the earlier notifications one: https://www.githubstatus.com/incidents/smf24rvl67v9 Edit: Now acknowledging issues across GitHub as a whole, not just PRs.

I cannot approve PRs because the JSON API is returning HTML error pages. Something is really hosed over there.

Re: GitHub is down again

#368

Post by chrisandchris »

12_throw_away wrote: post #262
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 .

14 incidents in February! It's February 9th! Glad to see the latest great savior phase of the AI industrial complex [1] is going just as well as all the others! [1] https://www.theverge.com/tech/865689/microsoft-claude-code-a...

An interesting thing I notice now is that people do not like companies that only post about outages if half the world have them ... and also not companies that also post about "minor issues", e.g.:

> During this time, workflows experienced an average delay of 49 seconds, and 4.7% of workflow runs failed to start within 5 minutes.

That's for sure not perfect, but there was also a 95% chance that if you have re-run the job, it will run and not fail to start. Another one is about notificatiosn being late. I'm sure all others do have similar issues people notice, but nobody writes about them. So a simple "to many incidents" does bot make the stats bad - only an unstable service the service.

Re: GitHub is down again

#369

Post by toastal »

ajross wrote: post #269
sgt wrote: post #136

Earlier quoted context omitted.

Is there any reason why Github needs 99.99% uptime? You can continue working with your local repo.

I think this is being downvoted unfairly. I mean, sure, as a company accepting payment for services, being down for a few hours every few months is notably bad by modern standards. But the inward-looking point is correct: git itself is a distributed technology, and development using it is distributed and almost always latency-tolerant. To the extent that github's customers have processes that are dependent on service…

Being snapshot-based. Git has some issues being distributed in practice since the patch order matter which means you basically need to have some centralized authoritative server in most cases with more than 2 folks to resolve the order of patches for meaningful uses as the hash is used in so many contexts.

Re: GitHub is down again

#370

Post by stevekemp »

bartread wrote: post #148
showerst wrote: post #7

If you'd have asked me a few years ago if anything could be an existential threat to github's dominance in the tech community I'd have quickly said no. If they don't get their ops house in order, this will go down as an all-time own goal in our industry.

Yeah, I'm literally looking at GitLab's "Migrate from GitHub" page on their docs site right now. If there's a way to import issues and projects I could be sold.

If you're considering moving away from github due to problems with reliability/outages, then any migration to gitlab will not make you happy.
Post reply on HN