Live data from Hacker News

Cloudflare Network Performance Issues

cloudflarestatus.com

91–100 of 329 posts

Re: Cloudflare Network Performance Issues

#91
post #38

Earlier quoted context omitted.

For the site itself that's totally fine, and the status page is separate as it should be, too.

Fair. Some service recently had their status page hosted on the same server that went down, that was funny.

I guess it's like diversifying one's assets - you put your status page elsewhere than on your own infrastructure.

Re: Cloudflare Network Performance Issues

#92
post #9

Single point of failure - we all shouldn’t trust CF alone anymore...

Any CDN is a single point of failure and limits your availability to as low as three nines. Although anycast-based CDNs like Cloudflare are much less reliable than DNS-based CDNs, those can do orders of magnitude better.

Re: Cloudflare Network Performance Issues

#93
post #47

Earlier quoted context omitted.

Great, now we can't even disable HTTP proxy to allow traffic directly to AWS :/

Point your DNS back to your actual host? Might be the only short term solution, though DNS propagation times kinda rule that out :/

That's a no-go if you transferred your domains to Cloudflare Registrar.

Re: Cloudflare Network Performance Issues

#94
post #69
post #3

So it seems... Even https://cloudflare.com/ itself is down

More importantly, their admin dashboard is down. It's impossible to bypass their "orange cloud" proxies and send traffic directly to our hosting. That they can't flip a switch and have their nameservers send dash.cloudflare.com to a separate piece of redundant infrastructure is mind-boggling.

change the nameserver at the registrar to someone else

Re: Cloudflare Network Performance Issues

#97
post #94
post #69

Earlier quoted context omitted.

More importantly, their admin dashboard is down. It's impossible to bypass their "orange cloud" proxies and send traffic directly to our hosting. That they can't flip a switch and have their nameservers send dash.cloudflare.com to a separate piece of redundant infrastructure is mind-boggling.

change the nameserver at the registrar to someone else

By the time that change propagates, cloudflare will be backup

Re: Cloudflare Network Performance Issues

#98

So what should the ideal redundancy plan be here? If you can't log into the CDN provider and they are down do you you just have a second one ready (and paid for) and then log into your registrar and be ready to switch to that secondary CDN provider in this scenario? Or is there some sort of load balancing / routing solution between CDN's that I don't know about / understand?

If you use Cloudflare nameservers, you have to change to new nameservers, wait for that to propogate, and then wait for clients cached records TTLs to expire. So it will be a major disruption no matter what you do.

What about the API? If that is up, you could script it.

Re: Cloudflare Network Performance Issues

#100
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.

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.
Post reply on HN