And here goes my first post for 2017. The start of this year did not go well as I broke my hand in Jan and that resulted in a lot of time loss. Now I am almost recovered and in much better condition. I just attended HKNOG 4.0 at Hong Kong followed by APRICOT 2017 at Ho Chi Minh, Vietnam. an event and I enjoyed the both. Here’s my presentation from APRICOT 2017.
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.
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.
It has been super boring evening considering my sessional tests tomorrow. Test time is dull as always. I have been precisely measnuring latency on BSNL link from BSNL Haryana to Singapore based servers. The fluctuation in latency is pretty much common now. Someones we get 120ms latency to Singapore (an expected number based on distance) while other time it goes off as high as 310ms. Latency with openDNS nodes in Singapore makes it pretty much poor to use openDNS here.
Quick traceroute between Reliance and Neotel (South African subsidiary of Tata Communications) Using Reliance Mumbai node: You requested a Traceroute from Mumbai (184.108.40.206) to neotel.co.za (220.127.116.11) 1 ge-0-2-0.0.pjr02.mmb004.flagtel.com (18.104.22.168) 80.252 ms 79.822 ms 79.737 ms MPLS Label=351552 CoS=0 TTL=1 S=1 2 so-1-3-0.0.pjr02.hkg005.flagtel.com (22.214.171.124) 79.688 ms 79.717 ms 79.779 ms MPLS Label=301328 CoS=0 TTL=1 S=1 3 so-5-0-0.0.cjr04.hkg003.flagtel.com (126.96.36.199) 79.790 ms 81.271 ms 84.868 ms MPLS Label=300272 CoS=0 TTL=1 S=1 4 xe-1-2-0.0.cji01.hkg003.flagtel.com (62.