Might be because of the peering from your local ISP
I remember I have restricted access to only my country, but somehow I got an IP from the IP range of my ISP provider which somehow wasn’t going over the regular country, rather from neighbour country, therefore Cloudflare WARP got me an IP from the neighbour country and I wasn’t being able to bypass it because of my settings were set to my country.
Tracing my true IP down, I found that I went over other (neighbour) country which is a bad thing as I don’t want it. However, that’s because of the peering of my ISP and I cannot do anything except wait them to get the “peer” or “route server/connection” over the same IX point (data center) where Cloudflare has it.
Until then, in case if I get the IP from them, and any other IP range, I am stuck with that ISP except if I move to some other, where the packets and routing would go straight through Cloudflare peer/point.
I don’t think the issue is the peering.
I think the issue is that the IP address the trace is reporting is the IP of the Cloudflare datacenter, not the IP of the connecting users ISP (in my case, Rogers).
In other words, from the trace above,
should actually be:
ip=99.x.x.x (my Rogers IP Address).
Something has changed on the Cloudflare backend where they are no longer reporting the users IP address when connecting via Warp.
Cloudflare is usually smart enough to know the visitors ip address location (irrespective of which Cloudflare PoP you connect to and whether it is in a different country or not). It wasn’t doing this yesterday so something has changed since yesterday.