Interestingly, GitHub seem's to be allowing logged-in users to access those pages, but using a incongnito tab shows unicorns. I'm guessing they've just disabled access for unauthenticated requests.
Does anybody have any wider context regarding this attack? Is it the first time a massive DDoS like that was mitigated, with just minor disruptions to the victim?
Not by a long-shot; this was reported as a big deal (and I'd love to have more insight and data available), but this kind of thing has been going on for many years.
Ask your local DNS admin for some war stories. :-)
[+] [-] timdorr|11 years ago|reply
[+] [-] snsr|11 years ago|reply
[+] [-] MollyR|11 years ago|reply
Update: its working now, but it was definitely not working earlier.
[+] [-] dak1|11 years ago|reply
Is this simply a temporary precautionary measure because of the initial JS DDOS, or has GitHub permanently taken those two repos down?
If it's the latter, then I'm really disappointed and it would seem the PRC was able to get what it wanted.
[+] [-] micah_chatt|11 years ago|reply
[+] [-] smurfpandey|11 years ago|reply
[+] [-] andor436|11 years ago|reply
[+] [-] remi|11 years ago|reply
[+] [-] ryannevius|11 years ago|reply
[+] [-] johnnyfaehell|11 years ago|reply
[+] [-] NamTaf|11 years ago|reply
https://status.github.com/messages
[+] [-] cotillion|11 years ago|reply
From a state sponsored attacker I would have expected to see a BGP attack..
[+] [-] f055|11 years ago|reply
[+] [-] lordbusiness|11 years ago|reply
Ask your local DNS admin for some war stories. :-)
[+] [-] zmk|11 years ago|reply
http://techcrunch.com/2015/03/19/anti-censorship-service-gre...
See links around this article, similar attacks have happened before:
http://www.netresec.com/?page=Blog&month=2015-03&post=China%...