Live data from Hacker News

Github: Major Service Outage

status.github.com

61–70 of 80 posts

Re: Github: Major Service Outage

#61

Nothing against Github but this probably highlights the real benefit of DVCS: setting up multiple remotes for your repo. Manage it probably and when one service goes down, fall back to Bitbucket or another service. It would limit the potential damage these attacks could cause, given the reliance dev teams have on pushing code to a central repo. Taking down a site like Github has a fairly clear effect on the productiv…

Multiple remotes are easy. Three lines in the config to push to Github and Bitbucket. Which is great if you rely on either service. It's everything else - hooks, wiki, issues, etc. - that get overlooked.

Re: Github: Major Service Outage

#63
post #51

/enqueue jokes about decentralized DVCS systems being hosted centrally... Srsly tho, the relationship between Git and GitHub, might be somewhat analogous to that of BitTorrent and TPB

Fortunately since you have an entire copy of the repository it doesn't really matter. Your team can just push the latest copy to another remote like Bitbucket and start using that.

Well, except for Issues, Pull Requests, Wiki, etc, but those aren't part of Git.

Re: Github: Major Service Outage

#64
post #59
post #34

First off, as others have said, disabling port 80 is a great way to handle this, I don't really care that much if I can see/use github the website for a few hours, but I'd be much more upset if I couldn't pull my code. Secondly, I kind of like when big sites go down when I'm not in desperate need because it means a really nice aftermath write up is on the way. Can't wait to hear more about this one.

> "disabling port 80 is a great way to handle this" It's been a disaster for a bunch of people I know. git is distributed by nature so they all had extra remotes they could use. github's issues and other project metadata wasn't distributed, since that's github's alone. So all of the friends of mine who are corporate github users who were using git in a distributed style (a minority of their overall customer base, I w…

The web app is also available on port 443, which every "corporate github user" should have been using anyway.

Re: Github: Major Service Outage

#65
post #50

Why do people always post on Hacker News whenever Github is offline? It's not going to make Github go online any quicker. They have a Twitter account, you know.

can we please try not to become slashdot, with the "this doesn't belong here!!" comments on every post.

Re: Github: Major Service Outage

#66
post #32
post #24

Earlier quoted context omitted.

This is correct. They needed ~90 dynos to keep up with about 500 qps on their status page in the last outage. Source: http://news.ycombinator.net/item?id=4524489

Should probably throw a Fastly or CloudFlare cache in front of a single dyno.

That would suggest people in charge know what they're doing.

Re: Github: Major Service Outage

#67

They said they're under a DDoS attack https://twitter.com/github/statuses/259029493669310464

Nearly every reasonably popular site on the internet gets DDoSed. It's embarrassing that Github goes down every time they're targeted.

Honestly, grow a pair, fellas. It's part of doing business on the Internet.

Re: Github: Major Service Outage

#69
post #36

Earlier quoted context omitted.

Who DDOS'es twitter? Mercurial committers? the Bitbucket people?

I heard once about a tire shop that drummed up business by strewing nails along the highway around it. Somewhere outside America; India or Thailand or somewhere else. Anyway, that kind of business practice wouldn't get you far in the Western world, so it seems unlikely. OTOH, if I had a botnet and I wanted to see how powerfully it could DDOS without drawing a lot of mainstream media attention, github might be good fo…

OT: the urban legend about tire shops putting nails in the neighborhoods' is very widespread. I have heard about it in at least three countries, and I recall my school teacher telling me about it in '91.

I sort of expect it wouldn't be an effective practice anywhere.

Re: Github: Major Service Outage

#70
Cheatsheet for continuing work when Github is down:

    1) ssh myserver.com
    2) adduser git
    3) sudo su git
    4) cd $HOME
    5) mkdir .ssh
    6) Add people's public keys to .ssh/authorized_keys (in /home/git)
    7) git init --bare myrepo.git
    8) Push and pull to git@myserver.com:myrepo.git
Voila!
Post reply on HN