Terrible Latency and speed

[Strife2k]

Hey everyone

Basically the story is that ever since the seacom outage and for over a week now I have been having terrible latencies and speed on my line. I currently have a 4mb uncapped shaped account with Mweb although the line is synced at 2mb's for stability issues. I live in the Roodeport, Joburg area and last tuesday we did have a technician from telkom come to our area in regards to our fault, but the problem still persists. Anyway here is some evidence to show how the line is performing at present.

Im not sure if this is correct but here is a tracer to telkom - www.telkom.co.za

Tracing route to nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 921 ms 995 ms 1022 ms 41-132-18-1.dsl.mweb.co.za [41.132.18.1]
3 870 ms 713 ms 599 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.16
9.170]
4 518 ms 573 ms 704 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 727 ms 641 ms 511 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16
9.241]
6 1241 ms 1426 ms 1018 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.
249]
7 1000 ms 1307 ms 1560 ms 196.43.11.166
8 2057 ms 1987 ms 1673 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
9 694 ms 458 ms 641 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.30]
10 940 ms 1205 ms 1261 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.

The latencies on the local steam servers average around 400 - 1200 ms all day making online gaming unplayable. Another thing is that when I do get ingame I experience alot of ping spikes for as long as it stays playable.

Also a speedtest on the line:

http://www.speedtest.net/result/899594672.png


Any help that someone could suggest would be very appreciated.

 

[ichigo]

looks like a problem on exchange/dslam or congestion

2 921 ms 995 ms 1022 ms 41-132-18-1.dsl.mweb.co.za [41.132.18.1] (is exchange/dslam)

have you tried another internet account?

 

[Strife2k]

I was on afrihost 4mb uncapped prior to this but the problem was evident on that account too. Not to sound naive but what is the exchange/dslam? and how would i know if it were congested?

 

[GingerBeer]

I was on afrihost 4mb uncapped prior to this but the problem was evident on that account too. Not to sound naive but what is the exchange/dslam? and how would i know if it were congested?

Can it get congested overnight?

 

[ambo]

Not to sound naive but what is the exchange/dslam? and how would i know if it were congested?

It refers to the telephone exchange that you connect to. The DSLAM is the equipment that handles your ADSL service.

There is no way for you to check if the DSLAM is congested but a latency like that is an indication of a problem somewhere on the Telkom ADSL network. Have you contacted your ISP about this? The can often follow up with telkom more easily than you could.

 

[Strife2k]

Ok thanks for the advice, I'll try give mweb a call. On another note can anyone tell me if these attenuation rates and noise margins are good on the line, hopefully this is correct. Im not really sure if this has anything to do with the poor ping/speeds.

--- System Information ---
Vendor: Linksys
ModelName: WAG54G2
Firmware Version: 1.00.10 , 2008-08-01T20:20:49
Boot Version: 1.03
Hardware Version: 0.01

--- DSL Information ---
DSL Driver Version: E.25.41.39
DSL VPI/VCI: 8/35
DSL Status: Showtime
DSL Mode: G.Dmt
DSL Channel: 64
DSL Upstream Rate: 512000
DSL Downstream Rate: 2048000

Down up
DSL Noise Margin: 28.5 dB 53.0 dB
DSL Attenuation: 12 dB 12.0 dB
DSL Transmit Power: 17.0 dBm 11.7 dBm

 

[ichigo]

DSL Noise Margin: 28.5 dB 53.0 dB
DSL Attenuation: 12 dB 12.0 dB
DSL Transmit Power: 17.0 dBm 11.7 dBm

that can easily give you 4 meg + speeds

 

[GingerBeer]

Is the attenuation changing a lot?

 

[Strife2k]

This is the first time i have checked my attenuation so i wouldn't know if was or has been changing. However like Merenwenrago says i should be getting good speeds. I honestly don't know what could be affecting my latency the way it is now, hopefully when the second technician comes through for a look he can solve the problem.

Could there be anything else that I myself can try, to identify or fix the latency problem?