A friend of mine buzzed me yesterday about his missing route objects. Later multiple other ISPs told the same story which triggered me to put this as a question on INNOG Mailing list. Many folks replied of missing route objects there and it seems to be limited to IRINN members only. I also asked the same question on APNIC mailing list and it was again confirmed about the issue. Before I proceed further, here’s what it is all about.
I am in Chiang Mai, Thailand for APNIC 48 conference. Earlier today attended APIX meeting where many IX members from Asian community gave an update including NIXI i.e National Internet Exchange of India. As per the update NIXI now allows content players to peer at the exchange. NIXI earlier had a strict requirement of telecom license for anyone to peer but as of now it allows anyone with IP address and AS number to be part of the exchange just like all other exchanges.
And it’s less than a week before the INNOG 2 i.e Indian Network Operators Group Conference 2. We (Indians) are little late to start a NOG but it’s finally working out and this is the 2nd event. First one happened last year. Event website: www.innog.net Why INNOG is important and why we should care? Well, having a functional NOG is as important for local community as a working Internet Exchange Point.
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). Traceroutes Amazon India to Vodafone India traceroute to 220.127.116.11 (18.104.22.168), 30 hops max, 60 byte packets 1 ec2-52-66-0-128.ap-south-1.compute.amazonaws.com (22.214.171.124) 21.861 ms ec2-52-66-0-134.
One of frequent email and contact form message I get my blog is about available content networks in India and where one can peer. There are certain content networks in India and of course most of the content networks have open peering policy and are usually happy with direct inter-connection (we call as “peering”) with the ISP networks (often referred to as “eyeball networks”). Some of these networks have a backbone which connects back to their key datacenter locations on their own circuits via Singapore/Europe, some other have simply placed their caching server where cache fill happens over IP transit.