Re:How LulzSec kept itself safe during the summer of 'lulz'
by damoncloudflare on Tuesday February 28, 2012 @02:49PM
(#3644641)
Hi,
We only force a site direct if the attack is too large & starts to impact other customers as well. If the attack doesn't impact other customers, then we won't force the site direct (we generally only force a few sites direct per week & these are monster attacks).
Re:How LulzSec kept itself safe during the summer of 'lulz'
by mr-ron on Tuesday February 28, 2012 @02:58PM
(#3644691)
How was it that the Lulzsec attacks were not as large? What qualifies a sufficient size attack?
Re:How LulzSec kept itself safe during the summer of 'lulz'
by damoncloudflare on Tuesday February 28, 2012 @02:54PM
(#3644667)
Also:
Clarifying that forcing direct does not mean a null route. Forcing direct = going direct to the site's server (we still resolve the DNS).
Re:How LulzSec kept itself safe during the summer of 'lulz'
by girlvinyl on Tuesday February 28, 2012 @03:57PM
(#3644939)
Yes. This happened to our site as well. Cloudflare buckled and sent a "sorry, can't handle it" email.
Re:How LulzSec kept itself safe during the summer of 'lulz'
by andrewthornton on Tuesday February 28, 2012 @02:49PM
(#3644636)
This is very true as I saw it first hand around the very same time.
Correct me if any of this inaccurate, but last I checked it was not.