Posts

Day before yesterday i.e on 18th August 2016 Bangladesh’s TLD .bd went had an outage. It was originally reported by Jasim Alam on bdNOG mailing list.

dig btcl.com.bd @8.8.8.8
; <<>> DiG 9.10.4-P2 <<>> btcl.com.bd @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 8114
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;btcl.com.bd.                   IN      A
;; Query time: 76 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Thu Aug 18 14:24:25 Bangladesh Standard Time 2016
;; MSG SIZE  rcvd: 40

His message shows that DNS resolution of BTCL (Bangladesh Telecommunications Company Ltd) was failing. Later Alok Das that it was the power problem resulting in outage. Let’s look ask one of 13 root DNS server about NS records on who has the delegation for .bd.

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, ? - incomplete
RPKI validation codes: V valid, I invalid, N Not found
     Network          Next Hop            Metric LocPrf Weight Path
 *   47.35.0.0/16     195.208.112.161                        0 3277 3267 174 64049 55836 i
 *                    217.192.89.50                          0 3303 6762 64049 55836 i
 *                    212.66.96.126                          0 20912 1267 64049 55836 i
 *                    162.243.188.2                          0 393406 6453 6762 64049 55836 i
 *                    192.241.164.4                          0 62567 2914 174 64049 55836 i
 *                    129.250.0.11          1007             0 2914 174 64049 55836 i
 *                    104.192.216.1                          0 46450 174 64049 55836 i
 *                    202.93.8.242                           0 24441 3491 3491 174 64049 55836 i
 *                    66.59.190.221                          0 6539 577 6762 64049 55836 i
 *                    144.228.241.130         80             0 1239 174 64049 55836 i
 *                    207.172.6.20             0             0 6079 3356 174 64049 55836 i
 *                    203.62.252.83                          0 1221 4637 174 64049 55836 i
 *                    93.104.209.174                         0 58901 51167 3356 6762 64049 55836 i
     Network          Next Hop            Metric LocPrf Weight Path
 *                    162.250.137.254                        0 4901 174 64049 55836 i
 *                    4.69.184.193             0             0 3356 174 64049 55836 i
 *                    208.51.134.254           1             0 3549 3356 174 64049 55836 i
 *                    89.149.178.10           10             0 3257 174 64049 55836 i
 *                    66.110.0.86                            0 6453 6762 64049 55836 i
 *                    134.222.87.1           650             0 286 174 64049 55836 i
 *                    95.85.0.2                              0 200130 6453 174 64049 55836 i
 *                    12.0.1.63                              0 7018 174 64049 55836 i
 *                    173.205.57.234                         0 53364 3257 174 64049 55836 i
 *                    206.24.210.80                          0 3561 174 64049 55836 i
 *                    5.101.110.2                            0 202018 2914 174 64049 55836 i
 *                    207.172.6.1              0             0 6079 3356 174 64049 55836 i
 *                    154.11.98.225            0             0 852 174 64049 55836 i
 *                    194.85.40.15                           0 3267 174 64049 55836 i
 *                    208.74.64.40                           0 19214 174 64049 55836 i
 *                    209.124.176.223                        0 101 101 174 64049 55836 i
 *                    66.185.128.48            6             0 1668 174 64049 55836 i
 *                    203.181.248.168                        0 7660 2516 6762 64049 55836 i
 *                    202.232.0.2                            0 2497 701 6762 64049 55836 i
 *                    103.247.3.45                           0 58511 64049 55836 i
 *                    193.0.0.56                             0 3333 1103 64049 55836 i
     Network          Next Hop            Metric LocPrf Weight Path
 *                    80.241.176.31                          0 20771 47872 64049 55836 i
 *>                   216.218.252.164                        0 6939 64049 55836 i
 *                    132.198.255.253                        0 1351 174 64049 55836 i
 *                    103.255.249.22                         0 58443 45177 64049 55836 i
 *                    114.31.199.1                           0 4826 174 64049 55836 i
route-views>

This shows Reliance Jio’s ASN AS55836 announcing 47.35.0.0/16. Charter Communications (AS20115) is originating multiple of /18s out of the same pool.  

So last week I couldn’t hold off my curiosity about world famous address “221b Baker Street”. I passed “Baker Street” tube station quite a few times and finally decided to just look for it. :) By time I reached the street it was lightly raining and I found few other (curious) people like me standing outside 221b Baker Street. It has got a museum for Sherlock Holmes (though was closed by the time I reached).

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.

I just presented data on Performance of Root DNS anycast in UK & Ireland at INEX meeting.

Last week while travelling to London from Delhi IGI airport I was standing in immigration queue. One of fellow passenger (likely from Bihar as per my guess from his accent) came right behind me. He was bit afraid and asked me in low voice if those (immigration) gates would get him to his flight for Dubai. I smiled and told him that it’s common passage for everyone travelling to just anywhere and explained to him about his gate by looking at his boarding pass. By this time he appeared less worried and stood silently behind me. After few mins as queue proceeded a group of 4 travellers (again of similar profile) proceeded to immigration desk and I heard multiple immigration officers screaming/shouting on them for coming to their desk without boarding pass. I even heard a loud noise.

I just visited Moscow last week for attending ENOG 11. Some quick pictures from this short trip.

Just saw this excellent TEDx talk by Ritu Karidha (ISRO Scientist & Dept. Operations director, ISRO Mars Mission). It tells about some really hard challenges of the mission and the fact that still ISRO succeeded. :)

Last month India & Bangladesh went into an agreement for power and bandwidth. India stated export of an additional 100MW of power to Bangladesh while Bangladesh started a 10Gbps link to Indian state of Tripura. (News article on this here)

Tripura is an Indian state having its boundaries with Bangladesh as you can see in above map. Coming to routing side of things setup is that BSNL (AS9829) is buying IP transit from Bangladesh Submarine Cable Co. Ltd (BSCCL) at $1.2 million / year. This means a cost of around $10/Mbps/month or 662Rs/Mbps/month. It’s hard to say if it’s good or bad since other link from BSNL is via it’s other links. But yes it’s good to see a layer 3 connectivity in terms of IP transit relationship rather then leasing dark fiber or L1 waves as they would have caused bit inefficient routing in the area. In order to do this BSNL has setup a “gateway node” at Agartala. I think it would be pretty much a node with approvals under ILD from doT and extremely likely a LIM device for lawful interception.   Months before it actually came up, Dyn research tweeted about this visible routing relationship.  

Saw excellent movie “The Inside Job” on 2008 market crash. It nicely explains that in fine details, people & companies who were involved, how it happened and finally what Govt. did. I was amazed by funny part of story where they let one to insure against things which you they did not own!

Movie Trailer

Have fun!