If I upgrade to the Pro plan, will that give me access to Sydney / Melbourne Australia DCs/Edge Nodes?

#1

This is listed on the Pro plan page:

“Global Content Delivery Network (CDN) Improve latency and performance with location-based access to your website using our 165 data centers located around the globe.” https://www.cloudflare.com/plans/pro/

But I was told it wouldn’t due to the high bandwidth charges to Australia. https://blog.cloudflare.com/the-relative-cost-of-bandwidth-around-the-world/

I just found these 2 blog posts down below now from a quick Google search. Since caching can mean 2 different things here, I just wanted some clarification on how Cloudflare routes and fetches requests when you first set it up without static content caching at the edge nodes.

1. What this blog post down below refers to, it’s not content caching, but requests rerouting to Cloudflare’s servers (when the orange cloud is enabled in the DNS tab) which then go back to the origin to fetch all dynamic content if a static rule isn’t setup for static HTML content.

What does Cloudflare actually cache by default on standard setting? From looking at DevTools, it seems like it stores a copy of all content at 2 of CF’s IP addresses (hosts), but those IP addresses / servers then fetch content there and then from the origin, hence the double slow down there as well.

2. FULL Static HTML/CSS/JS caching with a Page Rule where requests don’t hit back to the origin? (I’ve tried several WordPress static site generators, but none are working with my Elementor.com Page Builder, so I’m relying on Cloudflare here to pull through with full static page caching).

Some more transparency around affected performance in Australia from Cloudflare would have been nice. There’s no mention of which countries are used for the Pro plan, so I’m assuming it’s all countries by that marketing play… can some CF Engineer please confirm before I decide to commit?

I’ve been using Cloudflare for 6 years, I joined with the premise of having a faster site loading experience, but it’s honestly not the case for free users in Australia or neighbouring countries for that fact.

The only real value here is free automatic SSL (which Let’s Encrypt offers too, but I haven’t had the need to set it up since I’ve always used CF) and Page Rule Redirects for www. redirections or http to https is pretty easy (and caching if it works), but that can all be done in Nginx or Apache as well if you have any server admin experience or don’t mind learning.

CF just makes it easy and puts it all in one GUI console place. :slight_smile: Just ironic the performance isn’t there for Australians (at least on free) which is the primary reason of why people use a CDN and it isn’t warned for Australian users when they go to use it.

Thank you.

https://www.digitalpacific.com.au/blog/is_cloudflare_making_your_website_slower/

0 Likes

#2

I think it’s Business and above.

1 Like

#3

Yeah, that’s what I got from reading the comments in that Cloudflare article too. I wish it was outlined somewhere in the plans. Something Cloudflare could definitely improve on.

I noticed Keycdn.com and stackpath.com (previously MaxCDN) seem to support all PoP regions, and KeyCDN charges like $0.10/GB for first 2TBs bandwidth. https://www.keycdn.com/pricing .

My sites are quite small in traffic, I can’t warrant yet afford the steep USD $200/ month bill just to use local PoPs. There are cheaper alternatives that do what I want though. (I know Australia’s ISPs are basically the worse in the business, they aren’t very open to peering or NBN talks either and love to rip off loyal customers, and it doesn’t help that we’re on an island with expensive submarine leasing bandwidth costs).

I haven’t set up another CDN yet though. If I use Cloudflare as just DNS (grey cloud), will it still keep my page rules active or will I have to redo all of that on the server level with Nginx like forcing HTTPS redirects and www to root domain redirect? And Let’s Encrypt for SSL.

0 Likes

#4

:grey: disables Cloudflare services, including page rules.

0 Likes

#5

Thought so, so just DNS & Analytics remains with grey cloud. Thanks!

0 Likes

#6

One thing I find unbelievable though apart from the price is that apparently each plan is for EACH site/URL. That is hella expensive, especially if all you want to do is a 301 redirect, but I suppose that’s more easier to setup at the server level if you’ve done it before there, and 301 redirects don’t need any CDN support, but the Page Rule, it’s just 1 overseas request, it wouldn’t diminish speed at all. Barely noticeable I’d take it.

I’ve always just relied on page rules for that and CNAMEs.

They should have a look at https://webflow.com/pricing pricing model. They have both plan and account level pricing.

0 Likes

#7

like you said you don’t need cloudflare for 301…

but they considered to be really really cheap, you get most of the security stuff at the free plan…
even the 20$\200$ is really cheap for what you get

0 Likes

#8

I would get the Pro version if it meant Aussie PoPs were covered, but they’re not.

0 Likes

#9

are you getting this pop when visiting one of this sites?

0 Likes

#10

I’m also in Australia and followed this change when it was made (wasn’t always the case, by the way) and it was because Telstra et al weren’t open to peering arrangements which made it expense to give away the bandwidth on the free/cheaper plans. I agree that it would have been nice to have on ‘Pro’ but maybe it just wasn’t supportable financially. Must have been a reason because the free stuff is normally pretty free-flowing.

One thing I do just as a matter of my own personal design philoshophy is have all my assets served from their own subdomain- assets.example.com. If you had a similar approach you could ‘grey-cloud’ that CNAME to remove Cloudflare from the mix on delivering bigger items (even route that subdomain via an alternative CDN) and so still keep all the benefits of Cloudflare on the rest of your domain (Page Rules, Firewall Rules, workers etc) even if you don’t want to use them completely. Obviously this is hard if you use a CMS but if you’re using your own code it’s not too much of a change.

1 Like

#11

It really depends on the specific Australian ISP/IP routes. I have cloudflare free, had pro and now also have business plans and all my Telstra cable internet access and my Brisbane, Sydney and Melbourne VPN access to my cloudflare sites go and hit Australian Cloudflare POP/servers for me for free, pro and business. Some folks report they don’t so hard to say exactly if they do not.

Say in theory if only 25-50% of Australian IP visitors hit Cloudflare POP/servers, that is still upto 50% better than without Cloudflare still ! :slight_smile:

0 Likes