Plumstead ADSL Problems

riverdusty

riverdusty

Senior Member
Joined
Jun 8, 2006
Messages
639
Reaction score
4
Location
Cape Town
Problem: Telkom Congested Exchange
Exchange: 021 762
Line Speed: 2Mbs
ISP: Mweb Premium 1Mbs Uncapped
Occurance: All the time, more so at night.


Traceroute:
traceroute to telkom.co.za (196.43.22.222), 64 hops max, 52 byte packets
1 login.router (10.0.0.2) 2.072 ms 1.559 ms 1.591 ms
2 41-133-138-1.dsl.mweb.co.za (41.133.138.1) 516.303 ms 597.365 ms 638.834 ms
3 197-84-96-186.cpt.mweb.co.za (197.84.96.186) 669.696 ms 555.963 ms 774.675 ms

Sync: Downstream / Upstream (Kbps) 2048/512

Attenuation stats: (?!)
DS Line Attenuation 43
US Line Attenuation 22
 
Hi

I am also an 021 762 number.
I am connecting to the Wynberg exchange and I have no problems.

Perhaps get one of the free 1GB accounts from Afrihost / WebAfrica / Axxess and run some trace routes with these just to confirm it is an exchange problem.

You could also run Zertops Diagnostic and IS It My Line tools as well on your Mweb account and then perhaps one of the other free accounts to compare results.

riverdusty said:
Problem: Telkom Congested Exchange
Exchange: 021 762
Line Speed: 2Mbs
ISP: Mweb Premium 1Mbs Uncapped
Occurance: All the time, more so at night.


Traceroute:
traceroute to telkom.co.za (196.43.22.222), 64 hops max, 52 byte packets
1 login.router (10.0.0.2) 2.072 ms 1.559 ms 1.591 ms
2 41-133-138-1.dsl.mweb.co.za (41.133.138.1) 516.303 ms 597.365 ms 638.834 ms
3 197-84-96-186.cpt.mweb.co.za (197.84.96.186) 669.696 ms 555.963 ms 774.675 ms

Sync: Downstream / Upstream (Kbps) 2048/512

Attenuation stats: (?!)
DS Line Attenuation 43
US Line Attenuation 22
Click to expand...
 
I'm also in Plum but on 021 705, Grassy Park exchange, manage to get 4MBit fine but can't go any higher.

Would advise you get a free gig as i.got~issues said.. will narrow down if its your ISP or your line though it does seem like congestion
 
I have got a free AfriHost account and same story. I've also tried with telkom guest account, same story.
I'll try those other Diagnostics tools, if I find a windows machine lying around here.

Just been up the road to a friend on 021 761 and he says his nightly pings on first hop can go over 2000ms...
 
LineTool Results on Mweb Account


Zertop's "Is it my Line" Results
Basic Report:

Your average ping was 743ms
Your maximum ping was 850ms

Looking at your average ping, there is definitely something wrong with your line-( Please post the results (at the end of the program) into the forum for advice


Detailed Report

Code: 
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 41.133.138.1 with 32 bytes of data:
Reply from 41.133.138.1: bytes=32 time=700ms TTL=254
Reply from 41.133.138.1: bytes=32 time=787ms TTL=254
Reply from 41.133.138.1: bytes=32 time=696ms TTL=254
Reply from 41.133.138.1: bytes=32 time=724ms TTL=254
Reply from 41.133.138.1: bytes=32 time=749ms TTL=254
Reply from 41.133.138.1: bytes=32 time=756ms TTL=254
Reply from 41.133.138.1: bytes=32 time=696ms TTL=254
Reply from 41.133.138.1: bytes=32 time=689ms TTL=254
Reply from 41.133.138.1: bytes=32 time=796ms TTL=254
Reply from 41.133.138.1: bytes=32 time=793ms TTL=254
Reply from 41.133.138.1: bytes=32 time=732ms TTL=254
Reply from 41.133.138.1: bytes=32 time=621ms TTL=254
Reply from 41.133.138.1: bytes=32 time=761ms TTL=254
Reply from 41.133.138.1: bytes=32 time=797ms TTL=254
Reply from 41.133.138.1: bytes=32 time=767ms TTL=254
Reply from 41.133.138.1: bytes=32 time=757ms TTL=254
Request timed out.
Reply from 41.133.138.1: bytes=32 time=533ms TTL=254
Reply from 41.133.138.1: bytes=32 time=758ms TTL=254
Reply from 41.133.138.1: bytes=32 time=835ms TTL=254
Reply from 41.133.138.1: bytes=32 time=771ms TTL=254
Reply from 41.133.138.1: bytes=32 time=700ms TTL=254
Reply from 41.133.138.1: bytes=32 time=753ms TTL=254
Reply from 41.133.138.1: bytes=32 time=843ms TTL=254
Reply from 41.133.138.1: bytes=32 time=811ms TTL=254
Reply from 41.133.138.1: bytes=32 time=814ms TTL=254
Reply from 41.133.138.1: bytes=32 time=850ms TTL=254
Reply from 41.133.138.1: bytes=32 time=712ms TTL=254
Reply from 41.133.138.1: bytes=32 time=626ms TTL=254
Reply from 41.133.138.1: bytes=32 time=735ms TTL=254

Ping statistics for 41.133.138.1:
    Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
    Minimum = 533ms, Maximum = 850ms, Average = 743ms
 
2014/06/27 14:47:20.34
 
LineTool Results on AfriHost account:


Zertop's "Is it my Line" Results
Basic Report:

Your average ping was 621ms
Your maximum ping was 803ms

Looking at your average ping, there is definitely something wrong with your line-( Please post the results (at the end of the program) into the forum for advice


Detailed Report

Code: 
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 105.236.9.65 with 32 bytes of data:
Reply from 105.236.9.65: bytes=32 time=720ms TTL=254
Reply from 105.236.9.65: bytes=32 time=803ms TTL=254
Reply from 105.236.9.65: bytes=32 time=724ms TTL=254
Reply from 105.236.9.65: bytes=32 time=619ms TTL=254
Reply from 105.236.9.65: bytes=32 time=651ms TTL=254
Reply from 105.236.9.65: bytes=32 time=597ms TTL=254
Reply from 105.236.9.65: bytes=32 time=529ms TTL=254
Reply from 105.236.9.65: bytes=32 time=620ms TTL=254
Reply from 105.236.9.65: bytes=32 time=741ms TTL=254
Reply from 105.236.9.65: bytes=32 time=760ms TTL=254
Reply from 105.236.9.65: bytes=32 time=483ms TTL=254
Reply from 105.236.9.65: bytes=32 time=482ms TTL=254
Reply from 105.236.9.65: bytes=32 time=562ms TTL=254
Reply from 105.236.9.65: bytes=32 time=703ms TTL=254
Reply from 105.236.9.65: bytes=32 time=745ms TTL=254
Reply from 105.236.9.65: bytes=32 time=483ms TTL=254
Reply from 105.236.9.65: bytes=32 time=490ms TTL=254
Reply from 105.236.9.65: bytes=32 time=600ms TTL=254
Reply from 105.236.9.65: bytes=32 time=638ms TTL=254
Reply from 105.236.9.65: bytes=32 time=664ms TTL=254
Reply from 105.236.9.65: bytes=32 time=682ms TTL=254
Request timed out.
Reply from 105.236.9.65: bytes=32 time=735ms TTL=254
Reply from 105.236.9.65: bytes=32 time=663ms TTL=254
Reply from 105.236.9.65: bytes=32 time=469ms TTL=254
Reply from 105.236.9.65: bytes=32 time=453ms TTL=254
Reply from 105.236.9.65: bytes=32 time=466ms TTL=254
Reply from 105.236.9.65: bytes=32 time=513ms TTL=254
Reply from 105.236.9.65: bytes=32 time=663ms TTL=254
Reply from 105.236.9.65: bytes=32 time=763ms TTL=254

Ping statistics for 105.236.9.65:
    Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
    Minimum = 453ms, Maximum = 803ms, Average = 621ms
 
2014/06/27 14:51:21.36
 
riverdusty said:
LineTool Results on Mweb Account


Zertop's "Is it my Line" Results
Basic Report:

Your average ping was 743ms
Your maximum ping was 850ms

Looking at your average ping, there is definitely something wrong with your line-( Please post the results (at the end of the program) into the forum for advice

<snip>
Click to expand...

OUCH!

There is definitely a problem there.

My results after running the test now;

Code: 
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 41.181.221.254 with 32 bytes of data:
Reply from 41.181.221.254: bytes=32 time=17ms TTL=60
Reply from 41.181.221.254: bytes=32 time=11ms TTL=60
Reply from 41.181.221.254: bytes=32 time=12ms TTL=60
Reply from 41.181.221.254: bytes=32 time=12ms TTL=60
Reply from 41.181.221.254: bytes=32 time=19ms TTL=60
Reply from 41.181.221.254: bytes=32 time=17ms TTL=60
Reply from 41.181.221.254: bytes=32 time=11ms TTL=60
Reply from 41.181.221.254: bytes=32 time=12ms TTL=60
Reply from 41.181.221.254: bytes=32 time=43ms TTL=60
Reply from 41.181.221.254: bytes=32 time=12ms TTL=60
Reply from 41.181.221.254: bytes=32 time=10ms TTL=60
Reply from 41.181.221.254: bytes=32 time=11ms TTL=60
Reply from 41.181.221.254: bytes=32 time=18ms TTL=60
Reply from 41.181.221.254: bytes=32 time=14ms TTL=60
Reply from 41.181.221.254: bytes=32 time=24ms TTL=60
Reply from 41.181.221.254: bytes=32 time=14ms TTL=60
Reply from 41.181.221.254: bytes=32 time=16ms TTL=60
Reply from 41.181.221.254: bytes=32 time=13ms TTL=60
Reply from 41.181.221.254: bytes=32 time=11ms TTL=60
Reply from 41.181.221.254: bytes=32 time=41ms TTL=60
Reply from 41.181.221.254: bytes=32 time=19ms TTL=60
Reply from 41.181.221.254: bytes=32 time=12ms TTL=60
Reply from 41.181.221.254: bytes=32 time=20ms TTL=60
Reply from 41.181.221.254: bytes=32 time=36ms TTL=60
Reply from 41.181.221.254: bytes=32 time=17ms TTL=60
Reply from 41.181.221.254: bytes=32 time=16ms TTL=60
Reply from 41.181.221.254: bytes=32 time=11ms TTL=60
Reply from 41.181.221.254: bytes=32 time=13ms TTL=60
Reply from 41.181.221.254: bytes=32 time=22ms TTL=60
Reply from 41.181.221.254: bytes=32 time=15ms TTL=60

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

It might be your router, but if your mate a few houses down is also seeing the same rubbish results as you then you do indeed need Telkom to check your line and also possibly your connection at the exchange.

Eish.

EDIT: Try having your ADSL port reset, if your ADSL line is with Telkom phone them and request this, and if your ADSL line is with an ISP, contact them as well and request a port reset. See if this makes any difference.
 
Last edited:
I have had the port reset like 10 times. Every time I get < 10ms pings for a day.
After a day the problem returns.

The fact that after a port reset I get very decent results (for a limited time) leads me to believe my router is ok. I did at one time think perhaps I should look into the router issue, but as I mentioned above, I'm pretty sure router is fine and problem is the exchange.
 
No problems since 13th Feb. Currently 28ms pings to Axxess. My telephone no is 021-761XXXX
 
It is very hard to pinpoint the fault at an exchange or local box or line... but constantly reporting issues and resetting ports eventually gets something actioned.

For almost 6 months my line and the Wynberg exchange were blamed by OpenWeb, and then Afrihost (initially) for absolutely rubbish internet.
I paid for 2 Telkom call-outs and replaced my modem and router and nothing improved until I moved to Afrihost... and then they had IPC issues, and blamed my equipment and Telkom again before admitting to their IPC bottleneck. You will get a run-around and finger pointing blame-game... but perseverance will pay off.

Politeness and perseverance is one's only recourse.

At the very least you will get action from Telkom regarding your line and port at the exchange.

I am assuming you are connected to the Wynberg exchange?

My ADSL is fault free at the moment (touch wood) but I can fully sympathise with your situation... I too have endured the same rubbish and hoop-jumping.
BUT there is light at the end of the tunnel, well, for me there has been...

100628414.png

100628644.png

I am sure other more knowledgeable forumites will add their advice to this thread soon. Good luck.


riverdusty said:
I have had the port reset like 10 times. Every time I get < 10ms pings for a day.
After a day the problem returns.

The fact that after a port reset I get very decent results (for a limited time) leads me to believe my router is ok. I did at one time think perhaps I should look into the router issue, but as I mentioned above, I'm pretty sure router is fine and problem is the exchange.
Click to expand...
 
--- telkom.co.za ping statistics ---
14657 packets transmitted, 1262 packets received, 91.4% packet loss
round-trip min/avg/max/stddev = 513.385/736.339/897.982/73.826 ms

...No Comment
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X