Stellenbosch ADSL slow

G

Geek_wannabe

Well-Known Member
Joined
Jun 17, 2005
Messages
248
Reaction score
0
Location
Cape Town
Hi

I recently got an ADSL line - about three weeks ago - and everything's been working fine. Recently, however, my speeds have decreased enormously. I thought that I might be throttled/shaped, but that turned out not to be the case. I created another capped ADSL account with Vox Telecoms (my default is just TelkomInternet) and both connections are excruciatingly slow. Here are the technical details (on both ISPs they are quite similar):

Router Info:
Upstream line rate (kbit/s): 512
Downstream line rate (kbit/s): 4096
Upstream maximum line rate (kbit/s): 1056
Downstream maximum line rate (kbit/s): 12264
Upstream noise safety coefficient(SNR) (dB): 14
Downstream noise safety coefficient(SNR) (dB): 21.8

Speedtest Results:
Latency: 267 ms
Download Rate: 90 kbps
Upload Rate: 20 kbps

Is anyone else in Stellenbosch (Central) experiencing similar issues?
 
could you ping bras.afrihost.com and post it here please.
Could you also run a tracert to mybroadband.co.za
 
Hi

ping timed out to that specific address so I just did it to afrihost.com.

Pinging afrihost.com [41.181.185.18] with 32 bytes of data:
Reply from 41.181.185.18: bytes=32 time=108ms TTL=47
Reply from 41.181.185.18: bytes=32 time=125ms TTL=47
Reply from 41.181.185.18: bytes=32 time=97ms TTL=47
Reply from 41.181.185.18: bytes=32 time=90ms TTL=47

Ping statistics for 41.181.185.18:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 90ms, Maximum = 125ms, Average = 105ms


I also ran the tracert and here are the results (this is on the VOX account. I can also post one from TelkomInternet account?)

Tracing route to mybroadband.co.za [104.20.72.110]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 10.0.0.2
2 75 ms 83 ms 74 ms dsl-197-245-49-1.voxdsl.co.za [197.245.49.1]
3 77 ms * 71 ms telkom-upload-vlan-barrack-ipc.vox.co.za [41.193.121.9]
4 76 ms 77 ms 74 ms vox-upload-teraco-cpt-barrack-ipc.vox.co.za [41.193.121.10]
5 78 ms 77 ms 78 ms vox-b2b-pts-barrack-ipc-int.vox.co.za [209.203.1.41]
6 * 98 ms 75 ms africainx.ct1.napafrica.net [196.10.140.7]
7 112 ms 94 ms 93 ms CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za [41.84.13.228]
8 84 ms * 90 ms 41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59]
9 83 ms * 95 ms 104.20.72.110

Trace complete.
 
Here is the same tracert from my TelkomInternet account.

Tracing route to mybroadband.co.za [104.20.72.110]
over a maximum of 30 hops:

1 2 ms 1 ms 2 ms 10.0.0.2
2 73 ms 107 ms 69 ms wblv-ip-bb-3.south.dsl.telkomsa.net [105.224.200.1]
3 89 ms 87 ms * ipc-1-up.south.dsl.telkomsa.net [105.226.0.6]
4 125 ms 118 ms 116 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13]
5 114 ms 99 ms 91 ms jb1-pr-01-te1-0.net.telkomsa.net [105.187.249.6]
6 117 ms 102 ms 132 ms jb1-pr-01-te1-0.net.telkomsa.net [105.187.249.6]
7 113 ms 101 ms 103 ms cloudflare.jb1.napafrica.net [196.46.25.198]
8 * 92 ms 92 ms 104.20.72.110

Trace complete.
 
The bras.afrihost.com is in order to ping the exchange in case your exchange does not reply to it.
Might not work if you are not an afrihost client, just try pinging 155.239.255.250
Thing is, your first hop is quite high, it could be congestion, a line fault or telkom maintenance (as it is persistent throughout both of your tests it does not indicate an ISP issue).

EDIT:
Example of a tracert for me to mybroadband for you to compare with:
Code: 
Tracing route to mybroadband.co.za [104.20.71.110]
over a maximum of 30 hops:

  1     3 ms     6 ms     7 ms  home.gateway.pace.net [192.168.1.1] <-- streaming over WiFi, this should be <2ms preferably.
  2     *        *        *     Request timed out. <-- new exchanges do not reply to pings/tracerts.
  3    14 ms    29 ms    11 ms  cpt-up1.ip.adsl.co.za [169.1.5.105] <-- hop onto network of ISP
  4    27 ms    41 ms    26 ms  cpt-in1.ip.adsl.co.za [169.1.5.118]
  5    55 ms    37 ms   116 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6    33 ms    15 ms    18 ms  africainx.ct1.napafrica.net [196.10.140.7]
  7    41 ms    28 ms    29 ms  CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za [41.84.13.228]
  8    92 ms   117 ms   106 ms  41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59]
  9    31 ms    48 ms    77 ms  104.20.71.110

Trace complete.
 
Last edited:
Odd that the pinging didn't work. Here are the results anyway:

Pinging 155.239.255.250 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),



This is an interesting dilemma as I've never had to deal with ADSL issues before. What's the usual route to follow in order to address the issue?
 
Geek_wannabe said:
Odd that the pinging didn't work. Here are the results anyway:

Pinging 155.239.255.250 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),



This is an interesting dilemma as I've never had to deal with ADSL issues before. What's the usual route to follow in order to address the issue?
Click to expand...

Opening a fault with Telkom. Call Vox first and see if you can get the Tech support to make a check for you from their side, dealing with Telkom is extremely frustrating.
You can call Telkom on any landline with 10210 for free, good luck getting through. You can also use: https://secureapp.telkom.co.za/assurance/public/logafault

If it is congestion and not a line fault, you will have a long wait ahead of you, Telkom has a long list of congested exchanges. If there is no problem with latency tomorrow morning, it is most likely congestion, if it is still there it might "only" be a line fault.
 
Last edited:
It's a pity considering that this has been continually going on for about 4 days, so I assume it's "only" a line issue. Is there a long road ahead in terms of getting this resolved?

[I've contacted Vox; hopefully they can sort it out with Telkom]
 
Geek_wannabe said:
It's a pity considering that this has been continually going on for about 4 days, so I assume it's "only" a line issue. Is there a long road ahead in terms of getting this resolved?

[I've contacted Vox; hopefully they can sort it out with Telkom]
Click to expand...

If it is a line fault a technician will hopefully arrive in the next couple of days and sort it out (ask Vox to open a line fault for you or use the online portal I linked earlier).
If it is a congested exchange you're out of luck. Let us hope it is the former and not the latter.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X