And it’s less than a week before the INNOG 2 i.e Indian Network Operators Group Conference 2. We (Indians) are little late to start a NOG but it’s finally working out and this is the 2nd event. First one happened last year.
Event website: www.innog.net
Why INNOG is important and why we should care? Well, having a functional NOG is as important for local community as a working Internet Exchange Point.
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!
Just noticed that Reliance Jio (AS55836) seems to be originating a /16 which is for Charter Communications (AS20115) - 47.35.0.0/16. route-views>sh ip bgp 47.35.0.0/16 long | exclude 20115 BGP table version is 18764390, local router ID is 128.223.51.103 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure, S Stale, m multipath, b backup-path, f RT-Filter, x best-external, a additional-path, c RIB-compressed, Origin codes: i - IGP, e - EGP, ?