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

GitHub was down

github.com

Post reply on HN
Print view View original

181–190 of 288 posts

Re: GitHub was down

#181

Post by x86a »

thund wrote: post #39
cortesoft wrote: post #18

Earlier quoted context omitted.

There is always going to be SOME delay between the outage and the status page, although 5 minutes is probably enough time where it should be updated

after several minutes the status page is still showing all is fine. For a service like GH, anything more than 30 secs is unacceptable

That is very unrealistic. Infrastructure monitoring at that scale won't even be collecting metrics at that interval.

And simple HTTP monitoring would be too flappy for a public status page.

Re: GitHub was down

#183

Post by dataspun »

rvz wrote: post #119
sebmellen wrote: post #7

I've never seen an outage this big. Even the homepage doesn't load. We've had recurrent issues with Actions not running, but this seems a lot bigger. The status page says all is well, though: https://www.githubstatus.com/ . Hilarious.

Looks like we have a full house outage at GitHub with everything down. Much worse than the so-called Twitter / X recent speed-bump that was screeched at and quickly forgotten. I don't think GitHub has recovered from the monthly incidents that keeps occurring. Quite frankly it is the expectation that something will go down every month at GitHub which shows how unreliable the service is and this has happened for years.…

statute of limitations for HN comment predictions is 3 years.

Re: GitHub was down

#184

Post by mvdtnz »

willchen wrote: post #116

I'm wondering why this isn't on the front page? It has a lot of points in 23 minutes.

HN has a strange philosophy built into its ranking algorithm that an item with a large number of comments early on should be de-ranked because the conversation is likely to be of poor quality.

Re: GitHub was down

#186

Post by zacym »

Aug 14, 2024 - 23:29 UTC Update - We are experiencing interruptions in multiple public GitHub services. We suspect the impact is due to a database infrastructure related change that we are working on rolling back.

Re: GitHub was down

#188

Post by cropcirclbureau »

nox101 wrote: post #151
weystrom wrote: post #99

A reminder of how centralized and dependent the whole industry has become on GH, which is ironic, considering that git itself is designed to be decentralized. Good opportunity to think about mirroring your repos somewhere else like Gitea or Gitlab.

They're already mirrored on my hard drive. That's how git works.

Github is more than a remote host for git repositories. It's become one of the major CDNs for software distributions. Github Pages host a majority of static sites that developer use. You won't be able to use Cargo, Nix, Scoop and other package managers right now because their registries have a critical dependency hosted on Github.

This is not to mention all the projects that rely on Github for project management, devops, community and support desk.

GitHub is also very international, I doubt isolated netziens like those from China are shielded from this outage. I imagine very, very few software shops are unscathed by this. The whole affair is very on brand for 21st century software which is to say pitiful.

Re: GitHub was down

#189

Post by sunrunner »

bitbasher wrote: post #14

The timing is pretty uncanny. I just deployed a github page and had a DNS issue because I configured it wrong. I hit "check again" and github went down. Hope I don't appear in the incident report.

Perhaps this is a repeat of the Fastly incident with a customer's Varnish cache configuration causing an issue in their systems (I think this is a rough summary, I don't remember the details).

So, you're both responsible and not responsible at the same time :)

> Hope I don't appear in the incident report.

Appearing in an incident report with your HN username could be pretty funny...

Re: GitHub was down

#190

Post by Zambyte »

nox101 wrote: post #151
weystrom wrote: post #99

A reminder of how centralized and dependent the whole industry has become on GH, which is ironic, considering that git itself is designed to be decentralized. Good opportunity to think about mirroring your repos somewhere else like Gitea or Gitlab.

They're already mirrored on my hard drive. That's how git works.

The key difference is being able to mirror communication channels. While you can continue to work fine with your local repo, the only way to share those changes are via another forge, or sending patches through some other channel. Having another forge to distribute code is generally more ideal.
Post reply on HN