Local Latency Problems

[Mr.Jax]

Hi all (first post).

I've been experiencing latency issues for the past couple of weeks.
Basically, in business hours, my latency to my WAN side gateway is 14-17ms. Great.

After hours though....150-350ms all the time. Saturdays and Sundays pretty much all the time. Packet loss included for free too.

Pretty much happens at the only times I can play online games. Saddens me

Ofcourse, calling Telkom support doesn't help at all. They've checked out everything and cannot find anything wrong. They also claim that the exchange is not congested etc...
I've replaced my DSL router, used a different PC....those suckers are not at fault.

So, I've found one or two others reporting the same problem on the forums.

Oh, 4mbit using SAIX.

Do you guys have any advice for me ?
Anyone else experiencing this ?


PS> I dunno if its just me, but I'm sure it started getting worse after the 5GB cap was introduced.

EDIT: This is in the Pierre van Ryneveld, Pretoria area.

 

[ichigo]

dont seem to notice any problems here

i'm using 4 mbit line and telkom 5 gig account here

 

[ben dover]

Hmm i suffer the same issues, and im in the fourways area...
When i play online COD4 it jumps from 50ms-500ms, from time to time.
During the day i get a stable 50ms.
Not sure what telkom would do, but you say you've contacted them...

Sorry i couldn't help, im in the same boat...

 

[Maveric12]

me too...its actually kark frustrating

 

[ben dover]

Check out my Screenie of my issue...
http://mybroadband.co.za/photos/showphoto.php/photo/12542

 

[Adenoid Hynkel]

Pinging telkom.co.za [196.43.22.222] with 32 bytes of data:

Reply from 196.43.22.222: bytes=32 time=227ms TTL=250
Reply from 196.43.22.222: bytes=32 time=238ms TTL=250
Reply from 196.43.22.222: bytes=32 time=248ms TTL=250
Reply from 196.43.22.222: bytes=32 time=257ms TTL=250
Reply from 196.43.22.222: bytes=32 time=267ms TTL=250
Reply from 196.43.22.222: bytes=32 time=191ms TTL=250
Reply from 196.43.22.222: bytes=32 time=201ms TTL=250
Reply from 196.43.22.222: bytes=32 time=267ms TTL=250
Reply from 196.43.22.222: bytes=32 time=241ms TTL=250
Reply from 196.43.22.222: bytes=32 time=193ms TTL=250
Reply from 196.43.22.222: bytes=32 time=204ms TTL=250
Reply from 196.43.22.222: bytes=32 time=213ms TTL=250
Reply from 196.43.22.222: bytes=32 time=223ms TTL=250
Reply from 196.43.22.222: bytes=32 time=177ms TTL=250
Reply from 196.43.22.222: bytes=32 time=188ms TTL=250
Reply from 196.43.22.222: bytes=32 time=199ms TTL=250
Reply from 196.43.22.222: bytes=32 time=208ms TTL=250
Reply from 196.43.22.222: bytes=32 time=217ms TTL=250
Reply from 196.43.22.222: bytes=32 time=227ms TTL=250
Reply from 196.43.22.222: bytes=32 time=237ms TTL=250
Reply from 196.43.22.222: bytes=32 time=247ms TTL=250
Reply from 196.43.22.222: bytes=32 time=258ms TTL=250
Reply from 196.43.22.222: bytes=32 time=213ms TTL=250
Reply from 196.43.22.222: bytes=32 time=224ms TTL=250

F#$ing buuuuuuuuuuuuuuuulsheeeeeit. I'm tired of telkom

 

[fragtion]

set up smokeping or ping plotter and graph the data over a few days, then post that here for others to compare, and use that as proof when telkom denies

 

[Adenoid Hynkel]

Very weird. Seems to be a Router Issue on my side.

Billion 400G (Telkom Router) gives me a high latency, where my 2 year old netgear router gives me stable ms at all times.

Pinging telkom.co.za [196.43.22.222] with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=37ms TTL=250
Reply from 196.43.22.222: bytes=32 time=36ms TTL=250
Reply from 196.43.22.222: bytes=32 time=36ms TTL=250
Reply from 196.43.22.222: bytes=32 time=36ms TTL=250
Reply from 196.43.22.222: bytes=32 time=36ms TTL=250
Reply from 196.43.22.222: bytes=32 time=36ms TTL=250
Reply from 196.43.22.222: bytes=32 time=36ms TTL=250
Reply from 196.43.22.222: bytes=32 time=36ms TTL=250
Reply from 196.43.22.222: bytes=32 time=36ms TTL=250
Reply from 196.43.22.222: bytes=32 time=36ms TTL=250
Reply from 196.43.22.222: bytes=32 time=42ms TTL=250
Reply from 196.43.22.222: bytes=32 time=36ms TTL=250
Reply from 196.43.22.222: bytes=32 time=39ms TTL=250
Reply from 196.43.22.222: bytes=32 time=36ms TTL=250
Reply from 196.43.22.222: bytes=32 time=36ms TTL=250
Reply from 196.43.22.222: bytes=32 time=37ms TTL=250
Reply from 196.43.22.222: bytes=32 time=36ms TTL=250
Reply from 196.43.22.222: bytes=32 time=36ms TTL=250
Reply from 196.43.22.222: bytes=32 time=37ms TTL=250
Reply from 196.43.22.222: bytes=32 time=37ms TTL=250
Reply from 196.43.22.222: bytes=32 time=36ms TTL=250
Reply from 196.43.22.222: bytes=32 time=36ms TTL=250
Reply from 196.43.22.222: bytes=32 time=36ms TTL=250
Reply from 196.43.22.222: bytes=32 time=39ms TTL=250
Reply from 196.43.22.222: bytes=32 time=36ms TTL=250
Reply from 196.43.22.222: bytes=32 time=36ms TTL=250
Reply from 196.43.22.222: bytes=32 time=36ms TTL=250
Reply from 196.43.22.222: bytes=32 time=36ms TTL=250
Reply from 196.43.22.222: bytes=32 time=38ms TTL=250
Reply from 196.43.22.222: bytes=32 time=39ms TTL=250

As soon as I plug the Billion in again, high ms figures.

Edit, look at the figures if I ping my router.

Pinging 10.11.3.2 with 32 bytes of data:
Reply from 10.11.3.2: bytes=32 time=59ms TTL=128
Reply from 10.11.3.2: bytes=32 time=67ms TTL=128
Reply from 10.11.3.2: bytes=32 time=79ms TTL=128
Reply from 10.11.3.2: bytes=32 time=76ms TTL=128
Reply from 10.11.3.2: bytes=32 time=89ms TTL=128
Reply from 10.11.3.2: bytes=32 time=101ms TTL=128
Reply from 10.11.3.2: bytes=32 time=58ms TTL=128
Reply from 10.11.3.2: bytes=32 time=70ms TTL=128
Reply from 10.11.3.2: bytes=32 time=83ms TTL=128
Reply from 10.11.3.2: bytes=32 time=95ms TTL=128
Reply from 10.11.3.2: bytes=32 time=92ms TTL=128
Reply from 10.11.3.2: bytes=32 time=105ms TTL=128
Reply from 10.11.3.2: bytes=32 time=61ms TTL=128
Reply from 10.11.3.2: bytes=32 time=73ms TTL=128
Reply from 10.11.3.2: bytes=32 time=86ms TTL=128
Reply from 10.11.3.2: bytes=32 time=99ms TTL=128
Reply from 10.11.3.2: bytes=32 time=111ms TTL=128
Reply from 10.11.3.2: bytes=32 time=68ms TTL=128
Reply from 10.11.3.2: bytes=32 time=81ms TTL=128
Reply from 10.11.3.2: bytes=32 time=95ms TTL=128
Reply from 10.11.3.2: bytes=32 time=70ms TTL=128
Reply from 10.11.3.2: bytes=32 time=82ms TTL=128

 

[Mr.Jax]

Yup, thats a router problem right there...
I only wish it was also my problem....

Default gateway ping (2009-10-05 19:00:00):

Reply from 41.240.128.1: bytes=32 time=183ms TTL=254
Reply from 41.240.128.1: bytes=32 time=109ms TTL=254
Reply from 41.240.128.1: bytes=32 time=182ms TTL=254
Reply from 41.240.128.1: bytes=32 time=176ms TTL=254
Reply from 41.240.128.1: bytes=32 time=259ms TTL=254
Reply from 41.240.128.1: bytes=32 time=190ms TTL=254
Reply from 41.240.128.1: bytes=32 time=255ms TTL=254
Reply from 41.240.128.1: bytes=32 time=138ms TTL=254
Reply from 41.240.128.1: bytes=32 time=128ms TTL=254
Reply from 41.240.128.1: bytes=32 time=155ms TTL=254
Reply from 41.240.128.1: bytes=32 time=133ms TTL=254
Reply from 41.240.128.1: bytes=32 time=172ms TTL=254
Reply from 41.240.128.1: bytes=32 time=198ms TTL=254
Reply from 41.240.128.1: bytes=32 time=177ms TTL=254
Reply from 41.240.128.1: bytes=32 time=115ms TTL=254

Router Ping:
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64

 

[Mr.Jax]

^bump^.

This crap is still happening to me. I'm close to biting off my bloody toes from frustration.
When this happens, I can sometimes not even manage a 512kbps download rate on a 4 MEG LINE! (www.speedtest.net)

No malware
No spyware
No downloads
No viruses
No hacked wifi (disabled, using LAN cable)
New Router
Different ISP's tried
New OS installed
Still big ping.

sigh....

TELKOM: upgrade your infrastructure in Pierre van Ryneveld...the quality of service is pathetic!

 

[wHiTe*LiGhTnInG]

have you tried another ISP account?...try an IS account and check to see if they give the same pings.

Also try to check all your cables around the house for your telkom line, check your power cables, check your filter on your phone.just try to check everything up to the point where your line connects to the road box. If you have to do abit of work by yourself, then do it rather than wait for the techs who take 3 weeks

 

[ponder]

have you tried another ISP account?...try an IS account and check to see if they give the same pings.

+1 Just get a 1GB Axxess prepaid voucher from Engen.

 

[Mr.Jax]

have you tried another ISP account?...try an IS account and check to see if they give the same pings.

Also try to check all your cables around the house for your telkom line, check your power cables, check your filter on your phone.just try to check everything up to the point where your line connects to the road box. If you have to do abit of work by yourself, then do it rather than wait for the techs who take 3 weeks

Great tips thanks. Will check the outside wiring.

Also tried a prepaid IS account...same results :/

 

[AgentSmithZA]

I've had a similar problem.

Rather ping www.saix.net - Telkom.co.za seems quite unstable for proper comparison.
Create a log file to show the technician.
"ping www.saix.net -t >> C:\pinglog.txt" let it run for about an hour and CTRL + C to end.


My problem was when accessing local items, my ping would sky rocket and then normalize. When pinging www.saix.net I got anything from 67ms to 2000ms.
I phoned telkom logged the fault, and phoned 4 times a day. When the telkom guy came, I explained my problem, showed him the ping test and said fix

He then went to the exchange, switched my dslam port(or something to that effect), called me up and i tested. Problem was still there.

He then did another swap, which took much longer and my phone was completely dead this time, then called. I did the tests. Problem solved.

I now get a stable 34ms from www.saix.net.

Be persistent and polite.

Also:
I logged my fault on 10215
Followed up 4 times a day on 0800 375 375 (They increased priority - apparently.)

 

[Mr.Jax]

Excellent, thanks.
I usually ping the default gateway, seeing that its the first hop in my connection.

I have logged the fault with them again yesterday, will see what transpires.

But I noticed something weird.

My connection's ping when tis good, would be a cool 15ms. Since about 3 days ago, its now at a ok'ish 39ms with zero jitter. It now never ever goes lower than that.

I wonder what they did and changed this time ?

Oh well, if it would just stay there I'd be a happy chappy.

I've had a similar problem.

Rather ping www.saix.net - Telkom.co.za seems quite unstable for proper comparison.
Create a log file to show the technician.
"ping www.saix.net -t >> C:\pinglog.txt" let it run for about an hour and CTRL + C to end.


My problem was when accessing local items, my ping would sky rocket and then normalize. When pinging www.saix.net I got anything from 67ms to 2000ms.
I phoned telkom logged the fault, and phoned 4 times a day. When the telkom guy came, I explained my problem, showed him the ping test and said fix

He then went to the exchange, switched my dslam port(or something to that effect), called me up and i tested. Problem was still there.

He then did another swap, which took much longer and my phone was completely dead this time, then called. I did the tests. Problem solved.

I now get a stable 34ms from www.saix.net.

Be persistent and polite.

Also:
I logged my fault on 10215
Followed up 4 times a day on 0800 375 375 (They increased priority - apparently.)

 

[MidnightWizard]

Grapevine

Excellent, thanks.

But I noticed something weird.

My connection's ping when tis good, would be a cool 15ms. Since about 3 days ago, its now at a ok'ish 39ms with zero jitter. It now never ever goes lower than that.

I wonder what they did and changed this time ?

Here be little birdies -- with BIG ears

MyBB is now also a support forum for TELKOM :erm:


MW

 

[Mr.Jax]

Got a call from a technician :wtf: Almost fell of my chair!

Dude's gonna put my line on a different DSLAM @ the exchange.

PROGRESS!!!!

Maybe, just maybe....there's hope....after 6 months !

Oh and this time I logged the fault online and not via the call centre.

 

[AgentSmithZA]

Good to hear theres progress

 

[Mr.Jax]

Well, Telkom is really impressing me this time around.

Friday, techie called.
Saturday techie called.
Just now a techie called again.

My problem still persists though, but fortunately they're really giving it attention.

Cautiously optimistic that this problem will get resolved