On Feb 9 10:30:54 BDT 2008 We are Getting BTTB Bandwidth FULL
BTTB Internet Link Problem is Solved. The SEA-ME-WE4 submarine cable has been cut in Alexandria of Egypt at January 30, 2008, suspending the BTTB's Internet connectivity
Today, January 9, 2008 10:30 BDT [GMT +6], we are getting FULL service from BTTB Internet Link. Seems The problem is solved. Though we are not sure that is it Permanent or Temporary, Now BTTB giving FULL Internet Bandwidth as per their agreement with Clients.
Also the latency between Bangladesh to Most of big transit providers is normal.
A little latency report: (From Host in Dhaka Running 'CentOS' as Operating System)
#### Bangladesh to Level 3 Communications, Inc. USA: ###
# date
Sat Feb 9 14:20:20 BDT 2008
# ping -c 5 4.2.2.1
PING 4.2.2.1 (4.2.2.1) 56(84) bytes of data.
64 bytes from 4.2.2.1: icmp_seq=1 ttl=243 time=207 ms
64 bytes from 4.2.2.1: icmp_seq=2 ttl=243 time=244 ms
64 bytes from 4.2.2.1: icmp_seq=3 ttl=243 time=249 ms
64 bytes from 4.2.2.1: icmp_seq=4 ttl=243 time=190 ms
64 bytes from 4.2.2.1: icmp_seq=5 ttl=243 time=240 ms
--- 4.2.2.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 190.804/226.334/249.182/23.091 ms
#
#### Bangladesh to www.yahoo.com (Random GEO IP) ###
#date
Sat Feb 9 14:55:40 BDT 2008
# ping -c 5 www.yahoo.com
PING www.yahoo-ht3.akadns.net (87.248.113.14) 56(84) bytes of data.
64 bytes from f1.us.www.vip.ird.yahoo.com (87.248.113.14): icmp_seq=1 ttl=55 time=222 ms
64 bytes from f1.us.www.vip.ird.yahoo.com (87.248.113.14): icmp_seq=2 ttl=55 time=218 ms
64 bytes from f1.us.www.vip.ird.yahoo.com (87.248.113.14): icmp_seq=3 ttl=55 time=234 ms
64 bytes from f1.us.www.vip.ird.yahoo.com (87.248.113.14): icmp_seq=4 ttl=55 time=250 ms
64 bytes from f1.us.www.vip.ird.yahoo.com (87.248.113.14): icmp_seq=5 ttl=55 time=247 ms
--- www.yahoo-ht3.akadns.net ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4001ms
rtt min/avg/max/mdev = 218.098/234.576/250.310/12.861 ms
#
#### Bangladesh to www.google.com (Random GEO IP) ###
# date
Sat Feb 9 14:56:12 BDT 2008
# ping -c 5 www.google.com
PING www.l.google.com (209.85.135.104) 56(84) bytes of data.
64 bytes from mu-in-f104.google.com (209.85.135.104): icmp_seq=1 ttl=244 time=200 ms
64 bytes from mu-in-f104.google.com (209.85.135.104): icmp_seq=2 ttl=244 time=239 ms
64 bytes from mu-in-f104.google.com (209.85.135.104): icmp_seq=3 ttl=244 time=225 ms
64 bytes from mu-in-f104.google.com (209.85.135.104): icmp_seq=4 ttl=244 time=230 ms
64 bytes from mu-in-f104.google.com (209.85.135.104): icmp_seq=5 ttl=244 time=230 ms
--- www.l.google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3998ms
rtt min/avg/max/mdev = 200.125/225.176/239.855/13.414 ms
#
#### Bangladesh to www.yahoo.com.in (Random GEO IP) ###
# ping -c 5 www.yahoo.co.in
PING gslb.fp.vip.in.g.internal.yahoo.com (202.43.219.47) 56(84) bytes of data.
64 bytes from in.beta.vip.in.yahoo.com (202.43.219.47): icmp_seq=1 ttl=51 time=343 ms
64 bytes from in.beta.vip.in.yahoo.com (202.43.219.47): icmp_seq=2 ttl=51 time=344 ms
64 bytes from in.beta.vip.in.yahoo.com (202.43.219.47): icmp_seq=3 ttl=51 time=311 ms
64 bytes from in.beta.vip.in.yahoo.com (202.43.219.47): icmp_seq=4 ttl=51 time=349 ms
--- gslb.fp.vip.in.g.internal.yahoo.com ping statistics ---
5 packets transmitted, 4 received, 20% packet loss, time 3997ms
rtt min/avg/max/mdev = 311.383/337.359/349.823/15.189 ms
#
#### Bangladesh to www.google.com.bd (Random GEO IP) ###
# ping -c 5 www.google.com.bd
PING www.l.google.com (209.85.135.104) 56(84) bytes of data.
64 bytes from mu-in-f104.google.com (209.85.135.104): icmp_seq=1 ttl=244 time=254 ms
64 bytes from mu-in-f104.google.com (209.85.135.104): icmp_seq=2 ttl=244 time=218 ms
64 bytes from mu-in-f104.google.com (209.85.135.104): icmp_seq=3 ttl=244 time=204 ms
64 bytes from mu-in-f104.google.com (209.85.135.104): icmp_seq=4 ttl=244 time=239 ms
64 bytes from mu-in-f104.google.com (209.85.135.104): icmp_seq=5 ttl=244 time=224 ms
--- www.l.google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4001ms
rtt min/avg/max/mdev = 204.090/228.245/254.348/17.377 ms
#
##### Bangladesh to www.hotmail.com (Random GEO IP) ###
# ping -c 5 www.hotmail.com
PING www.hotmail.aate.nsatc.net (211.206.123.219) 56(84) bytes of data.
64 bytes from 211.206.123.219: icmp_seq=1 ttl=51 time=375 ms
64 bytes from 211.206.123.219: icmp_seq=2 ttl=51 time=386 ms
64 bytes from 211.206.123.219: icmp_seq=3 ttl=51 time=335 ms
64 bytes from 211.206.123.219: icmp_seq=4 ttl=51 time=372 ms
64 bytes from 211.206.123.219: icmp_seq=5 ttl=51 time=379 ms
--- www.hotmail.aate.nsatc.net ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3996ms
rtt min/avg/max/mdev = 335.375/369.885/386.453/17.866 ms
# date
Sat Feb 9 15:03:50 BDT 2008
#exit
By this TEST using 'Ping' It is sure that BTTB Internet is now normal at this moment. More test is needed to find out the actual. No BTTB official is available at this moment to discuss the issue.
........
Let's Give Command inside my Mind:
[root@INSID-BAUANI~]#echo $MYSTATUS
Your status is CRITICAL and out of fuel
[root@INSID-BAUANI~]#echo $WHATSHOULDIDO
Just Close this console and go for lunch
[root@INSID-BAUANI~]#
Above command is just kidding -- originally it is my physical status....
Going Lunch, More information is coming Very Soon.
This is just a initial update of BTTB Internet from client end and one 2 hop away from BTTB Border Router. Waiting for BTTB official Statement for More Information...
Related Posts:
Posts
0 comments:
Post a Comment