Telkom Internet Capped/Uncapped User Feedback (Pt2)

el capitan said:
Two days later, and no reply from a moderator..

I'm getting a maximum 2-7Mbps on a 20Mbps line, when I get anything... most of the time it's down to 0.

Subsequent Speed tests have been returning "Latency test error".

I've sent a fault report to Telkom... will see if something gets done.
Click to expand...

Erm, a moderator can't fix speed issues. Get in touch with Telkom on twitter. They will sort you out.
 
Must admit although sync speed is great and downloads are ok. Streaming anything is abysmal!
 
Ranger: any idea why a lot of traffic is Routing via Jhb>CPT>JHB? It seems to be a lot of services going this route. Host1plus, Mweb, etc seems to be taking that odd route.
 
Good evening. Please can someone assist me. I am in northern KZN and currently playing CSGO on the official servers is almost impossible. I get a ping of around 300. When doing a speedtest on saix.net, i get decent numbers to the Durban server but when I select the cape town one, I get a ping of around 70ms but a jitter of 80ms (its 1ms to the Durban server). Not sure if this could be part of the problem. Would that be a routing issue if is fine to Durban but so terrible to the Cape?

Here is a tracert to www.uct.ac.za if that will help in any way

1 <1 ms <1 ms <1 ms 10.0.0.2
2 35 ms 34 ms 35 ms ndn-ip-esr-3.east.dsl.telkomsa.net [105.224.12.1]
3 * * * Request timed out.
4 36 ms 35 ms 35 ms ipc-1-up.east.dsl.telkomsa.net [105.229.0.22]
5 187 ms 36 ms 36 ms ipc-aggr-2.east.dsl.telkomsa.net [105.229.0.13]
6 57 ms 86 ms 144 ms 105-187-252-46.ti-sen.telkomsa.net [105.187.252.46]
7 56 ms 56 ms 84 ms 105-187-252-46.ti-sen.telkomsa.net [105.187.252.46]
8 259 ms 58 ms 57 ms tenet.ixp.capetown [196.10.140.67]
9 58 ms 57 ms 76 ms te0-7-0-2-101-cpt2-pe2.tenet.ac.za [155.232.27.250]

Thanks very much for the help.

Edit : Jitter is now consistently around 150ms
 
Last edited:
underthefigtree said:
Good evening. Please can someone assist me. I am in northern KZN and currently playing CSGO on the official servers is almost impossible. I get a ping of around 300. When doing a speedtest on saix.net, i get decent numbers to the Durban server but when I select the cape town one, I get a ping of around 70ms but a jitter of 80ms (its 1ms to the Durban server). Not sure if this could be part of the problem. Would that be a routing issue if is fine to Durban but so terrible to the Cape?

Here is a tracert to www.uct.ac.za if that will help in any way

1 <1 ms <1 ms <1 ms 10.0.0.2
2 35 ms 34 ms 35 ms ndn-ip-esr-3.east.dsl.telkomsa.net [105.224.12.1]
3 * * * Request timed out.
4 36 ms 35 ms 35 ms ipc-1-up.east.dsl.telkomsa.net [105.229.0.22]
5 187 ms 36 ms 36 ms ipc-aggr-2.east.dsl.telkomsa.net [105.229.0.13]
6 57 ms 86 ms 144 ms 105-187-252-46.ti-sen.telkomsa.net [105.187.252.46]
7 56 ms 56 ms 84 ms 105-187-252-46.ti-sen.telkomsa.net [105.187.252.46]
8 259 ms 58 ms 57 ms tenet.ixp.capetown [196.10.140.67]
9 58 ms 57 ms 76 ms te0-7-0-2-101-cpt2-pe2.tenet.ac.za [155.232.27.250]

Thanks very much for the help.

Edit : Jitter is now consistently around 150ms
Click to expand...

The traceroute varies a lot, even on the same hop. I suspect your DSLAM's backhaul (still connected to an ESR,,so likely still ATM) was almost congesting at the time.

Next time you experience a problem, please test with mtr, winmtr or pingplotter. Unlike traceroute, these tools first determine the path, and then ping each hop multiple times simultaneously, so if some point in the path congests during your test, you can see exactly where.
 
Genisys said:
Ranger: any idea why a lot of traffic is Routing via Jhb>CPT>JHB? It seems to be a lot of services going this route. Host1plus, Mweb, etc seems to be taking that odd route.
Click to expand...
Can you provide some destinations (hostnames or IPs) that are affected?
 
ranger said:
Can you provide some destinations (hostnames or IPs) that are affected?
Click to expand...

Tracing route to 197-80-200-32.jhb.mweb.co.za [197.80.200.32]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.5.1
2 * * * Request timed out.
3 9 ms 8 ms 9 ms ipc-3-up.north.dsl.telkomsa.net [105.224.0.50]
4 9 ms 8 ms 9 ms ipc-aggr-1.north.telkomsa.net [105.224.0.13]
5 29 ms 29 ms 29 ms ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
6 29 ms 29 ms 28 ms ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
7 30 ms * 30 ms optinet.ixp.capetown [196.10.140.15]
8 30 ms 33 ms 34 ms bu-ether1.cpt-p-1.optinet.net [197.84.7.33]
9 29 ms 31 ms 30 ms te0-7-0-0.cpt-p-2.optinet.net [197.84.4.32]
10 31 ms 33 ms 30 ms tengig-0-7-0-1-vic-p-1.mweb.co.za [197.84.4.47]
11 30 ms 30 ms 31 ms 197-84-4-101.cpt.mweb.co.za [197.84.4.101]
12 33 ms 43 ms 51 ms 197-80-7-111.jhb.mweb.co.za [197.80.7.111]
13 29 ms 29 ms 29 ms bu-ether3.mca-pe-1.optinet.net [197.80.4.37]
14 28 ms 28 ms 28 ms 197-80-96-30.jhb.mweb.co.za [197.80.96.30]
15 29 ms 28 ms 28 ms 197-80-200-32.jhb.mweb.co.za [197.80.200.32]

Trace complete.
Click to expand...

Tracing route to 154.70.153.70 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.0.5.1
2 * * * Request timed out.
3 9 ms 8 ms 8 ms ipc-3-up.north.dsl.telkomsa.net [105.224.0.50]
4 8 ms 8 ms 8 ms ipc-aggr-1.north.telkomsa.net [105.224.0.13]
5 29 ms * 28 ms ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
6 28 ms 28 ms 28 ms ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
7 29 ms 29 ms 29 ms 196-10-140-126.ixp.capetown [196.10.140.126]
8 30 ms 30 ms 30 ms mi-za-cpt-p7-te0-0-0-0.ip.isnet.net [168.209.6.12]
9 28 ms 27 ms 28 ms 168.209.100.101
10 28 ms 28 ms 28 ms csw5-pkl-tg2-7.ip.isnet.net [168.209.1.188]
11 * * * Request timed out.
12 27 ms 27 ms 26 ms za-node3.host1plus.com [154.70.152.52]
13 27 ms 27 ms 27 ms 154.70.153.70

Trace complete.
Click to expand...

Tracing route to 197-80-200-32.jhb.mweb.co.za [197.80.200.32]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.5.1
2 * * * Request timed out.
3 9 ms 9 ms 8 ms ipc-3-up.north.dsl.telkomsa.net [105.224.0.50]
4 8 ms 8 ms 8 ms ipc-aggr-1.north.telkomsa.net [105.224.0.13]
5 29 ms 29 ms 29 ms ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
6 28 ms 29 ms 28 ms ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
7 31 ms 30 ms 30 ms optinet.ixp.capetown [196.10.140.15]
8 33 ms 33 ms 33 ms bu-ether1.cpt-p-1.optinet.net [197.84.7.33]
9 30 ms 30 ms 29 ms te0-7-0-0.cpt-p-2.optinet.net [197.84.4.32]
10 32 ms 29 ms 29 ms tengig-0-7-0-1-vic-p-1.mweb.co.za [197.84.4.47]
11 29 ms 29 ms 29 ms 197-84-4-101.cpt.mweb.co.za [197.84.4.101]
12 29 ms 28 ms 30 ms 197-80-7-111.jhb.mweb.co.za [197.80.7.111]
13 29 ms 29 ms 29 ms bu-ether3.mca-pe-1.optinet.net [197.80.4.37]
14 29 ms 29 ms 28 ms 197-80-96-30.jhb.mweb.co.za [197.80.96.30]
15 29 ms 29 ms 28 ms 197-80-200-32.jhb.mweb.co.za [197.80.200.32]

Trace complete.
Click to expand...

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.5.1
2 * * * Request timed out.
3 9 ms 8 ms 8 ms ipc-3-up.north.dsl.telkomsa.net [105.224.0.50]
4 8 ms 8 ms 12 ms ipc-aggr-1.north.telkomsa.net [105.224.0.13]
5 9 ms 9 ms 9 ms jb1-pr-02-te0-1-0.net.telkomsa.net [105.187.249.2]
6 9 ms 9 ms 10 ms jb1-google-gw.net.telkomsa.net [105.187.249.22]
7 9 ms 9 ms 9 ms 72.14.239.35
8 9 ms 9 ms 9 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.
Click to expand...

That is just a few tracert's to a few ip's. 8.8.8.8 is fine, the others however seem to be routing via JHB>CPT>JHB.
 
ranger said:
The traceroute varies a lot, even on the same hop. I suspect your DSLAM's backhaul (still connected to an ESR,,so likely still ATM) was almost congesting at the time.

Next time you experience a problem, please test with mtr, winmtr or pingplotter. Unlike traceroute, these tools first determine the path, and then ping each hop multiple times simultaneously, so if some point in the path congests during your test, you can see exactly where.
Click to expand...

Thanks very much ranger. Will use those tools if I experience those conditions again.

Please just two quick questions so I can understand the terminology. What does "still connected to an ESR,,so likely still ATM" mean?

And is DSLAM just used at my local exchange because the issue only ever effects me to CPT and not Durban so surely that would suggest the problem is not local? The jitter to Durban is always 1ms and to Cape Town is often over 100ms.

Thanks again for the help
 
i have had my line for a month couldn't have more than 200gb and i got a message this week from telkom ive been shaped now. im on an uncapped package and considered a 'power user'
 
csc003 said:
Thanks Mick. Ok its a 4mb line according to link im on 240 Gb for Nov 2016
Click to expand...
Assuming all your usage has been outside of "free" Night Surfer hours (00.00 - 07:00) that sounds about right for 4Mbps uncapped going by other MyBB members reports.

You could grab a capped axxess 20GB double data account for R46/mth for times like this (you currently get 40GB data on the promo and any unused rolls over to next month).
 
Can you take the Do Broadband Elite Package month to month or do you have to sign 24month contract?
 
MickZA said:
Pretty sure you can't, I'm on month to month 10Mbps uncapped @R999 excluding line rental and I provide my own router.
Click to expand...

Ok so after holding on forever.... telkom said you can take any Do Package month to month you just won't get the free router.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X