Issue: Off-routing of DNS impacting GEO-routing of CDN.
When issue happens: If I use 184.108.40.206 DNS in Android 9, or Win 10 Network Adapter settings
When issue doesn’t happen: With Android 220.127.116.11 app. I don’t want to use this app.
[quote=“user3996, post:6, topic:228574”]
I do not use Cloudflare CDN at all.[/quote]
Thank you very much for the feedback so this is then a DNS Resolve Issue.
They recently updated a important part of their Software Backbone.
My Understanding is that this New Quicksilver Software Solution is causing the DNS and Rerouting Problems i and others had.
I do like what Cloudfare offer with Workers very much.
If my website gains more Popularity i even plan to upgrade from PRO to Bussines Plan to support Cloudflare.
For the moment my Website need get more popular and regain my old SEO Rankings so i am stuck at the moment with PRO Plan.
What were the reasons for the switch and where did you go ?
Think from performance point of view and Price / Value Cloudfare is a own class and unbeatable.
There is nobody who provide this Value for the Price the offer.
I cant imagine there is anyone nearly offering the same for the same Price.
You hvae to be however skilled to use Cloudfalre maximal.
A most important reason: Poor routing for Indian traffic for Free, Pro and Business Plan. I have experienced this problem on regular basis for past five years.
BunnyCDN, I switched here because it has 3 PoPs here and works fine.
It was a sad decision to leave Cloudflare “CDN” services for which I was familiar with its UI for a long time, but then I also wanted a solution that offers guaranteed regional routing. Enterprise plan was a solution for prioritised routing, but that’s something I can’t afford.
I would be more than happy to see if Cloudflare discontinue free plan and focus on quality routing instead for Indian customer, maybe that helps in maintaining a fair balance for every customer.
It’s sad to see that many commercial sites making a profit are using free plan while it’s clear that Free Plan is for evaluation purpose only. Probably, weak policy implementation has led to such an effect.
lets hope the problems with 18.104.22.168 DNS Resolving problem get solved fast too.
A lot of people report problems since about 10 Days when using 22.214.171.124 as a resolver direct in their Network Settings without to use any app just 126.96.36.199. as a DNS Resolver instead 188.8.131.52.