CDN is not choosing the best datacenter

cdn

#1

My server is in Argentina, but instead of using the local datacenter, all my requests are being handled by the Miami’s, which obviously has a much higher ping rate (125ms).

The Buenos Aires’ datacenter is operational (https://www.cloudflarestatus.com/).

How can I make the requests to be handled by my local datacenter, or at least one nearer (Brazil and Chile also have their own datacenters)?

You can check the CDN trace in http://www.avellanedaauntoque.com/cdn-cgi/trace

Thank you


#2

Two questions:

Which plan are you on?

Try opening both your website’s (www.avellanedaauntoque.com/cdn-cgi/trace) and https://www.cloudflare.com/cdn-cgi/trace and, if it works, https://1.1.1.1/cdn-cgi/trace and posting the content.


#3

Matteo. thank you for your quick response.
I’m on a free plan.

As you can see next, the other requests go correctly to the EZE datacenter, located in Buenos Aires.

  1. avellanedaauntoque
    fl=17f134
    h=www.avellanedaauntoque.com
    ip=190.111.205.77
    ts=1541526800.908
    visit_scheme=http
    uag=Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36
    colo=MIA
    spdy=off
    http=http/1.1
    loc=AR
    tls=off
    sni=off

  2. cloudflare
    fl=44f22
    h=www.cloudflare.com
    ip=190.111.205.77
    ts=1541526800.415
    visit_scheme=https
    uag=Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36
    colo=EZE
    spdy=h2
    http=h2
    loc=AR
    tls=TLSv1.3
    sni=plaintext

  3. 1.1.1.1
    fl=44f40
    h=1.1.1.1
    ip=181.164.207.131
    ts=1541526801.638
    visit_scheme=https
    uag=Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36
    colo=EZE
    spdy=h2
    http=h2
    loc=AR
    tls=TLSv1.3
    sni=off


#4

I imagine that due to some circumstances in that specific POP they are restricting traffic from low-tier plans.

Unfortunately I don’t know anything about those issues. Maybe @cloonan can check internally and confirm.


#5

Thank you @matteo. I hope it’s not a billing problem, since this behaviour is exactly the opposite than the reason CDN’s are built for…


#6

It’s not a billing problem, it’s a problem in the fact that since you are a free user they have no obligation to keep replying from every POP. If one is congested the higher-tier plans will take precedence and they will kick free domains for the time needed.


#7

I am not even 100% sure its just pricing\problems, there is some data centers that available to only some isp… for example in my country only something like 20% of requests go to the country datacenter all other not supported isp go to europe


#8

Yeah, that is due to ISP’s routing though. They maybe don’t interconnect where Cloudflare is present, or they are at maximum load and move the traffic to another location.


#9

Do you know if is there any metric in CF regarding how many requests are handled by each datacenter?


#10

Not that I know of, not publicly for sure!


#11

the closest thing I know of is: Analytics -> Geography -> DNS
its only show dns query but its should be close enough(in percentage)


#12

I have also faced this problem and I believe, we can’t do anything for this. This problem may be limited to certain ISP, I would suggest checking on the different ISP.


#13

There is a similar Topic earlier discussed. You may check