Grahamstown ADSL Problem - Please help with line testing

Gatecrasher said:
What do you get on this test?

http://streamingmediahosting.com/support/speed_test

I get 0.22Mbps down and 0.26Mbps up, which fairly accurately reflects the results I have trying to watch streaming media.
Click to expand...

Well, my power just came back on after that scheduled power cut. I was hoping it would reboot something or other in the exchange and fix our problems :D . Sadly, not to be :cry:

1.73 down and 0.25 up
 
There is not an emoticon available to describe the hatred I am feeling towards Telkom at the moment :(
 
I discovered an interesting utility in Windows that combines a trace route and packet loss test: pathping.

Here is my result to google.com

Code: 
C:\>pathping google.com

Tracing route to google.com [74.125.233.40]
over a maximum of 30 hops:
  0  xxxxxx-xxxx-PC.localnet [192.168.10.115]
  1  dsldevice.lan [192.168.10.1]
  2  105-236-8-129-esr-lo.mtnbusiness.co.za [105.236.8.129]
  3  41.181.221.254
  4  41.181.198.188
  5  unc-cpt-1.mtnns.net [196.44.18.8]
  6  196.44.31.106
  7  ct-cr-2.za--rb-cr-2.za-a.mtnns.net [196.44.31.30]
  8  41.181.139.99
  9  72.14.194.74
 10  64.233.174.21
 11  jnb01s01-in-f8.1e100.net [74.125.233.40]

Computing statistics for 275 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           xxxxxx-xxxx-PC.localnet [192.168.10.115]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  dsldevice.lan [192.168.10.1]
                                1/ 100 =  1%   |
  2   19ms     4/ 100 =  4%     3/ 100 =  3%  105-236-8-129-esr-lo.mtnbusiness.co.za [105.236.8.129]
                                0/ 100 =  0%   |
  3   30ms     4/ 100 =  4%     3/ 100 =  3%  41.181.221.254
                                0/ 100 =  0%   |
  4   22ms     6/ 100 =  6%     5/ 100 =  5%  41.181.198.188
                                0/ 100 =  0%   |
  5   27ms     3/ 100 =  3%     2/ 100 =  2%  unc-cpt-1.mtnns.net [196.44.18.8]
                                0/ 100 =  0%   |
  6   51ms     6/ 100 =  6%     5/ 100 =  5%  196.44.31.106
                                0/ 100 =  0%   |
  7   49ms     1/ 100 =  1%     0/ 100 =  0%  ct-cr-2.za--rb-cr-2.za-a.mtnns.net [196.44.31.30]
                                0/ 100 =  0%   |
  8   60ms     4/ 100 =  4%     3/ 100 =  3%  41.181.139.99
                                0/ 100 =  0%   |
  9   69ms     4/ 100 =  4%     3/ 100 =  3%  72.14.194.74
                                0/ 100 =  0%   |
 10   56ms     5/ 100 =  5%     4/ 100 =  4%  64.233.174.21
                                0/ 100 =  0%   |
 11   55ms     1/ 100 =  1%     0/ 100 =  0%  jnb01s01-in-f8.1e100.net [74.125.233.40]

Trace complete.

Doesn't quite show the same % packet loss as the 4k data loaded pings. But any packet loss of 2% or more has severe consequences for broadband speeds and throughput since it results in a constant re-transmission of data and reduces the TCP receive window crippling one's download speeds.
 
Gatecrasher said:
I discovered an interesting utility in Windows that combines a trace route and packet loss test: pathping.

Here is my result to google.com

Code: 
C:\>pathping google.com

Tracing route to google.com [74.125.233.40]
over a maximum of 30 hops:
  0  xxxxxx-xxxx-PC.localnet [192.168.10.115]
  1  dsldevice.lan [192.168.10.1]
  2  105-236-8-129-esr-lo.mtnbusiness.co.za [105.236.8.129]
  3  41.181.221.254
  4  41.181.198.188
  5  unc-cpt-1.mtnns.net [196.44.18.8]
  6  196.44.31.106
  7  ct-cr-2.za--rb-cr-2.za-a.mtnns.net [196.44.31.30]
  8  41.181.139.99
  9  72.14.194.74
 10  64.233.174.21
 11  jnb01s01-in-f8.1e100.net [74.125.233.40]

Computing statistics for 275 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           xxxxxx-xxxx-PC.localnet [192.168.10.115]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  dsldevice.lan [192.168.10.1]
                                1/ 100 =  1%   |
  2   19ms     4/ 100 =  4%     3/ 100 =  3%  105-236-8-129-esr-lo.mtnbusiness.co.za [105.236.8.129]
                                0/ 100 =  0%   |
  3   30ms     4/ 100 =  4%     3/ 100 =  3%  41.181.221.254
                                0/ 100 =  0%   |
  4   22ms     6/ 100 =  6%     5/ 100 =  5%  41.181.198.188
                                0/ 100 =  0%   |
  5   27ms     3/ 100 =  3%     2/ 100 =  2%  unc-cpt-1.mtnns.net [196.44.18.8]
                                0/ 100 =  0%   |
  6   51ms     6/ 100 =  6%     5/ 100 =  5%  196.44.31.106
                                0/ 100 =  0%   |
  7   49ms     1/ 100 =  1%     0/ 100 =  0%  ct-cr-2.za--rb-cr-2.za-a.mtnns.net [196.44.31.30]
                                0/ 100 =  0%   |
  8   60ms     4/ 100 =  4%     3/ 100 =  3%  41.181.139.99
                                0/ 100 =  0%   |
  9   69ms     4/ 100 =  4%     3/ 100 =  3%  72.14.194.74
                                0/ 100 =  0%   |
 10   56ms     5/ 100 =  5%     4/ 100 =  4%  64.233.174.21
                                0/ 100 =  0%   |
 11   55ms     1/ 100 =  1%     0/ 100 =  0%  jnb01s01-in-f8.1e100.net [74.125.233.40]

Trace complete.

Doesn't quite show the same % packet loss as the 4k data loaded pings. But any packet loss of 2% or more has severe consequences for broadband speeds and throughput since it results in a constant re-transmission of data and reduces the TCP receive window crippling one's download speeds.
Click to expand...

Nice find!!

Here is mine (from African Street) to google.co.za

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\>pathping www.google.co.za

Tracing route to www.google.co.za [74.125.136.94]
over a maximum of 30 hops:
0 local-pc.co.za [192.168.3.155]
1 192.168.3.253
2 10.0.0.2
3 * 105-236-8-129-esr-lo.mtnbusiness.co.za [105.236.8.129]
4 ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
5 * 41.181.198.188
6 unc-cpt-1.mtnns.net [196.44.18.8]
7 196.44.31.106
8 am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.221]
9 ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
10 195.66.224.125
11 209.85.240.61
12 209.85.253.90
13 209.85.240.28
14 216.239.49.38
15 * * *
Computing statistics for 350 seconds...
Click to expand...

It doesn't go further than computing statistics though...seems to get stuck there...
 
I waited about 3500 seconds :P but it just got stuck there...no CPU usage from the cmd prompt either at the time.

I'll try again tonight if I don't end up watching Star Trek at Roxbury :P
 
I hate being left in the dark like this. The fault logged for me by the social media guy has been "in hand" with a technician since Thursday yet I havent heard from a tech. The least they could do is put up a network notice on SAIX or something.
 
I got a call just now from the new MyBroadband Telkom rep. Did promise to take this up the area manager. Telkom don't really see that there is anything wrong, since there is no exchange congestion. It seems they don't really know what packet loss is, or how to test for it. So I'm not that hopeful that they will know how to fix it. Our best hope is that someone will accidentally trip over a power cord and cause the offending server/router to get a reboot.
 
Gatecrasher said:
Yeah, that and the TV is the only streaming video you'll find in Grahamstown!
Click to expand...
Gosh, and I have about 2 hrs of online training to get through as well...might as well set out a whole evening just to buffer it :/
 
Line went down at 5:40am. Came back at 6am. And....

FIXED!

Code: 
Tracing route to google.com [74.125.233.38]
over a maximum of 30 hops:
  0  xxxxxx-xxxx-PC.localnet [192.168.10.122]
  1  dsldevice.lan [192.168.10.1]
  2  105-236-8-129-esr-lo.mtnbusiness.co.za [105.236.8.129]
  3  41.181.221.254
  4  41.181.198.188
  5  compj-cpt-1.mtnns.net [196.44.18.2]
  6  ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
  7  pb-ad-1.za--pb-sla-1-a.mtnns.net [196.44.31.128]
  8  41.181.139.109
  9  72.14.194.74
 10  64.233.174.21
 11  jnb01s01-in-f6.1e100.net [74.125.233.38]

Computing statistics for 275 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           xxxxxx-xxxx-PC.localnet [192.168.10.122]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  dsldevice.lan [192.168.10.1]
                                0/ 100 =  0%   |
  2   28ms     0/ 100 =  0%     0/ 100 =  0%  105-236-8-129-esr-lo.mtnbusiness.co.za [105.236.8.129]
                                0/ 100 =  0%   |
  3   38ms     0/ 100 =  0%     0/ 100 =  0%  41.181.221.254
                                0/ 100 =  0%   |
  4   31ms     0/ 100 =  0%     0/ 100 =  0%  41.181.198.188
                                0/ 100 =  0%   |
  5   45ms     0/ 100 =  0%     0/ 100 =  0%  compj-cpt-1.mtnns.net [196.44.18.2]
                                0/ 100 =  0%   |
  6   29ms     0/ 100 =  0%     0/ 100 =  0%  ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
                                0/ 100 =  0%   |
  7   52ms     0/ 100 =  0%     0/ 100 =  0%  pb-ad-1.za--pb-sla-1-a.mtnns.net [196.44.31.128]
                                0/ 100 =  0%   |
  8   48ms     1/ 100 =  1%     1/ 100 =  1%  41.181.139.109
                                0/ 100 =  0%   |
  9   54ms     0/ 100 =  0%     0/ 100 =  0%  72.14.194.74
                                0/ 100 =  0%   |
 10   52ms     0/ 100 =  0%     0/ 100 =  0%  64.233.174.21
                                0/ 100 =  0%   |
 11   49ms     0/ 100 =  0%     0/ 100 =  0%  jnb01s01-in-f6.1e100.net [74.125.233.38]

Trace complete.
 
Last edited:
Been following the ASNoutages e-mail feed as well and they also said there was hope! :D

Lines are back, and traffic has been re-distributed

Some work appears to have happened last night relating to DSL , as the dropped lines have restarted. Testing from my home DSL has shown a return to performance seenin early May
Click to expand...

W00t!
 
Great stuff! Now for some serious gaming! Who should we thank though, was it TelkomZA here on the forum or what.
 
Looks like everything is getting back to normal. Tested my home line from work (PS3 downloading) and I am getting my regular speeds. Took long enough, but at least now I can stream Netflix
 
Pathetic (to CT):

2885868316.png


Strangely enough to Canterbury the ping is better:

2885871091.png


This is on a 10Mbps Axxess account :/
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X