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.<p>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.
They said they're under a DDoS attack <a href="https://twitter.com/github/statuses/259029493669310464" rel="nofollow">https://twitter.com/github/statuses/259029493669310464</a>
01:41 PM PST<p>We've temporarily disabled service on port 80 while we investigate the source of a connection flood. HTTPS, GIT, and SSH service are unaffected.<p>01:33 PM PST<p>"We are experiencing issues due to a DDOS attack, working hard to restore service"
Cheatsheet for continuing work when Github is down:<p><pre><code> 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
</code></pre>
Voila!
/enqueue jokes about decentralized DVCS systems being hosted centrally...<p>Srsly tho, the relationship between Git and GitHub, might be somewhat analogous to that of BitTorrent and TPB
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.<p>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 productivity of a lot of their users.
Why do people always post on Hacker News whenever Github is offline?<p>It's not going to make Github go online any quicker. They have a Twitter account, you know.
Github status: "We've temporarily disabled service on port 80 while we investigate the source of a connection flood. HTTPS, GIT, and SSH service are unaffected."<p>Great way to keep the git push/pull workflow unaffected.
Github.com is now up <a href="https://github.com/" rel="nofollow">https://github.com/</a><p><a href="https://status.github.com/" rel="nofollow">https://status.github.com/</a>
<a href="https://twitter.com/AnonymousOwn3r" rel="nofollow">https://twitter.com/AnonymousOwn3r</a> is taking credit for attacks against YouTube and GitHub amongst others.
Github status is hosted on Github, d'oh. Their Twitter feed posted at 2037Z: "We are experiencing issues due to a DDOS attack, working hard to restore service..." <a href="https://twitter.com/github/status/259029493669310464" rel="nofollow">https://twitter.com/github/status/259029493669310464</a>
The internet is collapsing folks. YouTube is down as well: <a href="http://news.ycombinator.com/item?id=4670859" rel="nofollow">http://news.ycombinator.com/item?id=4670859</a>