05 Apr

Tata – Airtel domestic peering IRR filtering and OpenDNS latency!

Last month I noticed quite high latency with Cisco’s OpenDNS from my home fibre connection. The provider at home is IAXN (AS134316) which is peering with content folks in Delhi besides transit from Airtel.

ping -c 5 208.67.222.222
PING 208.67.222.222 (208.67.222.222) 56(84) bytes of data.
64 bytes from 208.67.222.222: icmp_seq=1 ttl=51 time=103 ms
64 bytes from 208.67.222.222: icmp_seq=2 ttl=51 time=103 ms
64 bytes from 208.67.222.222: icmp_seq=3 ttl=51 time=103 ms
64 bytes from 208.67.222.222: icmp_seq=4 ttl=51 time=103 ms
64 bytes from 208.67.222.222: icmp_seq=5 ttl=51 time=103 ms


--- 208.67.222.222 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 103.377/103.593/103.992/0.418 ms

This is bit on the higher side as from Haryana to Mumbai (OpenDNS locations list here). My ISP is backhauling from Faridabad which is probably 6-8ms away from my city and 2-3ms further to Delhi and from there to Mumbai around 30ms. Thus latency should be around ~40-45ms.

Here’s how forward trace looked like

traceroute 208.67.222.222
traceroute to 208.67.222.222 (208.67.222.222), 30 hops max, 60 byte packets
 1  172.16.0.1 (172.16.0.1)  0.730 ms  0.692 ms  0.809 ms
 2  axntech-dynamic-218.140.201.103.axntechnologies.in (103.201.140.218)  4.904 ms  4.314 ms  4.731 ms
 3  10.10.26.1 (10.10.26.1)  6.000 ms  6.414 ms  6.326 ms
 4  10.10.26.9 (10.10.26.9)  6.836 ms  7.135 ms  7.047 ms
 5  nsg-static-77.249.75.182-airtel.com (182.75.249.77)  9.344 ms  9.416 ms  9.330 ms
 6  182.79.243.201 (182.79.243.201)  62.274 ms 182.79.177.69 (182.79.177.69)  66.874 ms 182.79.239.193 (182.79.239.193)  61.297 ms
 7  121.240.1.201 (121.240.1.201)  85.789 ms  82.250 ms  79.591 ms
 8  172.25.81.134 (172.25.81.134)  110.049 ms 172.31.29.245 (172.31.29.245)  114.350 ms  113.673 ms
 9  172.31.133.210 (172.31.133.210)  112.598 ms 172.19.138.86 (172.19.138.86)  114.889 ms 172.31.133.210 (172.31.133.210)  113.415 ms
10  115.110.234.50.static.mumbai.vsnl.net.in (115.110.234.50)  125.770 ms  125.056 ms  123.779 ms
11  resolver1.opendns.com (208.67.222.222)  113.648 ms  115.044 ms  106.066 ms

Forward trace looks fine except that latency jumps as soon as we hit Tata AS4755 backbone. OpenDNS connects with Tata AS4755 inside India and announces their anycast prefixes to them. If the forward trace is logically correct but has high latency, it often reflects the case of bad return path. Thus I requested friends at OpenDNS to share the return path towards me. As expected, it was via Tata AS6453 Singapore.

Here’s what Tata AS4755 Mumbai router had for IAXN prefix:

BGP routing table entry for 14.102.188.0/22 
Paths: (1 available, best #1, table Default-IP-Routing-Table) 
Not advertised to any peer 
6453 9498 134316 134316 134316 134316 134316 134316 134316 134316 134316 134316 
192.168.203.194 from 192.168.199.193 (192.168.203.194) 
Origin IGP, localpref 62, valid, internal, best 
Community: 4755:44 4755:97 4755:888 4755:2000 4755:3000 4755:47552 6453:50 6453:3000 6453:3400 6453:3402 
Originator: 192.168.203.194, Cluster list: 192.168.199.193 192.168.194.15 
Last update: Mon Mar 25 15:26:36 2019

Thus what was happening is this:

Forward path: IAXN (AS134316) > Airtel (AS9498) > Tata (AS4755) > OpenDNS (AS36692)

Return path: OpenDNS (AS36692) > Tata (AS4755) > Tata (AS6453) > Airtel (AS9498) > IAXN (AS134316)

While this may seem like a Tata – Airtel routing issue but it wasn’t. I could see some of the prefixes with a direct path as well. Here’s a trace from Tata AS4755 Mumbai PoP to an IP from a different pool of IAXN:

traceroute to 103.87.46.1 (103.87.46.1), 15 hops max, 60 byte packets
1 * * *
2 172.31.170.210 (172.31.170.210) 0.911 ms 0.968 ms 0.643 ms
3 172.23.78.233 (172.23.78.233) 1.233 ms 0.821 ms 0.810 ms
4 172.17.125.249 (172.17.125.249) 23.540 ms 23.454 ms 23.367 ms
5 115.110.232.174.static.Delhi.vsnl.net.in (115.110.232.174) 49.175 ms 48.832 ms 49.107 ms
6 182.79.153.87 (182.79.153.87) 48.777 ms 182.79.153.83 (182.79.153.83) 49.043 ms 182.79.177.127 (182.79.177.127) 54.879 ms
7 103.87.46.1 (103.87.46.1) 60.865 ms 60.540 ms 60.644 ms

This clearly was fine. So why Tata was treating 103.87.46.0/24 different from 14.102.188.0/22? The reason for that lies in following:

  • Airtel (AS9498) very likely peers with Tata (AS4755). They do interconnect for sure as we see in traceroutes and my understanding is that it’s based on settlement-free peering for Indian traffic.
  • Airtel (AS9498) buys IP transit from Tata (AS6453) (besides a few others). Tata AS6453 is carrying the routing announcements to other networks in the transit free zone and that confirms that Airtel (at least technically) has a downstream customer relationship here.
  • Tata (AS4755) has IRR based filters on peering but not the Tata (AS6453) for it’s downstream. Hence while Tata rejected the route in India, they did accept that in Singapore PoP.
  • My IP was from prefix 14.102.188.0/22 and there was no valid route object for it at any of key IRRs like ATLDB, APNIC or RADB. But other prefix 103.87.46.0/24 did had a valid route object on APNIC.

Now after almost 10 days of it, my ISP has changed the BGP announcement and announcing 14.102.189.0/24 (which does a valid route object on APNIC). This fixes the routing problem and give me pretty decent latency with OpenDNS:

ping -c 5 208.67.222.222
PING 208.67.222.222 (208.67.222.222): 56 data bytes
64 bytes from 208.67.222.222: icmp_seq=0 ttl=55 time=52.552 ms
64 bytes from 208.67.222.222: icmp_seq=1 ttl=55 time=53.835 ms
64 bytes from 208.67.222.222: icmp_seq=2 ttl=55 time=53.330 ms
64 bytes from 208.67.222.222: icmp_seq=3 ttl=55 time=52.700 ms
64 bytes from 208.67.222.222: icmp_seq=4 ttl=55 time=52.504 ms

--- 208.67.222.222 ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 52.504/52.984/53.835/0.518 ms

So if you are a network operator and originating prefixes, please do document them in any of the IRRs. You can do that via IRR of your RIR (APNIC, ARIN etc) or a free IRR like ALTDB. If you have downstreams, make sure to create AS SET, add downstreams ASNs in your AS SET and also include that AS SET on peeringdb for the world to see!

Misc Notes

  • Posted strictly in my personal capacity and has nothing to do with my employrer.
  • Thanks for folks from Cisco/OpenDNS for quick replies with relevant data which helped in troubleshooting. 🙂
26 Aug

Facebook FNA Nodes Updates

Earlier this year after APRICOT 2018, I posted a list of visible Facebook FNA (CDN caching) nodes across the world with IPv4, IPv6 and the AS name. I got quite a few mails in following months about people mentioning that they installed nodes but do not see their names in the list (and that was normal since list was static). 

I re-ran my script to see emailslatest status of nodes. During last check I saw 1689  nodes (3rd March). Now on 26th Aug i.e after close to 6 months, the total number of nodes has increased to 2204.

Here is the latest sheet containing the list of nodes with ASN, network name, IPv4 and IPv6 – http://link.anuragbhatia.com/fna30aug

Summary of the data and some findings for India

  1. The number of nodes increased by 27% within the last 6 months. 

  2. On Reliance Jio network number of node increased by just 1 – which is a new node they put in Ludhiana, Punjab. 

  3. In Delhi, a number of FNA nodes went up from 16 to 21. Four new additions are ACT (AS18209), MNR Broadband (AS133648), Facebook itself (AS63293) which is worth exploring) and GEONET GEOCITY NETWORK SOLUTIONS (AS45235). This actually makes me wonder why I do not see any FNA nodes on my ex-employer Spectra AS10029 as yet.  (30 Aug 2018 Update: I missed this, please see footer below)

  4. In case of Mumbai (or Bombay as used for BOM airport code), the number went up from 17 to 21. New additions HNS (AS38457), Airtel (AS9498) and Vortex Netsol  (AS136334). 

  5. For Chennai number stayed same at 6 (4 telco – Airtel, Jio, Vodafone, IDEA) and 2 broadband ISPs (ACT and Hathway). 

  6. In Kolkata IDEA added the new FNA node. Rest all seems the same. 

  7. I see zero active nodes in Dishnet Wireless (Aircel) now. Earlier there was one in Kolkata and one in Chennai. 

  8. Still zero active nodes in India’s largest govt. incumbent operator BSNL AS9289. They clearly do not understand the value of content caching nodes. 

  9. There’s a major growth in a number of FNA nodes in Airtel from 9 (in March) to 16 (now at the end of Aug). And for IDEA number went from 6 to 12. While the number of nodes in Vodafone stays same (14). 

  10. There’s no node in any of Tata telecom companies. 

Well, that’s all about for now. Have a good Rakshabandhan. 🙂

Update: 30th Aug 2018

My friends from Spectra pointed out that they do have a node and that made me to re-look at my scripts. Due to a bug in the scripts, I was not getting all the nodes. I have fixed the bug and updated the data in this post. 

29 Jan

Amazon India peering check

And here goes first blog post of 2018. Last few months went busy with some major changes in personal life. 🙂

I looked into Amazon’s India connectivity with various ASNs tonight. Here’s how it looks like. (Note: Jump to bottom most to skip traces and look at the summary data).

 

Amazon India to Vodafone India

traceroute to 118.185.107.1 (118.185.107.1), 30 hops max, 60 byte packets
 1 ec2-52-66-0-128.ap-south-1.compute.amazonaws.com (52.66.0.128) 21.861 ms ec2-52-66-0-134.ap-south-1.compute.amazonaws.com (52.66.0.134) 19.244 ms 19.233 ms
 2 100.64.2.200 (100.64.2.200) 14.789 ms 100.64.0.200 (100.64.0.200) 20.731 ms 100.64.3.12 (100.64.3.12) 13.187 ms
 3 100.64.0.193 (100.64.0.193) 14.418 ms 100.64.3.69 (100.64.3.69) 15.469 ms 100.64.3.67 (100.64.3.67) 15.946 ms
 4 100.64.16.67 (100.64.16.67) 0.343 ms 100.64.17.165 (100.64.17.165) 0.312 ms 100.64.17.199 (100.64.17.199) 0.313 ms
 5 52.95.67.213 (52.95.67.213) 1.942 ms 52.95.67.209 (52.95.67.209) 1.967 ms 52.95.67.213 (52.95.67.213) 1.935 ms
 6 52.95.66.218 (52.95.66.218) 4.998 ms 4.694 ms 52.95.66.130 (52.95.66.130) 4.650 ms
 7 52.95.66.67 (52.95.66.67) 1.752 ms 52.95.66.89 (52.95.66.89) 1.850 ms 1.806 ms
 8 52.95.217.183 (52.95.217.183) 3.111 ms 3.102 ms 3.088 ms <- Amazon India
 9 182.19.106.204 (182.19.106.204) 3.426 ms 4.547 ms 4.537 ms <- Vodafone India
10 118.185.107.1 (118.185.107.1) 2.035 ms 2.059 ms 2.039 ms

 

Amazon India to IDEA

traceroute to 223.196.83.1 (223.196.83.1), 30 hops max, 60 byte packets
 1 ec2-52-66-0-128.ap-south-1.compute.amazonaws.com (52.66.0.128) 16.133 ms ec2-52-66-0-132.ap-south-1.compute.amazonaws.com (52.66.0.132) 14.232 ms ec2-52-66-0-130.ap-south-1.compute.amazonaws.com (52.66.0.130) 21.267 ms
 2 100.64.3.10 (100.64.3.10) 16.418 ms 100.64.1.76 (100.64.1.76) 20.674 ms 100.64.1.206 (100.64.1.206) 26.416 ms
 3 100.64.3.129 (100.64.3.129) 18.727 ms 100.64.3.135 (100.64.3.135) 13.790 ms 100.64.3.133 (100.64.3.133) 20.787 ms
 4 100.64.16.101 (100.64.16.101) 0.323 ms 100.64.16.195 (100.64.16.195) 0.296 ms 100.64.16.135 (100.64.16.135) 2.358 ms
 5 52.95.67.213 (52.95.67.213) 1.879 ms 2.452 ms 2.465 ms
 6 52.95.66.174 (52.95.66.174) 2.717 ms 52.95.66.130 (52.95.66.130) 8.568 ms 52.95.66.64 (52.95.66.64) 6.004 ms
 7 52.95.66.183 (52.95.66.183) 4.361 ms 52.95.66.73 (52.95.66.73) 11.474 ms 52.95.66.51 (52.95.66.51) 11.414 ms
 8 52.95.217.201 (52.95.217.201) 3.585 ms 3.627 ms 3.420 ms
 9 223.196.6.237 (223.196.6.237) 3.704 ms 3.832 ms 3.826 ms
10 223.196.15.26 (223.196.15.26) 6.155 ms 223.196.2.141 (223.196.2.141) 8.472 ms *

 

Amazon India to Reliance Communications

traceroute to 115.252.64.1 (115.252.64.1), 30 hops max, 60 byte packets
 1 ec2-52-66-0-132.ap-south-1.compute.amazonaws.com (52.66.0.132) 18.567 ms ec2-52-66-0-134.ap-south-1.compute.amazonaws.com (52.66.0.134) 19.024 ms 19.020 ms
 2 100.64.0.72 (100.64.0.72) 22.429 ms 100.64.0.200 (100.64.0.200) 19.483 ms 100.64.2.142 (100.64.2.142) 18.679 ms
 3 100.64.1.67 (100.64.1.67) 11.717 ms 100.64.0.7 (100.64.0.7) 30.194 ms 100.64.2.195 (100.64.2.195) 11.700 ms
 4 100.64.16.195 (100.64.16.195) 0.353 ms 100.64.16.67 (100.64.16.67) 0.398 ms 100.64.17.163 (100.64.17.163) 0.400 ms
 5 52.95.67.209 (52.95.67.209) 1.847 ms 1.879 ms 1.891 ms
 6 52.95.66.108 (52.95.66.108) 5.567 ms 52.95.67.108 (52.95.67.108) 11.119 ms 52.95.66.174 (52.95.66.174) 9.029 ms
 7 52.95.66.141 (52.95.66.141) 2.938 ms 52.95.67.99 (52.95.67.99) 1.755 ms 52.95.67.165 (52.95.67.165) 1.755 ms
 8 54.239.43.171 (54.239.43.171) 18.605 ms 54.239.44.63 (54.239.44.63) 18.034 ms 54.239.43.171 (54.239.43.171) 18.522 ms
 9 52.93.19.126 (52.93.19.126) 63.893 ms 52.93.19.82 (52.93.19.82) 23.508 ms 52.93.19.62 (52.93.19.62) 20.812 ms
10 52.93.19.139 (52.93.19.139) 19.302 ms 52.93.19.133 (52.93.19.133) 18.600 ms 52.93.19.25 (52.93.19.25) 18.365 ms
11 115.110.161.61.static.vsnl.net.in (115.110.161.61) 17.966 ms 18.201 ms 115.110.161.65.static.vsnl.net.in (115.110.161.65) 17.948 ms
12 121.244.23.6.STATIC.Chennai.vsnl.net.in (121.244.23.6) 18.391 ms * *
13 115.255.253.69 (115.255.253.69) 27.234 ms 27.455 ms 27.652 ms
14 115.255.28.129 (115.255.28.129) 27.836 ms 121.244.23.6.STATIC.Chennai.vsnl.net.in (121.244.23.6) 18.906 ms 18.809 ms
15 115.255.232.1 (115.255.232.1) 27.524 ms 115.255.253.69 (115.255.253.69) 27.971 ms 115.255.232.1 (115.255.232.1) 27.777 ms
16 220.227.241.217 (220.227.241.217) 27.841 ms * 27.886 ms
17 115.255.232.1 (115.255.232.1) 27.628 ms 27.920 ms 27.965 ms
18 220.227.241.217 (220.227.241.217) 29.835 ms 220.224.230.177 (220.224.230.177) 28.402 ms *

 

Amazon India to Powergrid Corp

traceroute to 43.227.132.1 (43.227.132.1), 30 hops max, 60 byte packets
 1 ec2-52-66-0-132.ap-south-1.compute.amazonaws.com (52.66.0.132) 15.971 ms ec2-52-66-0-128.ap-south-1.compute.amazonaws.com (52.66.0.128) 11.558 ms ec2-52-66-0-134.ap-south-1.compute.amazonaws.com (52.66.0.134) 19.813 ms
 2 100.64.0.14 (100.64.0.14) 18.356 ms 100.64.2.200 (100.64.2.200) 15.390 ms 15.390 ms
 3 100.64.2.1 (100.64.2.1) 21.122 ms 100.64.3.3 (100.64.3.3) 19.208 ms 100.64.1.1 (100.64.1.1) 21.094 ms
 4 100.64.17.165 (100.64.17.165) 0.283 ms 100.64.16.39 (100.64.16.39) 0.323 ms 100.64.17.103 (100.64.17.103) 0.341 ms
 5 52.95.67.215 (52.95.67.215) 1.638 ms 52.95.67.211 (52.95.67.211) 0.702 ms 52.95.67.215 (52.95.67.215) 0.749 ms
 6 52.95.67.64 (52.95.67.64) 1.103 ms 52.95.67.86 (52.95.67.86) 4.012 ms 3.986 ms
 7 52.95.67.51 (52.95.67.51) 0.599 ms 52.95.67.29 (52.95.67.29) 0.662 ms 52.95.67.51 (52.95.67.51) 0.651 ms
 8 52.95.219.49 (52.95.219.49) 7.935 ms 8.111 ms 8.675 ms
 9 kalwa-edge-177.230.218.103.powergrid.in (103.218.230.177) 1.452 ms 1.641 ms 1.169 ms
10 43.227.132.65 (43.227.132.65) 49.309 ms 49.233 ms 49.296 ms
11 43.227.132.1 (43.227.132.1) 58.909 ms 58.975 ms 58.893 ms

 

Amazon India to BSNL

traceroute to 218.248.235.130 (218.248.235.130), 30 hops max, 60 byte packets
 1 ec2-52-66-0-128.ap-south-1.compute.amazonaws.com (52.66.0.128) 15.199 ms 15.173 ms ec2-52-66-0-130.ap-south-1.compute.amazonaws.com (52.66.0.130) 16.306 ms
 2 100.64.2.140 (100.64.2.140) 18.831 ms 100.64.2.202 (100.64.2.202) 18.159 ms 100.64.2.78 (100.64.2.78) 15.493 ms
 3 100.64.1.1 (100.64.1.1) 16.829 ms 100.64.1.129 (100.64.1.129) 16.823 ms 100.64.2.193 (100.64.2.193) 16.813 ms
 4 100.64.16.193 (100.64.16.193) 0.403 ms 100.64.17.133 (100.64.17.133) 0.290 ms 100.64.17.99 (100.64.17.99) 0.289 ms
 5 52.95.67.215 (52.95.67.215) 0.803 ms 52.95.67.211 (52.95.67.211) 0.672 ms 0.702 ms
 6 52.95.66.130 (52.95.66.130) 7.382 ms 7.107 ms 52.95.67.174 (52.95.67.174) 2.292 ms
 7 52.95.66.179 (52.95.66.179) 1.819 ms 52.95.67.91 (52.95.67.91) 0.658 ms 52.95.66.91 (52.95.66.91) 1.798 ms
 8 52.95.217.42 (52.95.217.42) 0.534 ms 0.505 ms 52.95.217.38 (52.95.217.38) 2.010 ms
 9 182.79.178.199 (182.79.178.199) 1.938 ms 182.79.178.63 (182.79.178.63) 1.936 ms 182.79.178.201 (182.79.178.201) 1.926 ms
10 * * aes-static-042.105.144.59.airtel.in (59.144.105.42) 3.179 ms
11 218.248.235.157 (218.248.235.157) 3.106 ms 3.230 ms *
12 218.248.235.129 (218.248.235.129) 40.928 ms 40.433 ms 40.853 ms
13 218.248.235.130 (218.248.235.130) 40.307 ms 40.384 ms 40.280 ms

 

Trace from Amazon India to Google’s anycasted 8.8.8.8:

traceroute -A 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 ec2-52-66-0-134.ap-south-1.compute.amazonaws.com (52.66.0.134) [AS38895/AS16509] 12.662 ms ec2-52-66-0-130.ap-south-1.compute.amazonaws.com (52.66.0.130) [AS38895/AS16509] 20.008 ms ec2-52-66-0-128.ap-south-1.compute.amazonaws.com (52.66.0.128) [AS38895/AS16509] 21.983 ms
2 100.64.0.142 (100.64.0.142) [AS22773] 15.525 ms 100.64.0.204 (100.64.0.204) [AS22773] 16.081 ms 100.64.1.206 (100.64.1.206) [AS22773] 19.696 ms
3 100.64.0.131 (100.64.0.131) [AS22773] 12.944 ms 12.893 ms 100.64.2.5 (100.64.2.5) [AS22773] 15.071 ms
4 100.64.16.103 (100.64.16.103) [AS22773] 0.318 ms 100.64.17.39 (100.64.17.39) [AS22773] 0.325 ms 100.64.17.69 (100.64.17.69) [AS22773] 0.291 ms
5 52.95.67.215 (52.95.67.215) [AS16509] 1.374 ms 5.725 ms 4.294 ms
6 52.95.67.130 (52.95.67.130) [AS16509] 4.896 ms 52.95.67.86 (52.95.67.86) [AS16509] 2.021 ms 52.95.67.108 (52.95.67.108) [AS16509] 5.735 ms
7 52.95.67.111 (52.95.67.111) [AS16509] 0.705 ms 0.672 ms 0.670 ms
8 52.95.218.225 (52.95.218.225) [*] 0.542 ms 0.570 ms 0.505 ms
9 108.170.248.161 (108.170.248.161) [AS15169] 0.853 ms 108.170.248.193 (108.170.248.193) [AS15169] 0.804 ms 108.170.248.177 (108.170.248.177) [AS15169] 0.770 ms
10 108.170.234.9 (108.170.234.9) [AS15169] 1.449 ms 209.85.248.147 (209.85.248.147) [AS15169] 1.725 ms 1.728 ms
11 google-public-dns-a.google.com (8.8.8.8) [AS15169] 0.460 ms 0.744 ms 0.449 ms

 

Amazon India to Microsoft Azure India

traceroute to 52.172.52.79 (52.172.52.79), 30 hops max, 60 byte packets
 1 ec2-52-66-0-132.ap-south-1.compute.amazonaws.com (52.66.0.132) 11.434 ms ec2-52-66-0-134.ap-south-1.compute.amazonaws.com (52.66.0.134) 14.968 ms ec2-52-66-0-128.ap-south-1.compute.amazonaws.com (52.66.0.128) 14.694 ms
 2 100.64.2.8 (100.64.2.8) 15.301 ms 100.64.3.14 (100.64.3.14) 14.541 ms 100.64.2.10 (100.64.2.10) 15.289 ms
 3 100.64.0.131 (100.64.0.131) 19.954 ms 100.64.2.199 (100.64.2.199) 20.491 ms 100.64.1.135 (100.64.1.135) 20.473 ms
 4 100.64.16.67 (100.64.16.67) 6.650 ms 100.64.16.65 (100.64.16.65) 0.306 ms 100.64.16.133 (100.64.16.133) 0.307 ms
 5 52.95.67.213 (52.95.67.213) 1.917 ms 52.95.67.209 (52.95.67.209) 1.931 ms 1.980 ms
 6 52.95.66.130 (52.95.66.130) 3.015 ms 52.95.66.196 (52.95.66.196) 10.939 ms 52.95.66.86 (52.95.66.86) 11.644 ms
 7 52.95.66.91 (52.95.66.91) 1.802 ms 52.95.66.177 (52.95.66.177) 7.303 ms 52.95.66.199 (52.95.66.199) 3.435 ms
 8 52.95.218.61 (52.95.218.61) 16.785 ms 52.95.218.63 (52.95.218.63) 1.700 ms 1.674 ms
 9 ae0-0.bom02-96cbe-1b.ntwk.msn.net (104.44.226.17) 1.952 ms 1.897 ms ae14-0.bom30-96cbe-1b.ntwk.msn.net (198.206.164.159) 2.238 ms
10 ae14-0.bom30-96cbe-1b.ntwk.msn.net (198.206.164.159) 2.150 ms 2.172 ms ae5-0.maa30-96cbe-1a.ntwk.msn.net (104.44.226.241) 26.009 ms
11 ae5-0.maa30-96cbe-1a.ntwk.msn.net (104.44.226.241) 25.940 ms ae10-0.maa01-96cbe-1b.ntwk.msn.net (104.44.226.243) 27.591 ms 27.587 ms
12 ae10-0.maa01-96cbe-1b.ntwk.msn.net (104.44.226.243) 27.698 ms ae0-0.maa01-96cbe-1a.ntwk.msn.net (104.44.227.208) 28.090 ms *
13 * ae0-0.maa01-96cbe-1a.ntwk.msn.net (104.44.227.208) 27.682 ms *
14 * * *
15 * * *
16 * * *
17 * * *
18 *^C

 

Amazon India to Cloudflare India PoP

traceroute to amy.ns.cloudflare.com (173.245.58.101), 30 hops max, 60 byte packets
 1 ec2-52-66-0-130.ap-south-1.compute.amazonaws.com (52.66.0.130) [AS38895/AS16509] 13.912 ms ec2-52-66-0-134.ap-south-1.compute.amazonaws.com (52.66.0.134) [AS38895/AS16509] 15.167 ms 15.159 ms
 2 100.64.0.142 (100.64.0.142) [AS22773] 21.393 ms 100.64.3.72 (100.64.3.72) [AS22773] 16.098 ms 100.64.3.14 (100.64.3.14) [AS22773] 11.766 ms
 3 100.64.2.67 (100.64.2.67) [AS22773] 27.118 ms 100.64.2.131 (100.64.2.131) [AS22773] 27.097 ms 100.64.2.133 (100.64.2.133) [AS22773] 21.532 ms
 4 100.64.16.39 (100.64.16.39) [AS22773] 0.253 ms 100.64.17.193 (100.64.17.193) [AS22773] 0.256 ms 100.64.16.195 (100.64.16.195) [AS22773] 0.260 ms
 5 52.95.67.209 (52.95.67.209) [AS16509] 1.850 ms 1.846 ms 52.95.67.213 (52.95.67.213) [AS16509] 1.808 ms
 6 52.95.66.108 (52.95.66.108) [AS16509] 3.007 ms 52.95.66.174 (52.95.66.174) [AS16509] 13.312 ms 13.285 ms
 7 52.95.66.201 (52.95.66.201) [AS16509] 1.890 ms 52.95.66.135 (52.95.66.135) [AS16509] 2.571 ms 52.95.66.71 (52.95.66.71) [AS16509] 1.867 ms
 8 115.114.89.209.static-Mumbai.vsnl.net.in (115.114.89.209) [AS4755] 2.448 ms 115.114.89.189.static-Mumbai.vsnl.net.in (115.114.89.189) [AS4755] 1.984 ms 1.888 ms
 9 * * *
10 * 182.79.203.36 (182.79.203.36) [*] 2.459 ms *
11 182.79.223.54 (182.79.223.54) [*] 2.357 ms 2.368 ms 14.142.21.18.static-vsnl.net.in (14.142.21.18) [AS4755] 2.008 ms
12 amy.ns.cloudflare.com (173.245.58.101) [AS13335] 2.467 ms 182.79.203.44 (182.79.203.44) [*] 2.777 ms amy.ns.cloudflare.com (173.245.58.101) [AS13335] 2.445 ms

 

 

Some traces where traffic going from Amazon India is getting routed to Indian networks from outside:

traceroute to 125.18.237.1 (125.18.237.1), 30 hops max, 60 byte packets
 1 ec2-52-66-0-134.ap-south-1.compute.amazonaws.com (52.66.0.134) 18.252 ms ec2-52-66-0-130.ap-south-1.compute.amazonaws.com (52.66.0.130) 17.868 ms ec2-52-66-0-132.ap-south-1.compute.amazonaws.com (52.66.0.132) 20.634 ms
 2 100.64.3.76 (100.64.3.76) 15.640 ms 100.64.2.202 (100.64.2.202) 13.602 ms 100.64.0.74 (100.64.0.74) 14.663 ms
 3 100.64.3.197 (100.64.3.197) 2.152 ms 100.64.2.69 (100.64.2.69) 2.128 ms 100.64.3.69 (100.64.3.69) 2.134 ms
 4 100.64.17.37 (100.64.17.37) 0.337 ms 100.64.16.37 (100.64.16.37) 0.354 ms 100.64.17.129 (100.64.17.129) 0.293 ms
 5 52.95.67.213 (52.95.67.213) 1.902 ms 1.861 ms 52.95.67.209 (52.95.67.209) 1.867 ms
 6 52.95.66.64 (52.95.66.64) 5.317 ms 52.95.66.218 (52.95.66.218) 6.883 ms 52.95.66.196 (52.95.66.196) 9.687 ms
 7 52.95.66.203 (52.95.66.203) 1.817 ms 52.95.66.69 (52.95.66.69) 1.844 ms 52.95.66.137 (52.95.66.137) 1.792 ms
 8 115.114.89.121.static-Mumbai.vsnl.net.in (115.114.89.121) 1.745 ms 115.114.89.209.static-Mumbai.vsnl.net.in (115.114.89.209) 1.799 ms 115.114.89.121.static-Mumbai.vsnl.net.in (115.114.89.121) 2.034 ms
 9 * * *
10 ix-ae-4-2.tcore1.CXR-Chennai.as6453.net (180.87.36.9) 54.804 ms * *
11 if-ae-3-3.tcore2.CXR-Chennai.as6453.net (180.87.36.6) 228.066 ms ix-ae-4-2.tcore1.CXR-Chennai.as6453.net (180.87.36.9) 56.587 ms 53.271 ms
12 if-ae-3-3.tcore2.CXR-Chennai.as6453.net (180.87.36.6) 225.894 ms 226.883 ms 227.007 ms
13 if-ae-6-2.tcore2.SVW-Singapore.as6453.net (180.87.37.14) 226.616 ms 227.081 ms if-ae-10-2.tcore2.SVW-Singapore.as6453.net (180.87.37.65) 226.699 ms
14 if-ae-7-2.tcore2.LVW-Los-Angeles.as6453.net (180.87.15.26) 227.935 ms 225.266 ms 235.497 ms
15 xe-4-1-0.edge1.SanJose3.level3.net (4.68.62.105) 247.387 ms 257.588 ms 249.384 ms
16 ae-116-3502.edge3.London15.Level3.net (4.69.167.78) 241.053 ms 241.539 ms ae-115-3501.edge3.London15.Level3.net (4.69.167.74) 242.991 ms
17 ae-116-3502.edge3.London15.Level3.net (4.69.167.78) 240.407 ms ae-225-3601.edge3.London15.Level3.net (4.69.167.90) 243.525 ms ae-226-3602.edge3.London15.Level3.net (4.69.167.94) 241.484 ms
18 BHARTI-AIRT.edge3.London15.Level3.net (212.187.139.82) 244.356 ms 244.610 ms *
19 * * *
20 * * *
21 * * *
22 *^C

 

Summary of results

Network Name Network ASN Domestic Connectivity
Tata Communications 4755 Yes*
Airtel 9498 Yes*
Idea Cellular 55644 Yes
Reliance Communucations 18101 No
Aircel 10201 No
Powergrid Telecom 132215 Yes
Railtel 24186 Yes
BSNL 9829 No
NKN 55824 No
CtrlS 18229 No
Syscon Infoway 45194 No
Intech Online 58678 Yes
Charotar Broadband 132933 Yes
Ishan Tech 45117 Yes
Webwerks 33480 No
Blazenet 17625 Yes
Spectra 10029 Yes
Excitel Broadband 133982 Yes
Google 15169 Yes
Cloudflare 13335 No
Microsoft 8075 Yes

 

Misc points:

  1. *TCL and *Airtel seem to be IP transit provider of Amazon. For certain routes going outside India traffic seem to be going via Tata VSNL AS4755.
  2. Connectivity checked for certain random pools only and not for all announced routes for a large telco network.