ADSL BRILLIANT SNR, TERRIBLE INTERNET EXPERIENCE

J

jarrydred

Well-Known Member
Joined
Jun 14, 2010
Messages
138
Reaction score
0
Hello

My ADSL line is a force to be reckoned with, I have a 384 kbps ADSL line (with Telkom) and also uncapped with Mweb, the problem comes in that my browsing experience is terrible, pages time out, Pings get request times out, gaming experience is terrible (even for a 384). My questions are what could be causing it and what can I do about, I've posted details below:

Downstream Upstream
SNR Margin 34.0 31.0 db
Line Attenuation 19.5 7.0 db
Data Rate 384 128 kbps

Number to help for exchange:
011 867

Please any suggestions
 
Perform a trace route to like www.google.co.za and post your results here.

It is highly likely that the Telkom Exchange that you're going through is congested. You'll notice a high (50ms or higher) 2nd-hop in the trace route if this is the case.
If you're using an Mweb business account, then the 2nd-hop's ping may be high due to other reasons.
 
Hello I performed a trace route and this the response:

Tracing route to google.co.za [74.125.233.24]
over a maximum of 30 hops:

1 <1 ms * <1 ms BMAECOMPSRV [192.168.*.*]
2 * * * Request timed out.
3 496 ms 502 ms * 197-80-4-94.jhb.mweb.co.za [197.80.4.94]
4 373 ms 337 ms 323 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 398 ms 264 ms 334 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za [196.22.169.
242]
6 * 437 ms 347 ms tengig0-1-0-0.cpt-up-1.mweb.co.za [197.84.4.34]

7 482 ms 424 ms 244 ms 197-80-4-137.jhb.mweb.co.za [197.80.4.137]
8 451 ms 230 ms 291 ms gi0-2-cpt-cinx.mweb.co.za [196.28.178.133]
9 424 ms 389 ms 231 ms google.cinx.net.za [196.223.22.41]
10 356 ms 337 ms 271 ms 64.233.174.105
11 218 ms 363 ms 336 ms cpt01s01-in-f24.1e100.net [74.125.233.24]

Not on mweb business Account
 
jarrydred said:
Hello I performed a trace route and this the response:

Tracing route to google.co.za [74.125.233.24]
over a maximum of 30 hops:

1 <1 ms * <1 ms BMAECOMPSRV [192.168.*.*]
2 * * * Request timed out.
3 496 ms 502 ms * 197-80-4-94.jhb.mweb.co.za [197.80.4.94]
4 373 ms 337 ms 323 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 398 ms 264 ms 334 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za [196.22.169.
242]
6 * 437 ms 347 ms tengig0-1-0-0.cpt-up-1.mweb.co.za [197.84.4.34]

7 482 ms 424 ms 244 ms 197-80-4-137.jhb.mweb.co.za [197.80.4.137]
8 451 ms 230 ms 291 ms gi0-2-cpt-cinx.mweb.co.za [196.28.178.133]
9 424 ms 389 ms 231 ms google.cinx.net.za [196.223.22.41]
10 356 ms 337 ms 271 ms 64.233.174.105
11 218 ms 363 ms 336 ms cpt01s01-in-f24.1e100.net [74.125.233.24]

Not on mweb business Account
Click to expand...

Yep your line link is difinitely congested with 496ms+ in 3rd hop, it should be under 20 prefably 8-10 ms
 
Yes , because now the tracert shows this:

Tracing route to google.co.za [74.125.233.23]
over a maximum of 30 hops:

1 <1 ms * <1 ms BMAECOMPSRV [192.168.*.*]
2 * * * Request timed out.
3 141 ms 113 ms 54 ms tengig-0-0-0-100.vic-ipc-2.mweb.co.za [196.22.16
3.206]
4 63 ms 84 ms 150 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 107 ms 161 ms 152 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za [196.22.169.
242]
6 74 ms 129 ms 132 ms tengig0-1-0-0.cpt-up-1.mweb.co.za [197.84.4.34]

7 98 ms 97 ms 141 ms 197-80-4-137.jhb.mweb.co.za [197.80.4.137]
8 75 ms 89 ms 92 ms gi0-2-cpt-cinx.mweb.co.za [196.28.178.133]
9 103 ms 89 ms 53 ms google.cinx.net.za [196.223.22.41]
10 69 ms 69 ms 134 ms 64.233.174.105
11 129 ms 155 ms 108 ms cpt01s01-in-f23.1e100.net [74.125.233.23]

Trace complete.
 
jarrydred said:
Yes , because now the tracert shows this:

Tracing route to google.co.za [74.125.233.23]
over a maximum of 30 hops:

1 <1 ms * <1 ms BMAECOMPSRV [192.168.*.*]
2 * * * Request timed out.
3 141 ms 113 ms 54 ms tengig-0-0-0-100.vic-ipc-2.mweb.co.za [196.22.16
3.206]
4 63 ms 84 ms 150 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 107 ms 161 ms 152 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za [196.22.169.
242]
6 74 ms 129 ms 132 ms tengig0-1-0-0.cpt-up-1.mweb.co.za [197.84.4.34]

7 98 ms 97 ms 141 ms 197-80-4-137.jhb.mweb.co.za [197.80.4.137]
8 75 ms 89 ms 92 ms gi0-2-cpt-cinx.mweb.co.za [196.28.178.133]
9 103 ms 89 ms 53 ms google.cinx.net.za [196.223.22.41]
10 69 ms 69 ms 134 ms 64.233.174.105
11 129 ms 155 ms 108 ms cpt01s01-in-f23.1e100.net [74.125.233.23]

Trace complete.
Click to expand...

Depends on when people are using the internet, so evening/weekends may be worse, if you in a residential area

You can try get Mweb to complain to Telkom or phone them yourself and get a petition from everyone in neigbourhood it may help if they all report it and use same fault number.

The problem with trying to get it fixed is that the average browser user wouldnt notice so it's hard to get Telkom to do something.
 
Last edited:
is your line with telkom or mweb...
either way you need to log a fault with your line as this would be line related issues
 
Mineer said:
is your line with telkom or mweb...
either way you need to log a fault with your line as this would be line related issues
Click to expand...

Ok its with Telkom but what do I report, because I told them to see if the exchange is congested-they say no, so they do a port refresh and its marginally better, but not much
 
jarrydred said:
Ok its with Telkom but what do I report, because I told them to see if the exchange is congested-they say no, so they do a port refresh and its marginally better, but not much
Click to expand...

Is the line slow or does it drop connections allot ?
if slow access then say you tried multiple ISP's
if droped connections then say you have checked your phone and filters
 
Mineer said:
Is the line slow or does it drop connections allot ?
if slow access then say you tried multiple ISP's
if droped connections then say you have checked your phone and filters
Click to expand...

it always stays synced but if you had to ping for example mweb, you'd get quite a few Request timed out and a heavy fluctuation in response time.

But thanks tomorrow I'll phone, cause a call out i can almost definitely say wont improve anything.
 
jarrydred said:
Ok its with Telkom but what do I report, because I told them to see if the exchange is congested-they say no, so they do a port refresh and its marginally better, but not much
Click to expand...

I think they're lying.
That tracert looks very much like a congested exchange.
 
Have had the same issue which I assume is a congested exchange. Is there anything one can do about it? Latency skyrockets after 18:00, and only comes down at about 23:00.
 
fragtion:
With a 384kbps line, your 2nd and 3rd hop's (ICMP ping, with data being only 64 bytes) can be as low as 8-10ms.
The 2nd and 3rd hop's latencies depends on the ISP account, Exchange congestion and of course which city/suburb you live in.

I'm in Stellenbosch, so my 2nd hop on my 4Mbps ADSL connection is 10-11ms on both my Mweb & WebAfrica accounts.
At my office (where we have a Neotel Fibre link) in Stellenbosch, my latency to WAGE (which is in Cape Town) is under 6ms :D
 
Still the frustration continues

How do i ask Telkom to see of there is a problem on the exchange side, because I cant login (90% of the time i cant)into Black Light Retribution (Awesome Game), so how should i pursue this issue, especially seen as we are also going to get bumped up to 1MEG (which how the congested exchange will handle that 1 only wonders):mad:
 
Well found out what the problem was

It seems somehow the port at the exchange was "damaged" and on top of that the was another connection (Afrihost or something woth afri) on the same port as ours so the Technician moved our connection to a new port and left afri connection in the broken port now getting much better latency and speed 0.31Mbps on a 384kbps and .18 UP. Thanks guys
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X