Cloudflare Network Performance Issues
161–170 of 329 posts
Re: Cloudflare Network Performance Issues
#162A great example for why you shouldn't transfer your domain to Cloudflare Registrar if you're also using their CDN. Those who have transferred their domains cannot change DNS servers to mitigate the outage.
Yeah, I'm regretting that very choice now.
We wrote about a strategy to circumvent this sort of thing a little while back https://www.ably.io/blog/routing-around-single-point-of-fail.... Given two incidents in a matter of weeks, I think a revisit of that article in light of most businesses who operate on a single domain would be useful :)
Re: Cloudflare Network Performance Issues
#163A great example for why you shouldn't transfer your domain to Cloudflare Registrar if you're also using their CDN. Those who have transferred their domains cannot change DNS servers to mitigate the outage.
Re: Cloudflare Network Performance Issues
#164Re: Cloudflare Network Performance Issues
#165Re: Cloudflare Network Performance Issues
#166Earlier quoted context omitted.
No, dns doesn't work like this, you can't have backup records.
Not necessarily backup records, but you can add multiple A/AAAA records. There is no guaranteed order though. It is possible to have multiple A/AAAA records pointing to different loadbalancers, but I don't know how browsers would deal with this.
Re: Cloudflare Network Performance Issues
#167A great example for why you shouldn't transfer your domain to Cloudflare Registrar if you're also using their CDN. Those who have transferred their domains cannot change DNS servers to mitigate the outage.
Re: Cloudflare Network Performance Issues
#168Re: Cloudflare Network Performance Issues
#169Re: Cloudflare Network Performance Issues
#170Good. I'm tired of people not learning that trusting a single gateway with 50% of the internet is bad. Yes, I know, free DDOS protection. There has to be another way of doing this, some mesh based DDOS protection or so.
This seems like a case for putting more of the internet through a single gateway. Having my downtime correlated with everyone else's means users will be more forgiving because they'll perceive it as "the Internet's down" rather than "lkbm's site is broken". (We saw this with CloudFlare. Some users were pissed, and others jumped in with "it's not their fault; AWS is down". That doesn't happen when our stuff specifical…
(sarcasm!)