Today a friend from Pakistan informed about SMW4 outage. He reported about issues in Pakistan.

It seems like SMW4 is damaged near Egypt and that is what causing high load on East Asian routes giving pretty high latency.

I am at my home and sitting BSNL’s network and latency with Europe has jumped terribly to 700-800ms. Right now I do not see a direct route to Europe and it’s rather taking East Asia > US > Europe routes right now on other cable networks.

Quick view on some of traceroutes:

To Facebook.com

anurag:~ anurag$ traceroute -a www.facebook.com
traceroute to star.c10r.facebook.com (69.171.229.25), 64 hops max, 52 byte packets
1 [AS65534] router02 (10.10.0.1) 1.759 ms 1.018 ms 0.869 ms
2 [AS9829] 117.220.160.1 (117.220.160.1) 18.184 ms 18.809 ms 17.962 ms
3 [AS9829] 218.248.169.126 (218.248.169.126) 28.761 ms 28.648 ms 28.352 ms
4 [AS4755] 115.114.57.165.static-mumbai.vsnl.net.in (115.114.57.165) 77.803 ms 63.059 ms 61.319 ms
5 [AS3549] 172.29.250.33 (172.29.250.33) 63.106 ms 62.755 ms 63.853 ms
6 * * *
7 [AS4755] 115.114.85.233 (115.114.85.233) 64.694 ms 63.013 ms 61.133 ms
8 * [AS0] if-7-2.tcore1.cxr-chennai.as6453.net (180.87.36.34) 531.243 ms *
9 [AS0] if-5-2.tcore1.svw-singapore.as6453.net (180.87.12.53) 566.615 ms 906.432 ms *
10 * * *
11 [AS0] if-2-2.tcore1.tv2-tokyo.as6453.net (180.87.180.1) 577.953 ms 542.487 ms *
12 * [AS0] if-9-2.tcore2.pdi-paloalto.as6453.net (180.87.180.17) 538.170 ms 617.144 ms
13 * [AS3549] te1-4-10g.ar1.pao2.gblx.net (208.51.134.97) 673.785 ms *
14 * [AS22566] xe10-3-1-10g.scr3.snv2.gblx.net (67.17.79.169) 563.667 ms 631.657 ms
15 [AS22566] e8-1-20g.ar5.sjc2.gblx.net (67.16.145.118) 554.785 ms * *
16 [AS3549] 64.208.158.30 (64.208.158.30) 535.164 ms 573.485 ms 546.552 ms
17 [AS32934] ae1.bb02.sjc1.tfbnw.net (204.15.21.164) 580.511 ms * 529.838 ms
18 [AS32934] ae12.bb02.prn1.tfbnw.net (74.119.79.109) 543.454 ms 569.572 ms
[AS32934] ae16.bb01.prn1.tfbnw.net (31.13.24.254) 659.153 ms
19 [AS32934] ae1.dr02.prn1.tfbnw.net (74.119.79.107) 567.662 ms *
[AS32934] ae1.dr05.prn1.tfbnw.net (204.15.23.61) 560.851 ms
20 * * *
21 * * *
22 *^C
anurag:~ anurag$

Route to Europe:

anurag:~ anurag$ traceroute -a server7.anuragbhatia.com
traceroute to server7.anuragbhatia.com (178.238.225.247), 64 hops max, 52 byte packets
1 [AS65534] router02 (10.10.0.1) 1.797 ms 0.989 ms 1.015 ms
2 [AS9829] 117.220.160.1 (117.220.160.1) 21.046 ms 18.046 ms 18.068 ms
3 [AS9829] 218.248.169.126 (218.248.169.126) 244.155 ms 28.669 ms 28.922 ms
4 [AS4755] 115.114.57.165.static-mumbai.vsnl.net.in (115.114.57.165) 62.840 ms 61.595 ms 60.564 ms
5 [AS0] 172.31.16.193 (172.31.16.193) 91.433 ms 94.132 ms 94.564 ms
6 [AS6453] if-2-606.tcore1.njy-newark.as6453.net (66.198.70.121) 529.370 ms * *
7 * [AS6453] 66.110.59.66 (66.110.59.66) 566.573 ms *
8 [AS1299] nyk-bb1-link.telia.net (80.91.252.226) 614.390 ms * *
9 * * [AS1299] ffm-bb1-link.telia.net (213.155.131.146) 697.499 ms
10 * [AS1299] mcn-b2-link.telia.net (213.155.134.13) 733.122 ms 721.410 ms
11 * [AS1299] gw02.contabo.net (213.248.101.78) 731.281 ms *
12 * * [AS51167] server7.anuragbhatia.com (178.238.225.247) 702.811 ms
anurag:~ anurag$

 

Issues seems not isolated to BSNL or Tata but also with Airtel.

E.g Airtel Delhi PoP to London:

Wed Mar 27 16:28:59 GMT+05:30 2013
traceroute 62.239.237.1

Type escape sequence to abort.
Tracing the route to 62.239.237.1

1 203.101.100.29 [MPLS: Label 716197 Exp 0] 84 msec
182.79.254.242 [MPLS: Label 716197 Exp 0] 84 msec
203.101.95.146 [MPLS: Label 677302 Exp 0] 80 msec
2 125.21.80.161 [MPLS: Label 406905 Exp 0] 156 msec
203.101.95.141 [MPLS: Label 406905 Exp 0] 76 msec
202.56.223.205 [MPLS: Label 406905 Exp 0] 92 msec
3 203.101.95.117 [MPLS: Label 569896 Exp 0] 120 msec 40 msec
203.101.100.205 [MPLS: Label 389360 Exp 0] 52 msec
4 182.79.255.18 92 msec
182.79.255.14 88 msec 88 msec
5 BHA-0007.gw1.sin0.asianetcom.net (203.192.168.53) 176 msec 180 msec 172 msec
6 te0-3-0-0.wr1.sin0.asianetcom.net (61.14.157.233) [AS 10026] 184 msec 184 msec 216 msec
7 gi3-0-0.cr2.nrt1.asianetcom.net (61.14.157.158) [AS 10026] 248 msec 248 msec 244 msec
8 po5-0-0.gw3.lax1.asianetcom.net (202.147.0.38) [AS 10026] 428 msec 432 msec 420 msec
9 linx7.ukcore.bt.net (195.66.224.56) [AS 10026] 388 msec 388 msec 388 msec
10 *
core1-te0-3-0-1.ealing.ukcore.bt.net (62.172.102.2) [AS 2856] 384 msec 392 msec
11 core1-pos1-0.birmingham.ukcore.bt.net (62.172.103.81) [AS 2856] 384 msec 384 msec 384 msec
12 iar1-gig5-4.birmingham.ukcore.bt.net (62.6.196.94) [AS 2856] 392 msec 388 msec 448 msec
13 62.172.57.218 [AS 2856] 384 msec 432 msec 392 msec
14 * * *

 

If we look at Tata AS6453’s routing table at Mumbai for a Europe based IP:

And here we get latest EIG cable i.e Euro India Gateway cable in action. Although cable was up few months back, but it’s now we are getting some changes in routing table up. (Probably earlier was test mode?).

Here’s a map of EIG cable.

This was very interesting project because of few reasons – firstly it is one (of few) cable consortium’s where India’s biggest State owned telco BSNL (also known as NIB – National Internet Backbone). Apart from that, it is one of direct link between India and UK. Earlier main route was from Mumbai to France (VSNL-Tata route) and next domestic Europeon bones Lamdanet, Telia, Level3 etc used to carry data further.

Also, bharti airtel was also one of holders in consortium for EIG.

Here are a couple of interesting BGP announcements from BSNL-NIB ASN 9829 (from US based ISP – Hurricane Electric server)

It seems like BSNL is now purchasing bandwidth in bulk from London. Afterall EIG cable lands from Mumbai landing station directly in London. This will surely help in bringing cost of bandwidth down for BSNL thus leading to cheaper high speed plans.

Here’s one of interesting traceroutes:

traceroute to comcast.com (69.241.45.4), 30 hops max, 60 byte packets

1  192.168.1.100 (192.168.1.100) [AS8151/AS28513]  1.529 ms  2.151 ms  2.693 ms

2  117.207.48.1 (117.207.48.1) [AS9829]  26.731 ms  30.480 ms  31.713 ms

3  218.248.173.38 (218.248.173.38) [AS9829]  33.999 ms  36.616 ms  40.542 ms

4  12.89.56.25 (12.89.56.25) [AS7018]  309.255 ms  311.519 ms  314.201 ms

5  cr84.n54ny.ip.att.net (12.122.105.126) [AS7018]  336.292 ms  337.229 ms  338.124 ms

6  cr2.n54ny.ip.att.net (12.122.115.93) [AS7018]  343.377 ms  304.058 ms  325.154 ms

7  n54ny01jt.ip.att.net (12.122.81.69) [AS7018]  400.521 ms  400.990 ms  401.362 ms

8  te-1-13-0-4-pe01.111eighthave.ny.ibone.comcast.net (75.149.231.45) [AS7922]  363.936 ms te-1-12-0-4-pe01.111eighthave.ny.ibone.comcast.net (75.149.230.169) [AS7922]  323.262 ms 192.205.37.34 (192.205.37.34) [*]  373.792 ms

9  pos-3-0-0-0-cr01.newyork.ny.ibone.comcast.net (68.86.85.21) [AS7922]  371.198 ms  373.264 ms  375.889 ms

10  68.86.93.2 (68.86.93.2) [AS7922]  394.699 ms  397.320 ms  404.337 ms

11  te-1-1-ar02.philadelphia.pa.bo.comcast.net (68.85.215.178) [AS33657]  416.498 ms  418.828 ms  421.190 ms

12  te-5-1-ar01.newcastle.de.bo.comcast.net (68.86.228.85) [AS7922]  316.476 ms  318.557 ms  317.698 ms

13  te-0-3-0-0-ar01.westchester.pa.bo.comcast.net (68.86.228.81) [AS7922]  320.100 ms  320.596 ms  321.278 ms

14  te-4-1-ur07.westchester.pa.bo.comcast.net (68.85.215.146) [AS33657]  318.588 ms  315.323 ms  316.424 ms

15  ext-ssl01.westchester.pa.bo.comcast.net (76.96.69.5) [AS7922]  316.344 ms  350.379 ms  353.261 ms

So At&t acting as upstream carrier for BSNL 🙂

Baby bell – yay!

I think we are soon going to see speeds getting further up on DSL ….probably from 512Kbps to 1Mbps or 2Mbps in upcoming months. And you will see something like….

Hope to see you on faster broadband next time!