Comments on: CloudFlare goes down, cites router issue in DDoS attack http://gigaom.com/2013/03/03/cloudflare-goes-down-cites-dns-outage/ Wed, 22 May 2013 09:47:54 +0000 hourly 1 http://wordpress.com/ By: 12over7 http://gigaom.com/2013/03/03/cloudflare-goes-down-cites-dns-outage/#comment-1332356 Sun, 28 Apr 2013 18:37:21 +0000 http://gigaom.com/?p=616266#comment-1332356 Blame a DDoS attack??? Give me a break! This is another example of network engineering MIA. Various tests are part of the design process prior to a release being pushed to the production environment. I wouldn’t be pointing finger’s at the Juniper SE. No, whoever is responsible for network engineering at CloudFlare needs to have their a!! handed to them. I’d put them in “Herding Cats” in the below referenced article:

http://www.networkperformanceinnovations.com/blog/where-are-you-along-the-network-service-design-continuum/

]]> By: easydns http://gigaom.com/2013/03/03/cloudflare-goes-down-cites-dns-outage/#comment-1317494 Mon, 04 Mar 2013 18:58:09 +0000 http://gigaom.com/?p=616266#comment-1317494 “Given that the number of DDoS attacks is on the rise, web sites had better gird themselves and hope their security vendors are taking proactive steps to keep ahead of the problem.”

If anybody was using our proactive nameservers ( https://web.easydns.com/proactive.nameservers/ ) then they wouldn’t have felt a thing as our system would swap in their hot spares while the outage lasted and then put their regular nameservers back once cloudflare was back up again.

Given that any DNS provider is vulnerable to these types of episodes, using multiple providers with hot backups and some active monitoring and on-the-fly switching, it makes sense.

]]>