Broadband in Lebanon - Latest Updates

Ok it's now 3 p.m and the latency is now more weird because rather then becoming higher, it's now lower here is the test:

Mine still didnt change and it is 5:40 pm

mine has improved!!!! I'm with wise, before mine was ~500ms

This test is different because the server is now the same as the one ogero guys are testing.

wow can you ping france please?
let's say tf1.fr
Today my private ISP guy came for the monthly $$ (you know he gets internet from main ISPs + sat internet and shares it through his intranet via natting) so I asked him about the IMEWE cable. He said that in 2 months there should be improvements and that he will be able to allocate 512K for 20$/month (compared to 128K for 35$/mo now). Too good to be true?
Anyone knows if IMEWE has even reached Tripoli yet?
Cheers

Fernand wrotewow can you ping france please?
let's say tf1.fr
Today my private ISP guy came for the monthly $$ (you know he gets internet from main ISPs + sat internet and shares it through his intranet via natting) so I asked him about the IMEWE cable. He said that in 2 months there should be improvements and that he will be able to allocate 512K for 20$/month (compared to 128K for 35$/mo now). Too good to be true?
Anyone knows if IMEWE has even reached Tripoli yet?
Cheers

Here is the test.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\riad>ping tf1.fr

Pinging tf1.fr [193.169.66.26] with 32 bytes of data:

Reply from 193.169.66.26: bytes=32 time=120ms TTL=243
Reply from 193.169.66.26: bytes=32 time=119ms TTL=243
Reply from 193.169.66.26: bytes=32 time=121ms TTL=243
Reply from 193.169.66.26: bytes=32 time=120ms TTL=243

Ping statistics for 193.169.66.26:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 119ms, Maximum = 121ms, Average = 120ms


I think that the IMEWE will reach lebanon in june or july 30, but what I read was that it won't be operational until next year, hopefully.

i think im gonna become a ping host :p
its almost 1 month my application was sent to sodetel still waiting :( gaming package is tasty muhahaha

gamer4life dare I think that you are already on IMEWE? (lucky beta tester in Tripoli?)
I also think that the minister meant by "the major internet update will take place by early 2011" that official upgrade of packages will take place by then. We should therefore start getting better latency to Europe progressively all over the territory starting from Tripoli down to the South. Then, when most of Lebanon is interconnected with fiber, they will unlock IMEWE potential and suck its bandwidth.
cheesy theory?:P
any alternative explanation?
btw how is the latency in Tripoli for Ogero/Sodetel/Terranet subscribers?
Thank you

kareem you're an IDM subscriber? no improvements at all till now since other people started to notice lower latency?
120ms to France
150ms to Germany
170-180ms to Jerusalem
mmmmm IMEWE scheme? :P

yup IDM but to me it is better it used to be like 550ms by now and it is :
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Karim Nasser>Ping tf1.fr -t

Pinging tf1.fr [193.169.66.26] with 32 bytes of data:

Reply from 193.169.66.26: bytes=32 time=397ms TTL=236
Reply from 193.169.66.26: bytes=32 time=405ms TTL=236
Reply from 193.169.66.26: bytes=32 time=390ms TTL=236
Reply from 193.169.66.26: bytes=32 time=405ms TTL=236
Reply from 193.169.66.26: bytes=32 time=423ms TTL=236
Reply from 193.169.66.26: bytes=32 time=439ms TTL=236
Reply from 193.169.66.26: bytes=32 time=401ms TTL=236
Reply from 193.169.66.26: bytes=32 time=379ms TTL=236
Reply from 193.169.66.26: bytes=32 time=398ms TTL=236
Reply from 193.169.66.26: bytes=32 time=425ms TTL=236
Reply from 193.169.66.26: bytes=32 time=445ms TTL=236
Reply from 193.169.66.26: bytes=32 time=396ms TTL=236
Reply from 193.169.66.26: bytes=32 time=385ms TTL=236
Reply from 193.169.66.26: bytes=32 time=397ms TTL=236
Reply from 193.169.66.26: bytes=32 time=374ms TTL=236
Reply from 193.169.66.26: bytes=32 time=394ms TTL=236
Reply from 193.169.66.26: bytes=32 time=418ms TTL=236
Reply from 193.169.66.26: bytes=32 time=376ms TTL=236
Reply from 193.169.66.26: bytes=32 time=375ms TTL=236
Reply from 193.169.66.26: bytes=32 time=382ms TTL=236

even worse
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\???>ping impelcrm.in -t

Pinging impelcrm.in [202.71.129.176] with 32 bytes of data:
Reply from 202.71.129.176: bytes=32 time=718ms TTL=42
Reply from 202.71.129.176: bytes=32 time=735ms TTL=42
Reply from 202.71.129.176: bytes=32 time=737ms TTL=42
Reply from 202.71.129.176: bytes=32 time=726ms TTL=42
Reply from 202.71.129.176: bytes=32 time=751ms TTL=42
Reply from 202.71.129.176: bytes=32 time=1345ms TTL=42
Reply from 202.71.129.176: bytes=32 time=753ms TTL=42
Reply from 202.71.129.176: bytes=32 time=806ms TTL=42
Reply from 202.71.129.176: bytes=32 time=856ms TTL=42
Reply from 202.71.129.176: bytes=32 time=787ms TTL=42
Reply from 202.71.129.176: bytes=32 time=758ms TTL=42
Reply from 202.71.129.176: bytes=32 time=776ms TTL=42

now let's see what gamer4life gets from India.

does anyone knows what happened to alfa's HSPA+? it was announced over a year ago
thank you in advance

getting International bandwidth is a MUST before being able to think about HSDPA. Plus, I think they will go for 3G (UMTS) first before HSDPA since I doubt they will be even able to give away 7-8Mbits/s via landlines. ;D
Till then, dream on.

As for the ping tests:
------------------------
pinging India from The States gives:

PING impelcrm.in (202.71.129.176) 56(84) bytes of data.

64 bytes from corp3.net4india.com (202.71.129.176): icmp_seq=1 ttl=51 time=358 ms

64 bytes from corp3.net4india.com (202.71.129.176): icmp_seq=2 ttl=51 time=357 ms

64 bytes from corp3.net4india.com (202.71.129.176): icmp_seq=3 ttl=51 time=358 ms

64 bytes from corp3.net4india.com (202.71.129.176): icmp_seq=4 ttl=51 time=357 ms

64 bytes from corp3.net4india.com (202.71.129.176): icmp_seq=5 ttl=51 time=358 ms

64 bytes from corp3.net4india.com (202.71.129.176): icmp_seq=6 ttl=51 time=357 ms

64 bytes from corp3.net4india.com (202.71.129.176): icmp_seq=7 ttl=51 time=358 ms

64 bytes from corp3.net4india.com (202.71.129.176): icmp_seq=8 ttl=51 time=358 ms



That's a high speed VPS with a 100mbps link.



whereas pinging tf1.fr from the same location gives:

PING tf1.fr (193.169.66.26) 56(84) bytes of data.

64 bytes from 193.169.66.26: icmp_seq=1 ttl=246 time=81.7 ms

64 bytes from 193.169.66.26: icmp_seq=2 ttl=246 time=81.9 ms

64 bytes from 193.169.66.26: icmp_seq=3 ttl=246 time=81.3 ms

64 bytes from 193.169.66.26: icmp_seq=4 ttl=246 time=81.9 ms

64 bytes from 193.169.66.26: icmp_seq=5 ttl=246 time=81.3 ms

64 bytes from 193.169.66.26: icmp_seq=6 ttl=246 time=81.8 ms

64 bytes from 193.169.66.26: icmp_seq=7 ttl=246 time=81.3 ms

64 bytes from 193.169.66.26: icmp_seq=8 ttl=246 time=81.8 ms

64 bytes from 193.169.66.26: icmp_seq=9 ttl=246 time=81.3 ms

64 bytes from 193.169.66.26: icmp_seq=10 ttl=246 time=81.8 ms

64 bytes from 193.169.66.26: icmp_seq=11 ttl=246 time=81.3 ms



India's high latency is due to the fact that requests have to cross half of the globe to reach India (trans-Pacific-Australia for instance you can get 350MS IF YOU ARE LUCKY), though I am not sure which international cable our pings are taking when India is concerned.

My point is if Tripoli is linked to IMEWE now, gamer4life should theoretically get a low ping to India, perhaps even far less than the 350ms (high speed american VPS to India). Should test Italia too since it's closer than France on the IMEWE route.



So please gamer4life 3am men 3azzbak, kindly ping India: impelcrm.in

and Italia: digilander.libero.it

Thanks

Cheers