Just noticed that Reliance Jio (AS55836) seems to be originating a /16 which is for Charter Communications (AS20115) - 188.8.131.52/16. route-views>sh ip bgp 184.108.40.206/16 long | exclude 20115 BGP table version is 18764390, local router ID is 220.127.116.11 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, ?
Today I spotted some routes from Amazon AWS Cloud services - AS16509 in Indian tables. AS16509 was originating prefixes while sitting in downstream of Tata-VSNL AS4755 and Reliance AS18101. I almost missed Amazon AWS's announcement on their blog about Indian PoPs for their DNS service - Route53 and CDN service - Cloudfront. New PoP’s of Amazon in India are at Mumbai and Chennai and I see pretty much consistent BGP announcements to Tata and Reliance from these locations.
And finally academic session over. Done with all vivas and related stuff. Next will be exams likely in June. Time for me to get ready for travel. :) Anyways an interesting topic for today’s post - Google Public DNS. Lot of us are familier with popular (and free) DNS resolvers 18.104.22.168 and 22.214.171.124. I have covered reason in previous posts on why it tends to fail with Content Delivery networks like Akamai which rely on anycasting at bottom DNS layer and simple unicasting on application servers.
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.