nixi

Tata Communications (AS4755) pushing traffic to Reliance Jio (AS55836) via Singapore!

Anurag Bhatia
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!

K root server - Noida anycast and updates

Anurag Bhatia
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!

BSNL AS9829 - A rotten IP backbone

Anurag Bhatia
Today I met a good friend and he has recently moved back into Rohtak (like me!) and was crying over BSNL’s issues. He has issues of unstable DSL due to last mile and I told him that even if last mile works well, BSNL still has got ton of issues with their IP backbone traffic. It’s Sunday late night out here in India and I am having really pathetic connectivity with just everywhere except Google.

Notes from SANOG 26 - Mumbai

Anurag Bhatia
Just finished with SANOG 26 conference and tutorials. It went very nice. Interestingly this time conference did not start early morning like it did in SANOG 24 at Noida. It was rather late in afternoon. Also, on very good note - there were less Govt. bureaucrats to bore attendees with usual stuff they always talk about but have very little idea. One specific interesting presentation was Opportunities and Challenges for Broadband Wireless in India by Prof Abhay Karandikar (from IIT Mumbai).

Why NIXI AS24029 appears to be transit ASN?

Anurag Bhatia
And my post on 1st April. Don’t take it as April fool post ;) Multiple times NIXI’s AS24029 has been reported as acting like transit ASN for multiple networks. I have analysed it in past and this is very much because of route leaks by few specific networks. I have explained difference in peering Vs transit routes and their handling previously on my blog. In short: A network is supposed to re-announce it’s peering and transit routes only to customer and not to any other peer or upstream.