While using Warp, I noticed that sometimes I connect to an endpoint IP from 162.159.192.0/24, which always gets routed internationally. My ISP directly peers at an exchange where Cloudflare peers but doesn’t route the traffic to the exchange locally. I ran a few traceroutes from online probes located in India and found out that an ISP, which directly peers with Cloudflare and 162.159.192.0/24, still reroutes internally to Singapore. Take a look at the traceroute below
1.|-- 100.64.128.2 0.0% 5 1.9 1.5 1.2 1.9 0.3
2.|-- 162.158.226.44 0.0% 5 2.5 13.1 2.5 40.2 16.2
3.|-- 1.7.160.209 0.0% 5 3.3 3.2 2.9 3.4 0.2
4.|-- 100.70.208.36 0.0% 5 23.3 23.3 23.2 23.5 0.1
5.|-- 100.71.129.230 80.0% 5 22.6 22.6 22.6 22.6 0.0
6.|-- 100.70.136.182 0.0% 5 23.6 24.3 23.0 27.9 2.0
7.|-- 203.200.182.181 0.0% 5 22.6 24.2 22.5 30.7 3.6
8.|-- 172.31.180.57 0.0% 5 38.3 38.5 38.3 38.8 0.2
9.|-- 180.87.36.9 0.0% 5 35.8 36.1 35.8 36.6 0.3
10.|-- 180.87.36.41 0.0% 5 70.6 70.8 70.1 71.2 0.4
11.|-- 180.87.107.0 0.0% 5 73.6 73.7 73.5 73.9 0.2
12.|-- 172.70.146.3 20.0% 5 74.7 74.8 74.5 75.3 0.4
13.|-- 162.159.192.1 0.0% 5 70.5 70.0 69.6 70.5 0.3
This suggests that Cloudflare doesn’t advertise the IP in India. Is there any reason this IP range is used for Warp in India, as it will never connect you to a colocation server near you in India and will always be routed internationally?