IS Uncapped - bad packet loss

Leno

Expert Member
Joined
May 15, 2005
Messages
2,396
Reaction score
767
Location
UK & PE
Is anyone experiencing bad packet loss on the first hop from IS uncapped business adsl? we have been getting 48% loss for the last 48 hours...

a ping done recently of 150 packets

--- 196.xxx.xxxx.xxx ping statistics ---
150 packets transmitted, 97 packets received, 35% packet loss
round-trip min/avg/max/stddev = 164.290/304.644/1036.629/156.430 ms

we are in port elizabeth, so it might be telkom but have another line on the same exchange which is fine... erk!
 
Ive been having quite a bit of packet loss since saturday. Im using openweb. Not sure what the hell is going on. Thought it was my modem's fault. I also tried SAIX...same thing. Im fed-up allready!
 
i also had this wierd problem yesterday with a normal saix adsl account... it would disconnect every 5/10 mins... the adsl modem said the atm interface went down. that line seems fine today *shrug*
 
I think its pathetic that IS has not told anyone about the problems they are having ? surley they should send out a notice ?
 
The IS ADSL service has been shocking for the last three months.

High latency, packet loss and crap local/international bandwidth.

C:\>ping www.google.com

Pinging www.l.google.com [64.233.161.99] with 32 bytes of data:

Request timed out.
Reply from 64.233.161.99: bytes=32 time=1406ms TTL=227
Reply from 64.233.161.99: bytes=32 time=898ms TTL=227
Request timed out.

Ping statistics for 64.233.161.99:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 898ms, Maximum = 1406ms, Average = 576ms
 
the technician phoned me back, and said there were 14000 crc errors in a few hours... just as i was about to call our friends at 0800 dsl dsl hey presto it came right... yay

It came right a bit close to 17:00 for me... how do we know how much telkom is overselling the exchanges (contention ratio) i doubt they have a multiple of 512k on their inter exchange links for every adsl subscriber *shrug*

Just out of interest, does anyone know if port elizabeths adsl authenticates in jhb or ctn?

chow
 
JHB and CPT are the only ones,

As far as IS bandwidth into the Exchanges, they are running at a ratio of 1:8.

However my International is so bad.
 
I am getting quite good pings on my IS uncapped account .Thought they route all int via sat ?Seems not to be the case !

Pinging www.l.google.com [66.249.85.104] with 32 bytes of data:

Reply from 66.249.85.104: bytes=32 time=294ms TTL=241
Reply from 66.249.85.104: bytes=32 time=292ms TTL=241
Reply from 66.249.85.104: bytes=32 time=291ms TTL=241
Reply from 66.249.85.104: bytes=32 time=288ms TTL=241

Ping statistics for 66.249.85.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 288ms, Maximum = 294ms, Average = 291ms
 
http://196.211.2.162/cgi-bin/ping.cgi?t=66.249.85.104
PING 66.249.85.104 (66.249.85.104) 56(84) bytes of data.
64 bytes from 66.249.85.104: icmp_seq=0 ttl=237 time=706 ms
64 bytes from 66.249.85.104: icmp_seq=1 ttl=237 time=709 ms
64 bytes from 66.249.85.104: icmp_seq=2 ttl=237 time=708 ms

My uncapped,unshaped Business ADSL reflects the above
your routing seems like it was routing via SAT3 thanks Clipse
See below for SAIX ping times
Pinging www.l.google.com [72.14.207.99] with 32 bytes of data:
Reply from 72.14.207.99: bytes=32 time=300ms TTL=238
Reply from 72.14.207.99: bytes=32 time=299ms TTL=237
Reply from 72.14.207.99: bytes=32 time=299ms TTL=238
Reply from 72.14.207.99: bytes=32 time=300ms TTL=238
 
Last edited:
Jgoosen1 is actually on one of our uncapped packages, wonder what IS decided to do with international, seems routed via sat3 :-)
 
jgoosen1, are your speeds good? (local and international)
 
thewanted_ said:
jgoosen1, are your speeds good? (local and international)[/QUOT] Well it was slow over the weekend the international side.Local getting around 60KB/s better than i ever got from saix and int is between 36 and 56kb max
 
Thats cool :) Thanks for the response.

I'm toying with the idea of 192k uncapped if my ADSL is installed. My apologies for threadjacking.
 
Quite a simple answer to the low latency... IS routs their traffic over satelite but if there's a problem, they simply switch it to SAT3. Thus, they had a probe with satelite and swicthed to SAT 3. Try ping again. Then try tomorrow. Once it goes back to satelite, you'll see...
 
Top
Sign up to the MyBroadband newsletter
X