Live data from Hacker News

Cloudflare Network Performance Issues

cloudflarestatus.com

161–170 of 329 posts

Re: Cloudflare Network Performance Issues

#162
post #95

A 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.

Problem is not just about using Cloudflare as your DNS registrar really. Even if you have a different registrar, the Cloudflare model is to have the NS (nameserver) records set up to point to Cloudflare, and then they in turn resolve the DNS. You cannot really use Cloudflare without that set up. Changes to nameservers at a registrar level are rarely quick, at least quick enough to mitigate a disaster like this. It's why we've used two completely different domains at Ably (ably.io and ably-realtime.com) for all services we provide.

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

#163
post #95

A 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.

we were able to recover by submitting an API call rather than their UX, it was slow but the API requests work

Re: Cloudflare Network Performance Issues

#166
post #120

Earlier 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.

The lookup is essentially random. If you point DNS to 2 IP's and one of those goes down, then (without going into detail) half of your requests will fail.

Re: Cloudflare Network Performance Issues

#167
post #95

A 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.

No good if your Registrar (Namecheap) is behind CF as well!

Re: Cloudflare Network Performance Issues

#170
post #142
post #72

Good. 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…

CYA buddy, CYA

(sarcasm!)

Post reply on HN