Bsccl

This post analyses impact of cancellation of Bangladesh’s transit aggrement for India. It comparies latency via local Vs Bangladeshi paths.

A few weeks back I got in touch with Marc from Meghalaya. He offered to host RIPE Atlas probe at Shillong and that’s an excellent location which isn’t there on RIPE Atlas coverage network yet. It took around 5 days for the probe to reach Shillong from Haryana. I think probably this probe is the one at the most beautiful place in India. :) Now that probe is connected, I thought to look into routing which is super exciting for far from places like Shillong. Marc has a BSNL FTTH connection & mentioned about not-so-good latency. Let’s trace to 1st IP of the corresponding /24 pool on which probe is hosted:

Last month India & Bangladesh went into an agreement for power and bandwidth. India stated export of an additional 100MW of power to Bangladesh while Bangladesh started a 10Gbps link to Indian state of Tripura. (News article on this here)

Tripura is an Indian state having its boundaries with Bangladesh as you can see in above map. Coming to routing side of things setup is that BSNL (AS9829) is buying IP transit from Bangladesh Submarine Cable Co. Ltd (BSCCL) at $1.2 million / year. This means a cost of around $10/Mbps/month or 662Rs/Mbps/month. It’s hard to say if it’s good or bad since other link from BSNL is via it’s other links. But yes it’s good to see a layer 3 connectivity in terms of IP transit relationship rather then leasing dark fiber or L1 waves as they would have caused bit inefficient routing in the area. In order to do this BSNL has setup a “gateway node” at Agartala. I think it would be pretty much a node with approvals under ILD from doT and extremely likely a LIM device for lawful interception.   Months before it actually came up, Dyn research tweeted about this visible routing relationship.