Cloudflare routes me through the wrong continent
For a single account, cloudflare always routes me through there Ashburn DC (which can be confirmed by accessing the
/cdn-cgi/trace path, despite both me and the origin server being located in germany
This increases the response time 10x in comparison to non-proxy mode, other websites using cloudflare all route through the Frankfurt DC, so I am not sure whether there is some setting causing this routing issue15 Replies
Your ISP in Germany is DTAG?
yes
There's been issues with DTAG for a while now:
https://community.cloudflare.com/t/our-server-in-frankfurt-germany-eu-is-being-proxied-from-the-newark-nj-us-datacenter/610483/8?u=chaika
Something like DTAG wants Cloudflare to pay up/pay for peering and CF refuses for free accounts, so DTAG routes over congested/further away links
I don't have anouther free site to test
You can check https://cloudflare.manfredi.io/en/tools/datacenters/ and https://debug.chaika.me/?findColo=true and see where you get routed depending on plan
That's very useful thanks
Looks lke IPv4 is newark and v6 is ashburn that seems to align with my observations
hmm looks like that first link got broken at some point but yea second one should be a fine reference
there's a lot more info about that stuff in the community thread
But a confusing thing is
When I turn on NordVPN
and connect to a frankfurt server
nvm that makes sense, since it's no longer DTAG
What is the local-1111-ipv4 one, is that through warp?
It's 1.1.1.1, Cloudflare's DNS Service
most likely going to have Enterprise level or better routing
so it's when you are connected through 1111?
no
it's purely the dns service
so it's routing to 1111?
1.1.1.1 yes
ah that makes sense
WARP may route you better though, you could try it. I believe WARP itself has some higher routing priority, although WARP isn't in all colocations