Reddit is currently experiencing a malicious DDoS attack
twitter.com
twitter.com
If there's a malicious DDOS attack then this surge in legitimate traffic likely compounded the problem.
The update threads: [1] http://www.reddit.com/r/news/comments/1co395/live_updates_of... [2] http://www.reddit.com/r/news/comments/1cnwms/mods_removed_th...
Where the updates moved when reddit went down: [3] https://twitter.com/JpDeathBlade
But I wish it was :) Compounding I can deal with, astronomical is harder.
http://www.newstatesman.com/world-affairs/2013/04/reddit-bos...
Is there a recording of this? Because it sounds a lot like it never happened.
> @christiiinaaaxo @jaredleesmith @thejman218 Looks just like a kid from my area that went missing exactly a month and has yet to be found.
> I mean maybe it's a total coincidence but I'm more than a little freaked out by the resemblance. #Boston pic.twitter.com/Qsd6rj5v5l
At some point, the Internet ran with her speculation:
> It makes me sad that people are going to the Tripathi family Facebook page and writing nasty things. That was never my intention
And at around 4-5 am, the Boston police scanners said they were looking for Sunil. I remember this because I fell asleep at 5am thinking that this bizarre story involved Sunil and then woke up at 8 learning that two completely different suspects had been identified. From the twitterer:
> So if what I'm hearing is correct, at 3 AM when the police scanners said they had their suspect and it was Sunil, I was wrong.
The tweeter's account is now protected but she hasn't deleted her tweets. I think everyone, including her, has learned a little about making well-intentioned speculation on the Internet. But apparently, even the Boston police had been fooled (at least someone in the BPD was, which is why police scanners should not be taken as gospel)
Did you hear this yourself, or did you read it? That's really what I'm asking. I know many people were listening, but it's hard to tell what people heard first-hand and what people simply re-tweeted.
For my own peace of mind I'm trying to distinguish between two possibilities: a) that the names were not heard on the scanner at all and whole story was either a mirage or an intentional hoax, b) that someone's erroneous tip to the police was mistaken for its own confirmation.
Would the pictures, or the people in the pictures, be suspected of being bombers? Were the police looking for pictures or for people in pictures?
You don't like vigilantes, but you hope vigilantes are punishing reddit users?
Also, some of the highest upvoted threads and comments appear to be warning others of the potential negative consequences of their publicly pointing out everyone with a backpack or different coloured skin.
Reddit as a whole needs a better answer for that than just pointing out that it is just some small subreddit.
(I don't pretend to know what that answer is, and I guess it does have more to do with people choosing how to participate in online discussions than it does reddit, but reddit is well positioned to push that participation in a better direction)
Sorry about the snarky remark, but the headline does feel a tad redundant.
Getting Slashdotted or Hacker Newsed is definitely a distributed denial of service, but it's not so much an attack
I had a chuckle too about "malicious". A DDoS attack is a DDoS attack. It's like hearing about a "malicious stabbing."
But whatever, there are DDoS attacks every day on someone.
The best example off the top of my head was a D-Link firmware update which added an NTP server operated by a third party for "public use." This wound up increasing the NTP server's traffic by 90% and costing them over $8K/year in additional bandwidth fees. See [1].
Then you have so called "slashdotting." Or linking to a small web-site with an interesting story and overloading it with legitimate traffic until it goes down. See [2].
[1] http://en.wikipedia.org/wiki/NTP_server_misuse_and_abuse#D-L...
Sorry about being picky around semantics, but still: No point in throwing words around to the point where they become completely pointless.
It's all idle speculation, though.
if you look at their numbers[1] for 2012, it's plausible that they are simply overwhelmed during these bursts and they've judged it worthwhile to let these aberrations play out.
for many operations.. moving your availability from, say, 99.9% to 99.99% is simply not worth the cost.
uptime is hard; GitHub has only maintained 99.96% for the past month[2][3] (and, IMO, they're actively trying to improve it)
[1]: http://blog.reddit.com/2012/12/top-posts-of-year-and-best-of...
[2]: https://status.github.com/graphs/past_month
[3]: http://cl.ly/image/0O2S0L3O0l3J
edit: clean up links
edit2: learning \n
Also, what reason is there for a DDoS attack on Reddit right now?
you appear to be a bad robot
check out the rules for robots. thanks.That is basically what CloudFlare is.
Add in things like caches to prevent even valid requests from getting to the backend (so you've now added a CDN), and many peers to your network so that an attacker cannot saturate one or two peers... and you've got the essence of CloudFlare (sans features like optimising content for speedy delivery).
Ultimately the best defence to a DDoS is to be able to soak up the attack before it hits the backend, and to have enough spare capacity to keep serving regular traffic.
You can cache and distribute everything save for the valid requests to a dynamic resource (but even those you can optimise). So the whole game from a defensive point of view is to let nothing but valid dynamic requests through to the backend.
The attacker's side of a DDoS is about acquiring network capacity greater than your network capacity, identifying your weaker points (in an attempt to cause a domino effect, if they can take out a weaker peer then a stronger peer will need to do more work and itself becomes weaker). And then sending what appear to be valid requests without triggering an attack on themselves (having a 150 byte request respond with 100KB would wipe out the attackers). Bonus points for constructing requests that can get through to the dynamic resources on the site being attacked (as those are the weakest link).
The combination of adding caches and distributing those caches is to add a CDN.
You add caches to stop the request reaching a backend and doing the work twice, for optimisation. But in effect they become defensive shields as serving a static file or an in-memory file is less work and can be handled in far greater numbers than doing the work on the backend, and if one cache is attacked users accessing other caches elsewhere in the world continue to get their requests served.
If you then place a cache at every point at which your site is surfaced, for example you use DNS anycast to have your front-end appear to be surfaced from every Amazon datacenter and the closest one is nearly always selected... then you've helped stop requests at the first opportunity and to return them from a place which can handle far greater requests.
You've increase your network capacity, increased the ability to serve valid requests, and you've prevented all of that traffic reaching the backends.
And in doing all of this... placing caches for static resources throughout the world and using DNS anycast to return the cached item from the closest peer... well, you have created a CDN. A primitive one for sure, but it still is one.
Basically, DDoS Attacks can be (roughly) divided in 2 categories:
1. Attacks on your server (which usually target your server IP or some other part of your network infrastructure)
2. Attacks on your site (which use bots to flood your site with fake HTTP requests)
As explained above, Network attack can only be countered with strong and flexible infrastructure. The most common solution is a combination of several high-powered servers and load balancing capabilities.
HTTP DDoS attacks are trickier because they're best mitigated by visitor profiling, a technology that can help identify bots from humans and block them while still allowing providing full access to all legitimate visitors. Developing and maintaining such technology is arguably more complicated, simply because it's a software you need to create, not a hardware which you can buy.
Standard profiling solutions include CAPTCHAs and Delay Pages but these will also repel legitimate visitors. (because no one likes CAPTCHAs or waiting for 5-10 extra seconds for page load). Advanced profiling solutions use a combination of behavior and signature recognition, coupled with seamless challenges (i.e. checking for JS support).
CF and Incapsula (where I work) both handle Network DDoS in a similar manner but we have a somewhat different approach to HTTP DDoS.
And yes, while under DDoS (or even without it), dynamic resources can be the "weakest link". This is why WAFs are so important.
Either they've been doing a wonderful job with mitigation, or I'm missing something (I suppose I did miss a few hours while sleeping...). If anything I figured they're getting hammered with EST sunrise/Boston incident traffic...but a simultaneous malicious DDoS attack "beyond any shadow of doubt"? Wow