On weekend I was looking at BGP Instability Report data. As usual (and unfortunately) BSNL tops that list. BSNL is the most unstable autonomous network in the world. In past, I have written previously about how AS9829 is the rotten IP backbone.
This isn’t a surprise since they keep on coming on top but I think it’s well worth a check on what exactly is causing that. So I looked into BGP tables updates published on Oregon route-views from 21st May to 27th May and pulled data specifically for AS9829.
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.
Last night I was looking at routing tables and saw a interesting case where for a specific route.
Here’s what I got from Tata’s AS6453 looking glass:
Router: gin-ldn-core4 Site: UK, London, LDN Command: show ip bgp 117.219.227.229 BGP routing table entry for 117.219.224.0/20 Bestpath Modifiers: deterministic-med Paths: (4 available, best #4) Multipath: eBGP 17 18 19 33765 1299 3549 9829, (received-only) ix-3-1-2.core4.LDN-London. from ix-3-1-2.core4.LDN-London. (ix-3-1-2.core4.LDN-London.) Origin IGP, valid, external 4755 9829 mlv-tcore2.
An interesting evening here in village. From today sessional tests started at college and so does my blog posts too (to keep myself with positive energy!) ;)
Learned something new while troubleshooting. :)
I am used to getting latency of ~350ms with my server in Europe as I have mentioned in my past blog posts.
My connection > Server goes direct but return path goes via US and this is what increases latency.