On 3 March 2013 12:02, Nick Hilliard <[email protected]> wrote: > On 03/03/2013 10:46, Arthur Wist wrote: >> Apparently due to a routing issue... > > back up again: http://blog.cloudflare.com/todays-outage-post-mortem-82515 > > tl;dr: outage caused by flowspec filter tickling vendor bug.
Definitely smart to be delegating your DNS to the web-accelerator company and a single point of failure, especially if you are not just running a web-site, but have some other independent infrastructure, too. >>>>>>CloudFlare's 23 data centers span 14 countries so the response took some >>>>>>time but within about 30 minutes we began to restore CloudFlare's network >>>>>>and services. By 10:49 UTC, all of CloudFlare's services were restored. >>>>>>We continue to investigate some edge cases where people are seeing >>>>>>outages. In nearly all of these cases, the problem is that a bad DNS >>>>>>response has been cached. Typically clearing the DNS cache will resolve >>>>>>the issue. Yet, apparently, CloudFlare doesn't even support using any of their services with your own DNS solutions. And how exactly do they expect end-users "clearing the DNS cache"? Do I call AT&T, and ask them to clear their cache? http://serverfault.com/questions/479367/how-long-a-dns-timeout-is-cached-for C.
