Live data from Hacker News

Cloudflare Network Performance Issues

cloudflarestatus.com

101–110 of 329 posts

Re: Cloudflare Network Performance Issues

#101

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?

This is a good question.

I'm not sure if the browser receives all A/AAAA records from the syscall, or just one. I guess that if the browser has the whole list, and the error is in the 500 range, it could retry a different IP but I'm not sure if browsers do this.

Re: Cloudflare Network Performance Issues

#107
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 :/

I think the only option here would be to change our name servers at registrar level to point to AWS and recreate all DNS records there, but then you have to deal with name server propagation.

Re: Cloudflare Network Performance Issues

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

Down detectors down lol.
Post reply on HN