GitHub has explained how it was planning to tackle the kind of DDoS attack it had seen on Feb 28.
In a blog post, it said making its edge infrastructure more resilient to current & future conditions of the Internet & less dependent upon human involvement “requires better automated intervention.”
“We’re investigating the use of our monitoring infrastructure to automate enabling DDoS mitigation providers & will continue to measure our response times to incidents like this with a goal of reducing mean time to recovery (MTTR).
“We’re going to continue to expand our edge network & strive to identify & mitigate new attack vectors before they affect your workflow on GitHub.com.”
Between 17:21 and 17:30 UTC on February 28, GitHub had witnessed significant volumetric DDoS attack. The attack originated from over a thousand different autonomous systems (ASNs) across tens of thousands of unique endpoints. It was an amplification attack using the memcached-based approach described above that peaked at 1.35Tbps via 126.9 million packets per second.
To note, at no point was the confidentiality or integrity of users data at risk. GitHub said.
