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

 

Amazon India to IDEA

 

Amazon India to Reliance Communications

 

Amazon India to Powergrid Corp

 

Amazon India to BSNL

 

Trace from Amazon India to Google’s anycasted 8.8.8.8:

 

Amazon India to Microsoft Azure India

 

Amazon India to Cloudflare India PoP

 

 

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

 

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.
27 Apr

Cloudflare hosting F root server

A few days some folks in internet community noticed Cloudflare AS13335 announcing F root server’s routes covering prefix 192.5.5.0/24.

 

 

Above tweet shows that case is clearly not a mistake but rather some sort of arrangement between Cloudflare and ISC (which is responsible for F-root). There was another discussion on DNS-OARC mailing list here.

From our bgp.he.net tool, one can analyse route propagation for F root’s AS3557.

 

Here we can see that routes are visible from AS13335 to Telefonica AS13335. One can safely assume that AS12956 (considered to be a Tier1 / transit free network as per list here) is not a customer of Cloudflare. So the fact that still route is being announced to Telefonica gives an impression that AS3557 is downstream of Cloudflare.

It’s hard to say on the kind of arrangement as I still see many of instances of F-root are being hosted directly by ISC from hostname.bind query triggered via local RIPE Atlas probes in those regions. It could be that Cloudflare is hosting a part of this setup say in developing region where they have their caching PoPs. Yet to see a detailed blog post from Cloudflare about it. (I like their detailed blog!)

 

Update: 2nd April 2017 

Henry from Cloudflare pointed me to their official announcement blog post written after around 5 months of this post. You can find their official announcement here.