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!
It’s great to see Amazon announcement two days back about launch of their region in Mumbai. In past I was quite happy to see their Cloudfront CDN PoPs in Mumbai & Chennai (blog post here). Now it’s just great to see a full AWS region out of Mumbai. :) Though it’s going to eat most of important customers from the smaller players still it’s good for industry as industry is too big and we need more & more of such large Cloud players in India to bring more and more content hosting in India.
So last month I had a wonderful trip to Bangladesh for bdNOG. This is bit delayed. Some thoughts on infrastructure
In terms of infrastructure - roads & traffic, power, quality of builds - it seemed like India in 2000’s. Specifically roads and traffic was bit terrible and even as an Indian (who manages to drive in Indian traffic!) I still got scared out of traffic in Dhaka. Speeds, roughness and overtaking is pretty high.
There seems be an ongoing route leak by AS49505 (Selectel, Russia) for K root server.
K root server’s IP: 193.0.14.129 Origin Network: AS25152 Here’s trace from Airtel Looking Glass, Delhi PoP
Mon Oct 26 16:21:18 GMT+05:30 2015 traceroute 193.0.14.129 Mon Oct 26 16:21:22.053 IST Type escape sequence to abort. Tracing the route to 193.0.14.129 1 \* 203.101.95.146 19 msec 4 msec 2 182.79.224.73 14 msec 3 msec 1 msec 3 14.
K root in Noida seems to be not getting enough traffic from quite sometime and connectivity does seems bit broken. This is a blog post following up to Dyn’s excellent and detailed post about how TIC leaked the world famous 193.0.14.0/24 address space used by AS25152. It was good to read this post from RIPE NCC written by my friend Emile (and thanks to him for crediting me to signal about traffic hitting outside!