Yesterday there was an article in the Indian paper Financial Express with the title “OTTs may have to pay access charge to telcos”.
Quoting a few points from the article:
Social media intermediaries like WhatsApp, Facebook and Twitter, and over-the-top (OTT) players like Netflix, Prime Video and Disney+Hotstar may have to pay a carriage charge to telecom service providers Data, particularly video, comprises 70% of the overall traffic flow on telecom networks, and this would grow further with the rollout of 5G services Upon reference from the DoT, Trai is currently studying various possible models under which OTTs can be brought within the purview of some form of regulation According to sources, an interconnect regime is a must between OTTs and telcos because as 5G services grow, there would be immense data/ video load on networks, which may lead to them getting clogged or even crashing at times.
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!
Sometimes we see interesting IP’s in traceroute & they confuse lot of people.
I have seen this topic in discussion twice on NANOG and once on Linux Delhi user group. OK - let’s pick an example: anurag:~ anurag$ traceroute 71.89.140.11 traceroute to 71.89.140.11 (71.89.140.11), 64 hops max, 52 byte packets 1 router (10.10.0.1) 1.176 ms 0.993 ms 0.941 ms 2 117.220.160.1 (117.220.160.1) 20.626 ms 29.101 ms 19.216 ms 3 218.248.169.122 (218.
And college started after pretty good holi holidays. Again having bit painful time due to hot weather and this is just start of summers. Well all I can hope is that there won’t be voltage issues in village again (like last time). And just to make sure on that part - I have put 2 RTI’s asking Power department about their preparation details. :)
Anyways coming on blog post topic for the day - the effect of “next-hop-self” at an IXP when there are peers as well as transit customers of a network.
Fest time at college - Good since I get lot of free time to spend around looking at routing tables. It’s always interesting since last week was full of some major submarine cable cuts and has huge impact on Indian networks.
Anyways, an interesting issue to post today about Global IPv6 routing . There are “dark spots” in global IPv6 routing because of peering dispute between multiple tier 1 ISPs involving Hurricane Electric (AS6939) & Cogent Communications (AS174).