Hmm i find the report a bit disappointing, besides mentioning how long the attack lasted, and that different providers restored DNS(edit, auto spellcheck failure) responses to a regular response time at different times, it says very little.
Where did the attack originate from? What was the actual attack 'request'? How many queries per second were there at the point of failure? Why do you tell cloudflare about all your traffic? (yes i don't like cloudflare or sites hosted via/by/proxied etc)
as someone who has dyn dns through them for my home network .. I definitely noticed the slow down in response time.. takes 45 seconds to login to my teamspeak server now. Most of that time is caught up in resolving the domain.
4 comments
[ 2.7 ms ] story [ 26.7 ms ] threadWhere did the attack originate from? What was the actual attack 'request'? How many queries per second were there at the point of failure? Why do you tell cloudflare about all your traffic? (yes i don't like cloudflare or sites hosted via/by/proxied etc)
http://dns.he.net
http://wwww.dnsmadeeasy.com
http://www.cloudflare.com
http://www.dnspark.com
http://www.dyn.com
There is a good site that tracks performance http://www.dnsperf.com.