Cloudflare not routing through nearest datacentre

Recently, it takes around 1.5s just to connect to the site through Cloudflare. My server is hosted in Singapore. By right, Cloudflare should be routing me through Singapore’s server as I access my site from Singapore.

However, this is the trace:

fl=4f444
h=mydomain.com
ip=################
ts=1589724275.319
visit_scheme=https
uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.138 Safari/537.36
colo=SJC
http=http/2
loc=SG
tls=TLSv1.3
sni=plaintext
warp=off

As you can see, it’s routing me through San Jose, California, which is wayyy across the pacific ocean.

Meanwhile, if I go cloudflare.com’s trace, I get:

fl=35f488
h=cloudflare
ip=#############
ts=1589724335.979
visit_scheme=https
uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.138 Safari/537.36
colo=SIN
http=http/2
loc=SG
tls=TLSv1.3
sni=plaintext
warp=off

It correctly routes through Singapore’s server. Is the routing for cloudflare’s nearest CDN only available on paid plans?

How do I get my site routing correctly? As it stands, it loads really slow.

I have seen this article before. Still, I have been routed through Singapore’s server before, but it randomly switches to San Jose, California. Does this mean I’ll sometimes get sub 1s load times with Cloudflare and 2+s load times on Cloudflare randomly?

If your ISP routes you that way, then I am afraid yes.

Alright… is there a better method to speed up load times while achieving the same obscurity and CDN caching capabilities that Cloudflare provides?

If the latency to Cloudflare is your main issue, then there is not much you can do. You could try to upgrade to a paid plan where routing might be better.

Check this to see if upgrading your plan might help:
https://cloudflare-test.judge.sh/

This website shows me that my site is being routed through Singapore’s data center even on the freeplan, but when I access my site through domain##/cdn-cgi/trace I get San Jose California as the routing data center.

That shouldnt be the case as that site uses the same information. However you said it randomly switches, so that request will simply have gone through Singapore and then you have other requests going through the US.

I suppose it really is up to the ISP whether they want to route my traffic through San Jose or Singapore depending on their load and costs. This however, results in wildly varying response times.

Not sure if switching to a paid Cloudflare plan fixes this since the free plan says it routes through Singapore but doesn’t anyway. Not sure if a paid plan, which also says Singapore, will exhibit similar behaviour.

Can you post a screenshot of https://cloudflare-test.judge.sh?

Hmm… no idea why my first ping is so high as well.

Thats just a sub-set, but it seems they all go to SIN.

It’s basically SIN all the way down for all sites tested. No idea why my website routes to SJC randomly sometimes… I guess I’ll have to live with random 2s latency.

This topic was automatically closed after 30 days. New replies are no longer allowed.