SEA-ME-WE-4 Submarine Cable Fiber Repeater Problem Effect Internet Service of BTCL

From an unauthenticated Source, I got information that the Submarine Cable SEA-ME-WE-4 cable which is only Submarine cable connect Bangladesh to Worldwide Network of Internet Having Problem caused BTCL to route all of their traffic via only one peer which is Seabone in Italy.

Source also added that malfunction of SEA-ME-WE-4 Submarine Cable Fiber Repeater Near a place something called like 'Marakka' or Country name 'Morokko' fource BTCL to force ALL Internet Traffic via their other gateway peer which is Seabone Italy. BTCL even can't connect to TATA Communication, the default and main Gateway of them.

As my source is low in education, so there might a possibility of location of problem he told me over phone.

Let me check more deeply so that I can be sure about the problem and update you soon.

Please Visit Again and Again to get updated news regarding this issue or you can subscribe via RSS or Email so that any update posted here will directly delivery to your inbox or website.

By the way, the other IIGW called Mango Teleservice (MangoTEL) is having no problem. At this moment I am writing via an ISP connected through MangoTEL.

Thank You

Noor Ahamed Bauani
Freelance IT Consultant
Specially for Internet Routing on both protocol named IPv4 and IPv6
Need an Native or Dual stack IPv6 Connectivity? Just Knock me!
HP: +880-1818-BAUANI (SMS Only, No Direct Call Please)
-------------------------------------------------------------------------------------------------------
Give Me Sunshine, Give Me Some Rain, Give Me a Chance to Grow up Again




Updates: 


1. An high official of BTCL who don't want to discloser his name has confirm the malfunction of SEA-ME-WE-4 Submarine Cable Fiber Repeater, which is making BTCL in pressure of traffic. He also request to all ISP to limit their bandwidth and block unnecessary service or low priority like P2P applications, browsing of porn other game website etc.


2. See bellow the 'traceroute' from both BTCL and Mango. By the way, as I am on GSM Network, ignore the time to reach the next destination and for privacy, first few path has been removed. Please have a look, by the way both target traceroute is same, the IP of Google's Public DNS server (8.8.8.8)

A. Trace 8.8.8.8 from BTCL Network:


# 123.49.13.90 (123.49.13.90)  2.791 ms  6.709 ms  7.212 ms 149.038 ms pos1-8.palermo9.pal.seabone.net 3.144.181.117)  148.469 ms pos15-6.palermo9.pal.seabone.net (213.144.181.129)  149.745 ms
# 72.14.218.58 (72.14.218.58)  182.717 ms  187.404 ms  186.616 ms
# 72.14.218.58 (72.14.218.58)  183.052 ms  182.623 ms  182.319 ms
# 209.85.249.54 (209.85.249.54)  183.091 ms  190.724 ms 216.239.47.128 (216.239.47.128)  199.077 ms
# 209.85.251.113 (209.85.251.113)  198.907 ms  198.664 ms  198.311 ms
# 209.85.254.112 (209.85.254.112)  185.146 ms  186.016 ms 209.85.254.118 (209.85.254.118)   200.709 ms
# * 209.85.249.166 (209.85.249.166)  195.788 ms *
# google-public-dns-a.google.com (8.8.8.8)  183.568 ms  182.818 ms  182.707 ms

B. Now Check Mango on same destination (Sorry I had to use Windows tracert command: 

 #   607 ms   497 ms   359 ms  119.30.37.5

 #   434 ms   460 ms   358 ms  119.30.37.5

 #   793 ms   598 ms   478 ms  202.56.5.65

 #   631 ms   621 ms   598 ms  gi1-3.gsr-7609.dhk-gsr-01.mango.com.bd [114.130.1.13]

 #   474 ms   599 ms   496 ms  gi1-3.gsr-7609.dhk-gsr-01.mango.com.bd [114.130.1.13]

 #   492 ms   496 ms   502 ms  74.125.51.217

 #  1333 ms   543 ms   698 ms  74.125.51.217

 #  1266 ms   705 ms   598 ms  216.239.47.128

 #   950 ms   700 ms   598 ms  216.239.47.128

 #   968 ms   663 ms   598 ms  209.85.249.234

 #   554 ms   460 ms   520 ms  209.85.254.126

 #  1074 ms   718 ms   742 ms  google-public-dns-a.google.com [8.8.8.8]

Trace complete.

Update will be posted continuing till the problem is resolved. 

By Ahamed Bauani on 18:06 BDT [GMT + 06]  

3. I have talked with several tech & non tech personal, specially to find out the what is happening there. Few Senior officer confirmed me that they are working hard to restore normal peering with partners but it might take time till the Repeater replaced or repaired.  During this time they request Seabone to increase the capacity so that the impact on end user become low. He also said Seabone has already increased the capacity and working to give more capacity. The person who informed is an senior level official of BTCL and I can relay on him.

By Ahamed Bauani on 20:06 BDT [GMT + 06]

4. It seems that BTCL has successfully take care of the incident. Though the fiber problem still in place, BTCL manage to give all most 80+% of service to it's user. This is really nice. At last BTCL is active.

ALL Thanks & Credits goes to BTCL's Top to Low Level Engineers. We are (We the ISPs are) very happy to see this type of prompt service from BTCL. And hope BTCL will continue this type of support in future.

By Ahamed Bauani on 13:28 BDT [GMT + 06]

5. LAST UPDATE: Today, 7th November, 2010 from Aprox 02:00 to 03:25 Hour BDT [GMT + 06] BTTB Internet was DOWN. I have confirmed it from different source and every source expect BTCL has confirm the downtime. It seems that BTCL has properly restore it's full capacity during the downtime. But BTCL should issue some kind of Preses Release or Possible Maintainability Schedule before starting the job. So user like us can get prepared to take care of customer support issue.

Anyway, I hope this is the end of This issue, if anything arise again, I will start thread. Thanks to all for your support.  

By

Ahamed Bauani
Freelance IT Consultant
Advance & Complex Routing Expert
Both on IPv4 & IPv6
Need an IPv6 Connectivity? Just Knock me!

HP: +880-1818-BAUANI (SMS Only, No Direct Call Please)
--------------------------------------------------------------------------------
Give Me Sunshine, Give Me Some Rain, Give Me a Chance to Grow up Again