Requests from India routed to Singapore

All requests from India (including HTML and static files) are routed to Singapore. This is creating a latency of 400ms or more.

traceroute to quotzap.netlify.com (206.189.89.118), 30 hops max, 60 byte packets
 1  _gateway (192.168.0.1)  0.189 ms  0.178 ms  0.186 ms
 2  10.3.71.1 (10.3.71.1)  7.544 ms  7.545 ms  13.770 ms
 3  * * *
 4  170.230.88.202.asianet.co.in (202.88.230.170)  16.051 ms  16.052 ms  16.062 ms
 5  * * 17.1.1.1 (17.1.1.1)  15.912 ms

On tracing the IP, it’s from Singapore: https://www.ip2location.com/demo/206.189.89.118

Is this expected? Or there are no pops in India?

2 Likes

Hi @gijo-varghese - my insight into our routing doesn’t go deep enough to answer your question in detail, but, here is our most recent posting on CDN pops:

@perry Thanks. So I think it’s available only in the Enterprise plan (Mumbai region). Is that the same case for static files? I somewhere read that Netlify uses it’s own CDN for HTML files and Akamai for static files.

We do not use Akamai at this time. Cloudfront is used for assets which have been modified by our asset optimization during post processing, but only modified assets will be served from Cloudfront. If an asset is unchanged by the asset optimization, it will be served from Netlify’s ADN/CDN.