ADSL Slower than EVER?!?!?

9:43am

Pinging www.saix.net [196.25.1.200] with 32 bytes of data:

Reply from 196.25.1.200: bytes=32 time=11ms TTL=251
Reply from 196.25.1.200: bytes=32 time=10ms TTL=251
Reply from 196.25.1.200: bytes=32 time=11ms TTL=251
Reply from 196.25.1.200: bytes=32 time=11ms TTL=251

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

It's like they're flicking a switch on and off..
 
I live in the Kenilworth region and i pretty much experience the same problem.
The latency is now better to local servers but still unacceptably low in order for me to start enjoying my local online gaming.
I've been totally down for 3 days now and can only download.

Reading the forums i get frustrated to see that we are being pulled over a barrel in terms of our knowledge of the problem!!!

I hope that this problem gets resolved soon!!!! :mad:
 
Bad breath’s better than no breath at all…

C:\Documents and Settings\kungfoowiz___2>ping www.google.com

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

Reply from 209.85.135.99: bytes=32 time=1922ms TTL=241
Request timed out.
Reply from 209.85.135.99: bytes=32 time=1968ms TTL=241
Reply from 209.85.135.99: bytes=32 time=1902ms TTL=241

Ping statistics for 209.85.135.99:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 1902ms, Maximum = 1968ms, Average = 1930ms

C:\Documents and Settings\kungfoowiz___2>ping www.google.co.za

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

Request timed out.
Reply from 72.14.253.103: bytes=32 time=1955ms TTL=239
Reply from 72.14.253.103: bytes=32 time=1926ms TTL=239
Reply from 72.14.253.103: bytes=32 time=2006ms TTL=239

Ping statistics for 72.14.253.103:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 1926ms, Maximum = 2006ms, Average = 1962ms
 
Mine's on a SAIX account.

Been like this since Sunday. After hours = goes to hell. Sometime in the morning = perfect.

This reminds me of Eskom's load shedding.. one area goes dark, the other comes back up.
 
Last edited:
12:00PM

Notice improvement in local speed and stability.
Still not convinced that problem is resolved

Pinging saix.net [196.25.1.200] with 32 bytes of data

Reply from 196.25.1.200: bytes=32 time=59ms TTL=241
Reply from 196.25.1.200: bytes=32 time=61ms TTL=241
Reply from 196.25.1.200: bytes=32 time=60ms TTL=241
Reply from 196.25.1.200: bytes=32 time=59ms TTL=241
Reply from 196.25.1.200: bytes=32 time=60ms TTL=241
Reply from 196.25.1.200: bytes=32 time=63ms TTL=241
 
I spoke to a Telkom support dude this morning, who claimed that there was "a problem" and it had been "resolved" and all should be well. This is exactly what another agent told me on Tuesday this week though, and I let him know in no uncertain terms that I still had the fault number, and his name, and I refuse to let him close the ticket until tonight when I can see whether or not everything goes to hell in a hand basket again.

Of constant amusement is the fact that none of the agents know anything about these apparent "problems" that are constantly "fixed". If everything is still fine tonight, and for the whole weekend without problems, I'll be convinced.
 
LOL!! We think alike.

Same thing. I went home for lunch, and tested pings and tracerts. All looked well. Just then, I got a call from a telskum techie following up on my fault report.

I told him all was well for now, but I had no faith in their network, and they should call me this evening (or tomorrow) again to make sure it was still alright, and not to close the ticket until I had 24 hrs of good connection behind me.
 
Same boat as you guys - Rondebosch, Cape Town.

Mornings are fine - WoW reflects a latency of around 300 - 400ms, after work it sits at 1,200ms - 2000ms. Since sunday... I have raids to attend, driving me nuts!!! Tried to get a telscum operator for 2 hours last night but all i got was - all our operators are currently busy, please be patient(sod off!!!), your call will be answered as soon as an operator becomes available.

WTF is the point of charging more for unshaped BW when shaped is fkin 3 times faster for half the month!!

/cry
 
Well, 16:50 and all is well, lets see if Telskum **** us over tonight again.
 
Just spoke to a techie - apparently the problem was resolved last night, apparently there was a problem with an ESR in the Cape Town area. Guess we'll see this evening :confused:
 
I'm in Rondebosch too and it was STILL screwed this morning at 8:30am. It only got better after 9:30 - so whatever they "fixed" last night, it wasn't this. Can't wait for after hours today and an ENTIRE WEEKEND of my line being useless.
 
I still have 60-100ms ping. Games are playable now, but it's not even close to the 10-11ms ping I'm used to. +50 on the base and a fluctuation of 40ms is a bad tradeoff for 1 week downtime :<
 
My pings also went up from 2 last night.. pinging in the high 50-70 usually pinged in the 35-45 range... glad to see I'm not the only with a complaint !
 
Last edited:
Which Exchanges

I am quite convinced there have been outages and or replacement / defective equipment at the Clareinch exchange.

Firstly my Cybersmart account bugged out on the 1st and i'm not sure why on my home line, then both lines were not working at the office which are via Imaginet - both of which also use the ADSL port number on Telkom which needs a call to Imaginet if it does not work to change them - and they both had changed.

All local for me is bad (of course int as well), regardless of service provider - I think at least Clareinch exchange has problems and they dont know where they are and are trying to troubleshoot it. This could also imply that exchanges linking on to it could also have problems - e.g. Wynberg, Rondebosh etc.

NB: All my connections at home & at work are on the Clareinch exchange.
 
How is it possible that my IS and SAIX pings are both equally poor:

SAIX:

Pinging saix.net [196.25.1.200] with 32 bytes of data:

Reply from 196.25.1.200: bytes=32 time=92ms TTL=251
Reply from 196.25.1.200: bytes=32 time=93ms TTL=251
Reply from 196.25.1.200: bytes=32 time=93ms TTL=251
Reply from 196.25.1.200: bytes=32 time=90ms TTL=251

Ping statistics for 196.25.1.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 90ms, Maximum = 93ms, Average = 92ms


IS:
Pinging saix.net [196.25.1.200] with 32 bytes of data:

Reply from 196.25.1.200: bytes=32 time=94ms TTL=242
Reply from 196.25.1.200: bytes=32 time=94ms TTL=242
Reply from 196.25.1.200: bytes=32 time=94ms TTL=242
Reply from 196.25.1.200: bytes=32 time=153ms TTL=242

Ping statistics for 196.25.1.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 94ms, Maximum = 153ms, Average = 108ms

One other thing that I noticed on saix noticeboard is that they are going do planned maintenance on the New Doornfontein Core router on sunday..and my IS connection is also routed via that.. so maybe that would then explain the horrible ping times ? Might it improve on sunday after they have completed the maintenance ??

My SAIX account is with Cybersmart, and I have also read that there were a number of problems in the CT area, but I think the new doornfontein router might be the key to my problems and some other folks on myadsl as well...

PS: My ping problems only started yesterday evening however....
 
It's back, which makes this at least day 12 since this problem started:

brendon$ ping www.telkom.co.za
PING ctb-cache3-vif1.saix.net (198.54.202.4): 56 data bytes
64 bytes from 198.54.202.4: icmp_seq=0 ttl=252 time=1629.749 ms
64 bytes from 198.54.202.4: icmp_seq=1 ttl=252 time=1669.837 ms
64 bytes from 198.54.202.4: icmp_seq=2 ttl=252 time=1508.932 ms
64 bytes from 198.54.202.4: icmp_seq=3 ttl=252 time=1519.162 ms
64 bytes from 198.54.202.4: icmp_seq=4 ttl=252 time=1539.061 ms
64 bytes from 198.54.202.4: icmp_seq=5 ttl=252 time=1575.223 ms
64 bytes from 198.54.202.4: icmp_seq=6 ttl=252 time=1638.617 ms
^C
--- ctb-cache3-vif1.saix.net ping statistics ---
9 packets transmitted, 7 packets received, 22% packet loss
round-trip min/avg/max/stddev = 1508.932/1582.940/1669.837/59.006 ms
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X