02 Jul

Welcome to AWS Cloud Mumbai region


It’s great to see Amazon’s announcement two days back about launch of their region in Mumbai. In past I was quite happy to see their Cloudfront CDN PoPs in Mumbai & Chennai (blog post here). Now it’s just great to see a full AWS region out of Mumbai. 🙂

Though it’s going to eat most of important customers from the smaller players still it’s good for industry as industry is too big and we need more & more of such large Cloud players in India to bring more and more content hosting in India.


So how does Amazon’s Indian network is connected at the moment?

Let’s trigger a VM on Amazon EC2 in Mumbai and test based on routing of various networks to it’s IP and return.


On the instance:


Trace from Amazon to outside world:


So clearly Amazon is reaching all domestic destinations via Tata (AS4755). Let us  look at other side around i.e reaching from domestic destinations to Amazon by BGP table as well as trace from RIPE Atlas probes.


Routing table of NIXI route server:


So route for AWS Cloud in India seems via Tata (AS4755). A quick check on latency from RIPE Atlas Indian Probes:



Clearly latency does seems little high from certain probes. Running a trace from them:


One thing which is noticeable here is high latency from BSNL (AS9829) backbone.

BSNL to AWS Mumbai



Summary and misc thoughts:

  1. AWS India seems to have PoP/datacenters across Mumbai, Pune and Hyderabad (based on visible PTRs of their only Indian transit).
  2. AWS is using Tata (AS4755) in India to reachout to all Indian networks with highly likely option of peering with other Indian networks in near future.
  3. There seems to be a “pipe” connecting AWS Mumbai region with their Singapore network and I see most of their international traffic flow (traffic TO and FROM outside India over their own PoP and transits which they are using in Singapore).
  4. Connectivity seems OK from Tata Communications & Airtel while seems not very good with Reliance (AS18101) and BSNL (AS9829). BSNL is pushing some of the traffic out via AS6453 IPLCs outside India while Reliance is preferring FLAG (AS15412) > NTT (AS2914) > Amazon routes over (likely) visible routes from Tata (AS4755).


Time for me to hop on to next flight and get to home. 🙂

30 Jul

Welcome Amazon AWS AS16509 to India!

Today I spotted some routes from Amazon AWS Cloud services –  AS16509 in Indian tables. AS16509 was originating prefixes while sitting in downstream of Tata-VSNL AS4755 and Reliance AS18101. I almost missed Amazon AWS’s announcement on their blog about Indian PoPs for their DNS service – Route53 and CDN service – Cloudfront.


New PoP’s of Amazon in India are at Mumbai and Chennai and I see pretty much consistent BGP announcements to Tata and Reliance from these locations. Prefixes I have seen so far:


Unicast prefixes originated in India (for Cloufront CDN):


Anycast prefixes (for anycasted DNS route 53)


Note: I pulled these prefixes by looking at upstream peers in India (which is Tata and Reliance) and running simply sh ip bgp regexp 4755 16509sh ip bgp regexp 18101 16509 on Oregon routeviews & few other major data collection points of global IPv4 table. 

I can’t see any upstream from Airtel AS9498 or any other major Indian telco. Also at NIXI prefixes are available partially. I see prefiex at NIXI Mumbai carried by Tata VSNL. At NIXI Chennai prefixes are present with one degree prepend (AS4755 AS4755 twice) making route less preferable. While at NIXI Delhi there seems no route at all for Amazon’s prefixes (Tata follows regional route policy at NIXI). 


So now big question here – which datacenter is that? 

I doubt it would be Tata or Reliance since they are core competitiors and run datacenters pretty much on their own networks with almost zero carrier neutral options (few exceptions are there). My strong guess is that it’s Netmagic’s datacenter in Mumbai and Chennai with direct upstream links (bypassing Netmagic’s network). Just my guess. Cannot verify it from record of AS16509 on peeringdb.net – http://www.peeringdb.com/view.php?asn=16509


With that being said here’s a trace to cdn.anuragbhatia.com (which I use via Amazon Cloudfront):

Anurags-MacBook-Pro:~ anurag$ traceroute -a cdn.anuragbhatia.com
traceroute: Warning: cdn.anuragbhatia.com has multiple addresses; using
traceroute to ddlfp4nmkhyfr.cloudfront.net (, 64 hops max, 52 byte packets
1 [AS1] ( 1.152 ms 0.765 ms 0.627 ms
2 [AS10223] ( 1.460 ms 2.906 ms 1.569 ms
3 [AS9829] ( 16.339 ms 17.905 ms 15.704 ms
4 [AS9829] ( 94.835 ms 29.628 ms 118.135 ms
5 [AS4755] ( 60.472 ms 61.304 ms 59.103 ms
6 [AS0] ( 84.706 ms 87.201 ms 85.640 ms
7 [AS4755] ( 82.327 ms 83.276 ms 81.583 ms
8 [AS16509] server-54-230-189-204.maa3.r.cloudfront.net ( 85.261 ms 85.185 ms 84.269 ms
Anurags-MacBook-Pro:~ anurag$


Always nice to maa in all these nodes at Chennai. Basically most of companies (including Google) use 3 digit airport code in name of node (in rDNS PTR record of router’s WAN IP). For Chennai (which used to be known as Madras) airport code is still MAA and this is why you will see maa in Chennai nodes and BOM on Mumbai based nodes. 🙂


Time to get back to work. Have a good week ahead! 🙂