Telkom ADSL Performance ??

Tracing route to www.cnn.com [157.166.255.19]
over a maximum of 30 hops:

1 2 ms <1 ms <1 ms login.router [10.0.0.2]
2 8 ms 7 ms 8 ms dsl-241-124-01.telkomadsl.co.za [41.241.124.1]
3 8 ms 8 ms 8 ms rndf-ip-cat-1-vlan-913.telkom-ipnet.co.za [196.
3.33.166]
4 * * * Request timed out.
5 * * * Request timed out.
6 10 ms 8 ms 9 ms 196.43.10.130
7 11 ms 8 ms 8 ms rrba-ip-lir-1-gig-2-0-0-201.telkom-ipnet.co.za
196.43.33.5]
8 218 ms 219 ms 224 ms lon-ip-dir-stacker-pos-4-0-0-5.telkom-ipnet.co.
a [196.43.9.102]
9 230 ms 245 ms 244 ms s5-0-0-16.ipa4.lon1.bbnplanet.net [195.16.162.1
9]
10 244 ms 231 ms 240 ms vlan70.csw2.Frankfurt1.Level3.net [4.69.154.126

11 227 ms 228 ms 228 ms ae-71-71.ebr1.Frankfurt1.Level3.net [4.69.140.5

12 244 ms 245 ms 242 ms ae-48-48.ebr2.Paris1.Level3.net [4.69.143.146]
13 298 ms 303 ms 302 ms ae-44-44.ebr2.Washington1.Level3.net [4.69.137.
2]
14 316 ms 314 ms 307 ms ae-92-92.csw4.Washington1.Level3.net [4.69.134.
58]
15 318 ms 327 ms 327 ms ae-91-91.ebr1.Washington1.Level3.net [4.69.134.
41]
16 307 ms 306 ms 312 ms ae-2-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
17 330 ms 341 ms 343 ms ae-73-73.ebr2.Atlanta2.Level3.net [4.69.148.254

18 316 ms 313 ms 313 ms ae-21-52.car1.Atlanta1.Level3.net [4.69.150.67]

19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

C:\Users\Brian>tracert www.mweb.co.za

Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms login.router [10.0.0.2]
2 8 ms 7 ms 7 ms dsl-241-124-01.telkomadsl.co.za [41.241.124.1]
3 8 ms 8 ms 8 ms rrba-ip-lir-1-gig-3-0-0.telkom-ipnet.co.za [196
43.11.134]
4 8 ms 8 ms 8 ms 196.43.25.138
5 10 ms 9 ms 11 ms 197-80-4-118.jhb.mweb.co.za [197.80.4.118]
6 41 ms 41 ms 39 ms tengig0-0-0-3.vic-p-1.mweb.co.za [197.80.4.124]

7 41 ms 39 ms 39 ms tengig0-3-0-1.dbn-up-1.mweb.co.za [197.84.4.39]

8 42 ms 39 ms 39 ms tengig0-1-2-0.cpt-up-2.mweb.co.za [197.84.4.43]

9 37 ms 37 ms 37 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
10 37 ms 37 ms 37 ms 196.28.178.66
11 37 ms 37 ms 37 ms cte-core-sw2.vwol.net [196.41.144.35]
12 38 ms 37 ms 37 ms www.mweb.co.za [196.2.63.110]

Trace complete


Bushbug 23:44 May 4th
 
The traces suggest that the fault lies with Telkom ISP and not with your line.

My suggestion would be to get a 1GB prepaid account from Axxess (www.axxess.co.za) and test with that to see if it improves your speeds.
 
grim said:
The traces suggest that the fault lies with Telkom ISP and not with your line.

My suggestion would be to get a 1GB prepaid account from Axxess (www.axxess.co.za) and test with that to see if it improves your speeds.
Click to expand...

Will definitely improve speeds. The fault definitely lies with Telkom Internet ISP, without a bloody doubt.
 
I stopped using my Do3 for international gaming. I'm keeping it because you paying around R100 for 20 gig. My Webafrica Home account gives me +-100 better ping than Do3. And so does my pre-paid with Axxess and at times even my free Afrihost 1 gb surpass Do3.
 
Here's my results, almost identical except for worse pings. Telkom 384 uncapped.

Tracing route to cnn.com [157.166.226.26]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.0.2
2 22 ms 21 ms 21 ms dsl-247-7-01.telkomadsl.co.za [41.247.7.1]
3 24 ms 22 ms 22 ms ndnn-ip-cat-1-vlan-913.telkom-ipnet.co.za [196.4
3.33.150]
4 * * * Request timed out.
5 * * * Request timed out.
6 645 ms 410 ms 394 ms 196.43.48.158
7 37 ms 36 ms 41 ms rrba-ip-lir-1-gig-2-0-0-201.telkom-ipnet.co.za [
196.43.33.5]
8 225 ms 224 ms 227 ms lon-ip-dir-stacker-pos-4-0-0-5.telkom-ipnet.co.z
a [196.43.9.102]
9 660 ms 1234 ms 954 ms s5-0-0-16.ipa4.lon1.bbnplanet.net [195.16.162.12
9]
10 557 ms 352 ms 338 ms vlan90.csw4.Frankfurt1.Level3.net [4.69.154.254]

11 685 ms 1984 ms 1673 ms ae-91-91.ebr1.Frankfurt1.Level3.net [4.69.140.13
]
12 908 ms 951 ms 800 ms ae-47-47.ebr2.Paris1.Level3.net [4.69.143.142]
13 522 ms 701 ms 530 ms ae-43-43.ebr2.Washington1.Level3.net [4.69.137.5
8]
14 463 ms 328 ms 333 ms ae-72-72.csw2.Washington1.Level3.net [4.69.134.1
50]
15 942 ms 324 ms 1397 ms ae-71-71.ebr1.Washington1.Level3.net [4.69.134.1
33]
16 1013 ms 711 ms 382 ms ae-2-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
17 1791 ms 904 ms 413 ms ae-73-73.ebr2.Atlanta2.Level3.net [4.69.148.254]

18 342 ms 326 ms 426 ms ae-2-52.edge4.Atlanta2.Level3.net [4.69.150.77]

19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
Click to expand...

Are you from durban by any chance? And do you get throttled from 6am - 10pm? I'll test again tonight when i'm not throttled.
 
lilggg said:
Here's my results, almost identical except for worse pings. Telkom 384 uncapped.



Are you from durban by any chance? And do you get throttled from 6am - 10pm? I'll test again tonight when i'm not throttled.
Click to expand...

Your latency suggest that your exchange is congested and it's not the ISP's fault.
 
grim said:
Your latency suggest that your exchange is congested and it's not the ISP's fault.
Click to expand...

My exchange after a recent upgrade also is now congested, what can us normal users do to get it sorted :)?
 
grim said:
Your latency suggest that your exchange is congested and it's not the ISP's fault.
Click to expand...

I have no problems with afrihost or cybersmart if i do tracert's or pings or speedtests. A telkom techie came after i reported rubbish international speeds during the day and even he said it's ISP and i should change.
 
Redid the test 2am, much better results

Tracing route to cnn.com [157.166.226.26]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.0.2
2 25 ms 22 ms 22 ms dsl-247-7-01.telkomadsl.co.za [41.247.7.1]
3 23 ms 23 ms 22 ms ndnn-ip-cat-1-vlan-913.telkom-ipnet.co.za [196.4
3.33.150]
4 * * * Request timed out.
5 * * * Request timed out.
6 35 ms 32 ms 31 ms 196.43.48.158
7 36 ms 35 ms 33 ms rrba-ip-lir-1-gig-2-0-0-201.telkom-ipnet.co.za [
196.43.33.5]
8 223 ms 225 ms 224 ms lon-ip-dir-stacker-pos-4-0-0-5.telkom-ipnet.co.z
a [196.43.9.102]
9 226 ms 223 ms 221 ms s5-0-0-16.ipa4.lon1.bbnplanet.net [195.16.162.12
9]
10 225 ms 225 ms 223 ms vlan90.csw4.Frankfurt1.Level3.net [4.69.154.254]

11 221 ms 225 ms 223 ms ae-91-91.ebr1.Frankfurt1.Level3.net [4.69.140.13
]
12 228 ms * 232 ms ae-47-47.ebr2.Paris1.Level3.net [4.69.143.142]
13 312 ms 312 ms 311 ms ae-43-43.ebr2.Washington1.Level3.net [4.69.137.5
8]
14 309 ms 316 ms 310 ms ae-72-72.csw2.Washington1.Level3.net [4.69.134.1
50]
15 309 ms 314 ms 309 ms ae-71-71.ebr1.Washington1.Level3.net [4.69.134.1
33]
16 324 ms 324 ms 322 ms ae-2-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
17 325 ms 322 ms 327 ms ae-73-73.ebr2.Atlanta2.Level3.net [4.69.148.254]

18 325 ms 323 ms 328 ms ae-2-52.edge4.Atlanta2.Level3.net [4.69.150.77]

19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
Click to expand...
 
grim said:
Your latency suggest that your exchange is congested and it's not the ISP's fault.
Click to expand...

Hi there. I was reading this thread, not knowing much of what you people are talking. I checked my Router, and just want to ask if my results looks okay on the router?
SNR Margin-Downstream:40.3 DB, Upstream 14,0 DB
Line Attenuation-Downstream:12.5 DB, Upstream 8.5 DB
I'm on 1 meg line with Mweb.
I was complaining by Mweb for not good line speed. They somehow sorted it out. The techhy said though that my speedtest uploading of 40kbps is little high.
Hope it makes sence to you

Thanx
Chris
 
Lionking said:
Hi there. I was reading this thread, not knowing much of what you people are talking. I checked my Router, and just want to ask if my results looks okay on the router?
SNR Margin-Downstream:40.3 DB, Upstream 14,0 DB
Line Attenuation-Downstream:12.5 DB, Upstream 8.5 DB
I'm on 1 meg line with Mweb.
I was complaining by Mweb for not good line speed. They somehow sorted it out. The techhy said though that my speedtest uploading of 40kbps is little high.
Hope it makes sence to you

Thanx
Chris
Click to expand...

You've got excellent line stats so you shouldn't have any speed issues related to your line. 40KBps upload on a 1Mbps line is normal as your upload sync rate should be 512Kbps which is 64KBps without overheads
 
Are there any managers at Telkom Internet I can contact?

Or do they simply not give a toss about their ISP's *&^*% performance.
 
MickeyD said:
Start by sending a PM to 'ranger'.
Click to expand...

I've seen his posts in the other thread. I wonder if he will tell me more than it's "my ISP" after I paste the stats which seems to be what he's assessing? My exchange certainly isn't congested and other ADSL accounts perform well. And 10219 said nothing is wrong.

There is something FUBAR at Telkom Internet ISP and they must sort it out.
 
PostmanPot said:
I've seen his posts in the other thread. I wonder if he will tell me more than it's "my ISP" after I paste the stats which seems to be what he's assessing? My exchange certainly isn't congested and other ADSL accounts perform well. And 10219 said nothing is wrong.

There is something FUBAR at Telkom Internet ISP and they must sort it out.
Click to expand...
He works there...
 
PostmanPot said:
There is something FUBAR at Telkom Internet ISP and they must sort it out.
Click to expand...
s/Telkom Internet ISP/SAIX/

Everything is working to spec here.

We know of one technical issue at SAIX (that requires some financial processes to be concluded to be addressed), but we have been unable to get conclusive answers on whether this technical issue can be causing the behaviour you and a few other users (madala, lilggg) have been seeing. As far as I understand the SAIX design, it should not be impacting local traffic, only int.

I haven't looked through all your posts, but could you point me to a speedtest result to both the Cape Town and Rosebank SAIX speedtest servers (or from just paste the results from http://capetown.spdtst.saix.net/) while connected on your TI account, with no other downloads running. Please PM me either the TI username you are using, or your IP address at the time of the speedtest (PM'ing me your TI username would save me some time as I don't need to consult the traffic accounting database). As usual, a traceroute may also be useful. I can't promise anything, but we are trying to resolve these issues (taking into account other workload, problems in highlighting the scale/impact of the problem to multiple different units in the company etc. who don't necessarily have the same - or non-conflicting - targets/priorities).
 
/sees ranger :D

govt_red_tape.jpg.gif
 
grim said:
The traces suggest that the fault lies with Telkom ISP and not with your line.
Click to expand...

I assume you were responding to Bushbug's post that preceded this one. If so, how do you arrive at this conclusion. I see no problem with 300ms latency from Johannesburg to Atlanta via Rosebank, London, Paris, Frankfurt and Washington (quite a route Level3 takes there), or ~30ms from Johannesburg to MWeb in Cape Town via Durban.

@Bushbug, traces under normal conditions are useful for reference, but I need to see speedtests to your closest SAIX speedtest server, at least one other SAIX speedtest server, an international one, and the traceroute to a site in the same country, all completed while experiencing a slow connection, while you have minimal other network utilisation (e.g., no downloads, no updates, no torrents, no uploads of any kind). Then, PM me your TI username that you were using at the time (or the IP address you had, but providing the username saves me doing a few database queries).
 
ranger said:
s/Telkom Internet ISP/SAIX/

Everything is working to spec here.

We know of one technical issue at SAIX (that requires some financial processes to be concluded to be addressed), but we have been unable to get conclusive answers on whether this technical issue can be causing the behaviour you and a few other users (madala, lilggg) have been seeing. As far as I understand the SAIX design, it should not be impacting local traffic, only int.

I haven't looked through all your posts, but could you point me to a speedtest result to both the Cape Town and Rosebank SAIX speedtest servers (or from just paste the results from http://capetown.spdtst.saix.net/) while connected on your TI account, with no other downloads running. Please PM me either the TI username you are using, or your IP address at the time of the speedtest (PM'ing me your TI username would save me some time as I don't need to consult the traffic accounting database). As usual, a traceroute may also be useful. I can't promise anything, but we are trying to resolve these issues (taking into account other workload, problems in highlighting the scale/impact of the problem to multiple different units in the company etc. who don't necessarily have the same - or non-conflicting - targets/priorities).
Click to expand...

Thanks, turns out the debit order limit of R500 is enforced by telkom, not the bank. :confused: and everything owed was paid, and being doubled billed isn't helping. So would everything be fine if we ask telkom to increase the limit? If of course that is causing the problems.
 
Last edited:
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X