News for hackers. Stuff that matters.

A comment on Route Leak Impacting Cloudflare. Parent comment

Re:Route Leak Impacting Cloudflare by monkin on Monday June 24, 2019 @07:22AM (#20262310)
It's not their fault as accidents happen to everyone. You should be prepared for such a scenario and for many others too.
[ Parent | on HN ]
Re:Route Leak Impacting Cloudflare by dajonker on Monday June 24, 2019 @07:31AM (#20262394)
You are right, accidents happen to anyone. I cannot really be prepared for Cloudflare to go down though. What are my alternatives? Turn it off and route traffic to our servers directly? The DNS propagation takes longer than it just took for our website to be available again.
[ Parent | on HN ]
Re:Route Leak Impacting Cloudflare by jasongill on Monday June 24, 2019 @07:36AM (#20262432)
It shouldn't - Cloudflare keeps the TTL for their cache-enabled records very low (like 300 seconds).

If you just log in to Cloudflare and click the "orange cloud" icon on the DNS tab, which points the domain back directly to your origin, you'll see the site up within a couple minutes.

[ Parent | on HN ]
Re:Route Leak Impacting Cloudflare by yjftsjthsd-h on Monday June 24, 2019 @10:32AM (#20263876)
Is 300 very low? I've occasionally seen 60 in the wild.
[ Parent | on HN ]
Re:Route Leak Impacting Cloudflare by jasongill on Monday June 24, 2019 @10:36AM (#20263906)
It's very low compared to 24 hours, which is what used to be the most common setting and that (among other factors) was a big part of the "DNS propagation takes forever" mentality
[ Parent | on HN ]