Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Cloudflare Network Performance Issues

cloudflarestatus.com

Post reply on HN
Print view View original

151–160 of 329 posts

Re: Cloudflare Network Performance Issues

#151

Post by Avamander »

pmlnr wrote: 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.

With a lot of these things, if people can't agree to make a standard system to do all of it just as well then there's going to be a big company that does so. We have had this with e-mail, signed exchanges, DDOS protection and will probably have it with many other things unless people pull themselves together at least after these proprietary solutions are created and create better alternatives.

Re: Cloudflare Network Performance Issues

#156

Post by bovermyer »

pmlnr wrote: post #141
Waterluvian wrote: post #100

Earlier quoted context omitted.

I get your point. But I'm not sure I can ever grok the mindset of someone who thinks, "good, that'll teach 'em". Not sure I'd ever want to work with that individual.

Fair point. I'm wondering though, how else you make people understand something like this?

Education and positive reinforcement.

Teach people the right way to do things, and then make that behavior self-rewarding.

Re: Cloudflare Network Performance Issues

#157

Post by danShumway »

aclelland wrote: post #79
danShumway wrote: post #50

Don't want to go off topic, but if I want to prevent my website going down because of stuff like this in the future, will having back up DNS entries solve the problem? I know DNS will fall back if it can't reach a service, but would a 502 trigger that?

Yeah, you'll want to keep your domain registered through a different registrar and if CF goes down you can update your DNS Name Servers point from CF to something like AWS Route 53. This has a few drawbacks like making sure your Route53 configuration is identical to your CF config, ensuring your origin servers can cope with the additional load if CF caching isn't available and the DNS propagation time required for th…

Yeah, if I had access to the DNS records this would be easy, but like you said, even the dashboard is down.

Ideally, I'd want something where if Cloudflare goes down, I don't have to change anything, but... 502 isn't going to trigger that without some work on my part.

Meh.

Re: Cloudflare Network Performance Issues

#158

Post by chaz6 »

nullify88 wrote: post #131
dessant wrote: 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.

You can setup your domains using their CNAME method. You do not have to delegate your entire domain to them. https://support.cloudflare.com/hc/en-us/articles/36002061511... Together with a short TTL we were able to recover without relying on their dashboards.

Only if you are a paid customer. The free service does not allow this, and this is why I do not use Cloudflare for personal use.

Re: Cloudflare Network Performance Issues

#159

Post by vegardx »

dessant wrote: 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.

I'm guessing that they're going to be back up again before those changes can "propagate", given the relatively high TTLs most TLDs run with.
Post reply on HN