It’s kind of fun times in India with many IX’es showing up and now NIXI finally removing their traffic wise charge.
I came across this email which they sent to their member networks recently:
From: I X <[ix@nixi.in](mailto:ix@nixi.in)\> Sent: Thu, 21 Feb 2019 12:48:31 GMT+0530 To: "members " <[members@nixi.in](mailto:members@nixi.in)\> Cc: "[ceo@nixi.in](mailto:ceo@nixi.in)" <[ceo@nixi.in](mailto:ceo@nixi.in)\> Subject: Change in Data Transfer Charges (X-Y) Dear Members, In reference to the Board's direction to reduce the current data transfer (X-Y) charges from Re.
Seems like NPIX traffic has started hitting 1Gbps levels and that is just so amazing. Came across this post by Niranjan.
NPIX or Nepal Internet Exchange is located in Kathmandu and operates out of its own datacenter. There’s a huge amount of (overhead) dark fibre availability in Kathmandu and as of the writing of this post I see 30 members at NPIX. 1Gbps might seem low from Western IX’es standards but that’s a quite good amount of traffic for an IX in South Asian region.
Today I was having a chat with my friend Hari Haran. He mentioned that Facebook has started its PoP in Mumbai. This seems true and Facebook has mentioned GPX Mumbai as their private peering PoP in their peeringdb record.
I triggered a quick test trace to “www.facebook.com” on IPv4 from all Indian RIPE Atlas probes and resolved “www.facebook.com” on the probe itself. The lowest latency is from Airtel Karnataka and that’s still hitting Facebook in Singapore.
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.
So it seems like apart from voice interconnect issues, Jio is also facing routing issues on the backbone. I ran a trace to one of IP’s on Jio network allocated to end customer - 169.149.212.122. I ran trace from all Indian RIPE Atlas probes measurement here. There seem quite a few RIPE Atlas probes which are giving latency on 150ms + range. Seems like they are downstream or downstream of downstream of Tata Comm’s AS4755 and routing is happening via Singapore!