GitHub experiencing a large DDoS attack

I do not understand why GitHub get attacked so often - honestly it's not like they are doing anything wrong, they are a fabulous service and the go-to place for most (if not all) developers for all sorts of projects, be it open source or in an enterprise/corporate context.

Just a PSA Git is distributed, fire up a quick instance with git daemon.<p>git daemon --verbose --export-all --base-path=.git --reuseaddr --strict-paths .git&#x2F;

Can someone with experience mitigating an attack like this describe how it&#x27;s done? A known set of hosts&#x2F;address spaces is fine, but it&#x27;s the &quot;distributed&quot; part I don&#x27;t understand how to deal with.

This is getting really problematic. It stops our whole team every time.<p>Anybody has experience with Gitlab and Gitlab CI? How&#x27;s the flow compared to Github, especially for pull requests, commenting and collaboration?

Why is this happening to them almost every day? Is someone jealous? Proving a point? If so, what point?<p>Surely by now, GitHub must know who&#x27;s responsible and putting more in place to mitigate as much as possible before this happens. Right?

<a href="http://sd.keepcalm-o-matic.co.uk/i/keep-calm-and-commit-locally.png" rel="nofollow">http:&#x2F;&#x2F;sd.keepcalm-o-matic.co.uk&#x2F;i&#x2F;keep-calm-and-commit-loca...</a>

I wonder if there is a way to work with git offline, and then synchronize later? &#x2F;sarcasm

while git is distributed, Github managed to centralize the open source culture

I ask because I have no plausible answer: What does someone stand to gain by DDoSing github?

Let me get this straight, the command-line interface for googling code in a locally cloned GitHub repo is called grep?

What a coincidence. We actually just finished migrating all our projects over to GitLab about an hour before this outage.<p>I still very much love GitHub, it just ended up not scaling for us (we have a lot of repositories that seldom needs to be touched, which results in a $20 &#x2F; month Linode + Backup being a much better solution)<p>GitLab also allows us to group repositories and gives a little bit more flexibility in regards of git server-hooks. Also, server-side branch locking! (Does anybody know how to lock branches server-side with GitHub?)

Snarky comments about distributed version control aside, the bigger problem is the ecosystems which revolve around GitHub. Two which are immediately screwing my day up are Composer and Homebrew. Currently, both are totally dependent on GitHub.

Github enterprise works great.

What&#x27;s with DDoSing GitHub? Special place in Hell...

Let&#x27;s all take a watercooler break here at HN

Time to read up on `git send-email`, I suppose.

15:50 UTC: We are working to mitigate a large DDoS. We will provide an update once we have more information.

You git what you pay for.<p>(Actually, there are long established yet less high profile alternatives with decent features and better pricing for commercial teams, like beanstalk or unfuddle or codebasehq. No hip cred, but for example supporting archived projects that you can read w&#x2F;o using up your repo count license.)

Seems to be a recurring problem for them now.

Why in hell is anyone so pissed with GitHub?

Appears to be loading fine now.

Just a thought, but it would be interesting if there was a DDoS attack on the github status page. Then what would we do?

Curious though -- yesterday it was the NYTimes, today github, Apple a few weeks before that. Pretty high profile stuff in my opinion.

So what?