Cdn-cgi/trace - Returning a far away data center

I’m using 1.1.1.1 and the site is proxied on cloudflare. I’m based in the north east UK, The nearest data centers for cloudflare to me are Edinburgh, Manchester and London. The websites origin server is in Machester, my ISP is also Manchester based.

For some reason for the past month running a /trace to the site shows that it’s getting a response from the data center in Amsterdam:

visit_scheme=https
uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4456.0 Safari/537.36 Edg/91.0.845.2
colo=AMS
http=http/3
loc=GB
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off

Is there a reason why this is now happening?, Usually It’s 80/20 between LON and MAN respectively… I would have thought it would be faster and more efficient all coming from Manchester?.. It also appears they have peering with each other there too.

Hello,

This is most likely because your ISP is choosing a different (cheaper, faster, more efficient) route. I have a FAQ topic for this which has some more possible explanations: https://developers.cloudflare.com/warp-client/known-issues-and-faq#why-am-i-not-connecting-to-a-closer-cloudflare-point-of-presence

Note we intentionally don’t offer the ability to choose your colo. Your scenario is completely valid.
but the vast majority of folks want this to skirt intellectual property rules (watch Netflix in another country, listen to radio, etc…) which isn’t what we are about. It would be interesting to allow this within your own country though, i’ll add that idea to our backlog.