It's another thing to see it actually play out how you'd hope.'ĭespite the unprecedented power wielded by such an attack, it can still be mitigated, according to Akamai researchers, who say that setting up a rate limit on port 11211 – the default port used by memcached – is the way to go about it.

'So I would have been certain that we could handle 1.3 Tbps, but at the same time, we never had a terabit-and-a-half come in all at once. 'We modelled our capacity based on fives times the biggest attack that the internet has ever seen,' Josh Shaul, vice president of web security at Akamai told WIRED.

The site was able to survive the attack thanks to Akamai's DDoS mitigation service, which took over within minutes of being alerted about the attack, rerouting the barrage of traffic from GitHub to its scrubbing centres, WIRED reported. It was an amplification attack using the memcached-based approach described above that peaked at 1.35 Tbps via 126.9 million packets per second.' 'The attack originated from over a thousand different autonomous systems (ASNs) across tens of thousands of unique endpoints. 'Between 17:21 and 17:30 UTC on February 28, we identified and mitigated a significant volumetric DDoS attack,' GitHub said in a blog, which was posted after the attack was mitigated. Yet, GitHub survived the attack almost unscathed and experienced only a few minutes of sporadic downtime. The attack on GitHub surpassed even the 2016 massive DDoS attack against Dyn, which peaked at 1.2 Tbps and shut down internet services across the US. US Marine Forces data leak: Sensitive info of over 21,000 people exposed

Ddos ip github