Reliance-Globalcom

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. I recently I came across some of crazy confusing traceroutes as passed by one of my friends. I cannot share that exact traceroute on this blog post but can produce the same effect about which I am posting by doing a trace from one of large network like Telia London PoP to one of the Indian destinations via their looking glass

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. Prefixes I have seen so far:

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.   Based on my collected data and BGPlay’s routing records, here’s what’s happening. My IP is coming /20 BGP annoucement from BSNL Autonomous System 9829 - 117.207.48.0/20. Looking at BGP table records for that block from BGPlay’s routing data archive source.

Quick traceroute between Reliance and Neotel (South African subsidiary of Tata Communications)

Using Reliance Mumbai node: 

You requested a Traceroute from Mumbai (62.216.135.130) to neotel.co.za (41.168.1.110) 

   1 ge-0-2-0.0.pjr02.mmb004.flagtel.com (85.95.25.70) 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 (85.95.25.118) 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 (85.95.25.214) 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.216.128.66) 79.504 ms 79.587 ms 79.452 ms  
   5 62.216.145.194 (62.216.145.194) 85.660 ms 79.769 ms *  
   6 if-2-0-0-1123.core3.HK2-HongKong.as6453.net (216.6.95.137) [AS 6453] 79.930 ms 79.884 ms 79.775 ms  
   7 180.87.15.81 (180.87.15.81) [AS 6453] 295.413 ms 295.675 ms 295.695 ms  
   MPLS Label=300800 CoS=0 TTL=1 S=1  
   8 if-5-2.tcore2.CXR-Chennai.as6453.net (180.87.15.70) [AS 6453] 296.944 ms if-2-2.tcore1.SVW-Singapore.as6453.net (180.87.12.1) [AS 6453] 311.951 ms 311.784 ms  
   MPLS Label=299968 CoS=0 TTL=1 S=1  
   9 if-3-3.tcore1.CXR-Chennai.as6453.net (180.87.36.5) [AS 6453] 311.636 ms if-5-2.tcore1.CXR-Chennai.as6453.net (180.87.12.54) [AS 6453] 312.689 ms 312.041 ms  
   MPLS Label=300688 CoS=0 TTL=1 S=1  
  10 if-4-0-0.core1.CFO-Chennai.as6453.net (180.87.36.18) [AS 6453] 144.922 ms if-15-1-0.core1.CFO-Chennai.as6453.net (180.87.36.14) [AS 6453] 145.223 ms if-4-0-0.core1.CFO-Chennai.as6453.net (180.87.36.18) [AS 6453] 144.627 ms  
   MPLS Label=1578 CoS=0 TTL=1 S=1  
  11 116.0.86.1 (116.0.86.1) [AS 6453] 155.796 ms 155.857 ms 154.918 ms  
   MPLS Label=3107 CoS=0 TTL=1 S=1  
  12 116.0.86.30 (116.0.86.30) [AS 6453] 341.019 ms 312.304 ms 322.348 ms  
   MPLS Label=306816 CoS=0 TTL=1 S=1  
  13 if-2-2.tcore1.JSO-Johannesburg.as6453.net (216.6.55.85) [AS 6453] 312.133 ms 311.860 ms 311.718 ms  
  14 216.6.55.38 (216.6.55.38) [AS 6453] 324.450 ms 295.062 ms 296.033 ms  
  15 41.160.0.243 (41.160.0.243) [AS 36937] 312.371 ms 313.074 ms 311.998 ms  
  16 * * *  
  17 * * *  
  18 * * *

	

		Read more…