The routing to Cloudflare nagpur is messed up:
First I thought it was just my ISP not routing properly
(ping to Cloudflare nagpur IP)
The traceroute showed that it was hopping through SG and bunch of other countries even tho the server is in the same city.
I thought it was just my ISP messing things up.
so I tried using Cloudflare warp…
surprisingly it was worse:
It took even more hops through more countries
I think this’s an issue with Cloudflare routing
My ISP: AS24560 Bharti Airtel Ltd., Telemedia Services
IP of the CF COLO: 126.96.36.199
the latency over Cloudflare warp is currently 148ms
but it’s still taking a long route to italy for a server that’s in the same city
Does anyone have any idea, what’s causing this?
Thanks for raising this issue. My name is Venkat, a Technical Support Engineer at Cloudflare. Our Engineering team has taken a deeper look on your issue.
Our Engineering team has informed us that Nagpur only serves traffic from AS55836 and downstream peers, AS24560 is not one of those downstream peers. Routing to / from our Nagpur colo is working as expected right now.
Venkat Chaithanya Chintha
Thanks for replying,
Our Engineering team has informed us that Nagpur only serves traffic from AS55836 and downstream peers, AS24560 is not one of those downstream peers.
Why tho? any specific reason for this… I had tested using a friends network and can confirm that the traffic from AS55836 uses Cloudflare nagpur.
Any plans to add more peers?
AS24560 has a lot of users and it’d be nice to have a physically closer server