#Why My Custom Domain on Cloudflare Routes to the Wrong Colocation ?

3 messages · Page 1 of 1 (latest)

limpid elbow
#

I have a free Cloudflare plan for my domain and I’m using both Pages and Workers. On Pages, I have set up the custom domain deplit.tech, and on Workers I added the route *.deplit.tech.

When I visit - https://deplit.tech/cdn-cgi/traceor https://<subdomain>.deplit.tech/cdn-cgi/trace it shows the colo as SIN (Singapore), even though I’m in India.

By contrast, visiting https://unpkg.com/cdn-cgi/trace shows DEL (Delhi), and using my Pages app’s default URL: https://deplit.pages.dev/cdn-cgi/trace shows BOM. This mismatch forces traffic through farther data centers and increases latency for my domain.

Why is Cloudflare routing my custom domain to the wrong colo?

Tried domains with COL from the same device and same network

https://deplit.tech/cdn-cgi/trace - SIN (Singapore) ❓️❓️
https://zaggonaut.deplit.tech/cdn-cgi/trace - SIN (Singapore) ❓️❓️
https://deplit.pages.dev/cdn-cgi/trace - BOM (Mumbai) ✅

https://unpkg.com/cdn-cgi/trace - DEL (Delhi) ✅
https://cloudflare.com/cdn-cgi/trace- BOM(Mumbai) ✅
https://developers.cloudflare.com/cdn-cgi/trace: AMD (Ahmedabad) (nearest to my location) ✅
https://blog.cloudflare.com/cdn-cgi/trace: BOM (Mumbai) ✅

mental valley
#

not all datacenters are available to free plans because of load and cost

limpid elbow
#

Is this really the case here because I haven't found that in any docs or pricing page ?