That’s fucking insane.... Probably a double post; sorry in advance... I just have to express my anger and amazement for a second.

Angry that they didn’t use such a high powered DDoS attack against say... Facebook or some shit like that, amazed at the sheer size of that attack...

I kinda wanna touch it.

What amazed me even more is that GitHub didn't give a fuck and handled it extremely well !

@MeanStreet Hell yes they did!

Why github of all places?
DDoS sum random trump site or something .-.

@MeanStreet I don't follow or use github, how did they handle it?

any website like government or political, nope they ddos github, retard. still 1.3 Tb is quite incredibly.

@incognito they rerouted their traffic within 10 mins to an anti-ddos server that filtered out the bad requests. Normal traffic could still go through, but the ddos traffic was stopped by the anti-ddos. Handled very well and the ddos stopped after 13 minutes I think.

@mcorr so ddosing is pretty pointless these day as theres methods just to reroute it no matter how big the attack, 5 years ago im pretty sure a 1.3Tb ddos would of shut half the internet down lol now websites just shrug it off like nothing.

But that really makes you think... we rely on GitHub so much, how many projects would stop working and how many teams will be unable to continue on working if it goes down for a couple of days?

@Kryptic0 yeah exactly. I think the max capacity of the ddos handlers is around 10tb/s, like 7 times what this ddos was

Is the size based on the botnet?

@Kodeus in this case they apparently didn't use a botnet I think? They pinged some cache servers or something from spoofed ip addresses. The request to the cache servers was small, but then the cache servers sent a request to GitHub that was very large, so it amplified the attacker's computing power. Usually though, a bigger botnet means more computing power and a higher gb/s

@mcorr Thank you! But how can a cache server transforms a small request to a bigger one?

@Kodeus the cache sends a different request that is bigger I believe? I'm not an expert on this, so I might be wrong. Basically, the ddoser sends a simple request to get a file from the cache server, then the cache server makes a new request, with a lot more data, to github

@mcorr Ah okay. I thought that it was more complicated

Just google: "amplification attack" and thy shall learn.

@Lahsen2016 true, i was more thinking about big websites.

This was really sick man, It is a new world record in itself.

wish facebook was hit with a 1.3Tb attack

@Wiciaki large projects and large teams are more inclined to use enterprise so they would be unaffected.

But ya, a few projects back we basically had the day off with Gitlab going down.

I almost miss that day using bitfucket, even offline Gitlab is still more useful than that retarded pile of useless fuck shit.

'I kinda wanna touch it' 😆

I think GitHub instigated it themselves for PR.

It worked.

@ParkCity we should launch one (jk @notNSA)