WIRED
GitHub Survived the Biggest DDoS Attack Ever Recorded
On Wednesday, a 1.3Tbps DDoS attack pummeled GitHub for 15-20 minutes. Here's how it stayed online.
Recently shared by
![‽ [Interrobang] Media](https://res.cloudinary.com/refind-inc/image/facebook/w_200,h_200,c_fill,q_auto,f_auto,d_refind:avatar.png/10155970354085948 "‽ [Interrobang] Media")
More like this
TechCrunch
The world’s largest DDoS attack took GitHub offline for less than tens minutes
TechCrunch
1 min read · From 2018 · In a growing sign of the increased sophistication of both cyber attacks and defenses, GitHub has revealed that it weathered the largest-known DDoS attack in..
TNW
How GitHub braved the world's largest DDoS attack
TNW
3 min read · From 2018 · On February 28, GitHub found its code hosting platform hit by what's believed to be the largest Distributed Denial of Service (DDoS) attack ever recorded - and lived to tell the tale.
ZDNet
AWS said it mitigated a 2.3 Tbps DDoS attack, the largest ever
ZDNet
2 min read · 2020-06-17 · The previous record for the largest DDoS attack ever recorded was of 1.7 Tbps, recorded in March 2018.
TNW
Massive DDOS attack against Dyn DNS is causing havoc online [Resolved]
TNW
4 min read · From 2016 · A massive DDOS attack against a popular upstream DNS provider is screwing up the Internet today.
CoinDesk
Bitcoin Gold Website Down Following DDoS Attack
CoinDesk
4 min read · From 2017 · A website that serves as a central hub for a newly created cryptocurrency project went down today shortly after a successful, scheduled launch.
The Verge
Amazon says it mitigated the largest DDoS attack ever recorded
The Verge
1 min read · 2020-06-18 · An attack with a perviously unseen volume of 2.3 Tbps
githubengineering.com
February 28th DDoS Incident Report
githubengineering.com
3 min read · From 2018 · On Wednesday, February 28, 2018 GitHub.com was unavailable from 17:21 to 17:26 UTC and intermittently unavailable from 17:26 to 17:30 UTC due to a distributed denial-of-service (DDoS) attack. We understand how much you rely on GitHub and we know the availability of our service is of critical importance to our users. To note, at no point was the confidentiality or integrity of your data at risk. We are sorry for the impact of this incident and would like to describe the event, the efforts we’ve t
