[0]: https://blog.cloudflare.com/the-deep-dive-into-how-verizon-a... [1]: https://web.archive.org/web/20190628223129/https://blog.clou...
Cloudflare Network Performance Issues
121–130 of 329 posts
Seems fitting that Cloudflare spoke so aggressively against Verizon[0][1] last week and then this incident happens to them. I will be interested to read the postmortem on this situation. I really like Cloudflare but you should be careful not to jinx yourself with blogs posts like that.
Re: Cloudflare Network Performance Issues
#1227,5% of all websites... https://w3techs.com/technologies/details/cn-cloudflare/all/a...
9.6% of websites that have one of those CDNs
Re: Cloudflare Network Performance Issues
#123Re: Cloudflare Network Performance Issues
#124After trolling Verizon curious what reasons they will come with for that outage.
Care to elaborate how they were "trolling" Verizon?
Re: Cloudflare Network Performance Issues
#125Back for me.
Re: Cloudflare Network Performance Issues
#126A 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.
Re: Cloudflare Network Performance Issues
#127Even getting this error coming up in Android Studio trying to sync Gradle.
Anyone got a good Android NFC tutorial I can read up on with working code examples?
Re: Cloudflare Network Performance Issues
#128It seems to be up for me now in AMS.
Re: Cloudflare Network Performance Issues
#129Seems like it is clearing up. Our site is backup. Digital Ocean and Patreon are up as well.
Re: Cloudflare Network Performance Issues
#130Good. 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 don't think there is another cheap & easy to administer way, or more people would be doing that. Also CF is nice for the slight protection it provides against obvious bots and mass hacking attempts. And decreasing requests for static page resources. And it also (as long as your website doesn't leak its own ip, i.e. not sending emails except through Received-path-scrubbing services) hides your ip somewhat, meaning if you're careful you can run a website from your home on a raspberry pi without any issues.