Telkom Internet Capped/Uncapped User Feedback (Pt2)

I am not aware of any issues at present. If you try a new session, is it better? If you try a traceroute anywhere (by IP, e.g. 8.8.8.8 or 105.225.0.1), how far do you get?
 
I am not aware of any issues at present. If you try a new session, is it better? If you try a traceroute anywhere (by IP, e.g. 8.8.8.8 or 105.225.0.1), how far do you get?

Just tried again and it's working fine. :)
 
again the difference to CT based anything is insane for me, i just cannot understand, granted i've never been the sharpest tool in the shed

first some Telkom tracerts, to first, a TeamSpeak server, and a CSGO server, both in CT

CSGO SERVER
1 2 ms 1 ms 1 ms 192.168.1.1
2 27 ms 26 ms 28 ms nngy-ip-bb-1.east.dsl.telkomsa.net [105.224.124.1]
3 689 ms 102 ms 397 ms 105.229.0.169
4 31 ms 28 ms 28 ms 105.229.0.170
5 30 ms 30 ms 32 ms 105.229.0.29
6 74 ms 73 ms 73 ms dbn-pr-02-be200-vl1.net.telkosma.net [105.229.0.33]
7 75 ms 75 ms 72 ms db1-pr-01.net.telkomsa.net [105.187.249.74]
8 74 ms 72 ms 70 ms optinet.db1.napafrica.net [196.10.141.75]
9 47 ms 43 ms 49 ms 197-82-7-1.dbn.mweb.co.za [197.82.7.1]
10 89 ms 88 ms * te0-7-0-1.vic-p-2.optinet.net [197.84.4.44]
11 43 ms 43 ms 43 ms 197-80-7-111.jhb.mweb.co.za [197.80.7.111]
12 44 ms 43 ms 42 ms bu-ether3.mca-pe-1.optinet.net [197.80.4.37]
13 42 ms 41 ms 43 ms 197-80-96-30.jhb.mweb.co.za [197.80.96.30]
14 87 ms 86 ms 86 ms 197-80-200-52.jhb.mweb.co.za [197.80.200.52]

Teamspeak
1 <1 ms 1 ms 1 ms 192.168.1.1
2 27 ms 27 ms 28 ms nngy-ip-bb-1.east.dsl.telkomsa.net [105.224.124.1]
3 * * * Request timed out.
4 29 ms 29 ms 28 ms 105.229.0.170
5 30 ms 29 ms 29 ms ipc-aggr-1.east.dsl.telkomsa.net [105.229.0.29]
6 93 ms 86 ms 90 ms ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
7 97 ms 97 ms 95 ms ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
8 95 ms 96 ms 94 ms optinet.ct1.napafrica.net [196.10.140.15]
9 98 ms 98 ms 95 ms te0-0-0-1.cpt-p-2.optinet.net [197.84.7.34]
10 86 ms 90 ms 91 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
11 90 ms 92 ms 96 ms 196.28.178.66
12 97 ms 96 ms 97 ms 196.41.133.234
13 98 ms 101 ms 100 ms 152.111.192.232

now, switch over to a different ISP and .....
CSGO SERVER
1 1 ms 1 ms 1 ms 192.168.1.1
2 28 ms 27 ms 27 ms 196-210-157-1.dynamic.isadsl.co.za [196.210.157.1]
3 31 ms 31 ms 32 ms cdsl3-umh-gi0-0-0-3102.ip.isnet.net [196.38.74.245]
4 30 ms 31 ms 31 ms 196.26.210.212
5 31 ms 34 ms 30 ms mi-za-umh-p7-ten-0-0-0-1.ip.isnet.net [168.209.93.203]
6 31 ms 29 ms 30 ms mi-za-umh-p8-ten-0-0-1-1.ip.isnet.net [168.209.93.204]
7 56 ms 56 ms 55 ms mi-za-cpt-p7-ten-0-0-1-1-147.ip.isnet.net [168.209.0.25]
8 55 ms 56 ms 57 ms 168.209.2.131
9 54 ms 55 ms 55 ms mweb.cinx.net.za [196.223.22.32]
10 63 ms 63 ms 63 ms te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2]
11 65 ms 64 ms 62 ms tengig-0-7-0-1-vic-p-1.mweb.co.za [197.84.4.47]
12 63 ms 63 ms 61 ms 101.bu-ether5.vic-pe-1.optinet.net [197.80.7.9]
13 65 ms 63 ms 62 ms bu-ether3.mca-pe-1.optinet.net [197.80.4.37]
14 61 ms 61 ms 61 ms 197-80-96-30.jhb.mweb.co.za [197.80.96.30]
15 62 ms 62 ms 61 ms 197-80-200-52.jhb.mweb.co.za [197.80.200.52]

Teamspeak
1 <1 ms 1 ms 1 ms 192.168.1.1
2 26 ms 27 ms 26 ms 196-210-157-1.dynamic.isadsl.co.za [196.210.157.1]
3 31 ms 30 ms 30 ms cdsl3-umh-gi0-0-0-3102.ip.isnet.net [196.38.74.245]
4 30 ms 31 ms 31 ms 196.26.210.212
5 30 ms 31 ms 29 ms mi-za-umh-p7-ten-0-0-0-1.ip.isnet.net [168.209.93.203]
6 31 ms 30 ms 29 ms mi-za-umh-p8-ten-0-0-1-1.ip.isnet.net [168.209.93.204]
7 55 ms 56 ms 57 ms mi-za-cpt-p7-ten-0-0-1-1-147.ip.isnet.net [168.209.0.25]
8 54 ms 56 ms 56 ms 168.209.6.131
9 56 ms 55 ms 55 ms mweb.cinx.net.za [196.223.22.32]
10 60 ms 59 ms 59 ms te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2]
11 60 ms 56 ms 55 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
12 56 ms 55 ms 55 ms 196.28.178.66
13 56 ms 55 ms 56 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
14 55 ms 54 ms 56 ms 152.111.192.232


20ms doesnt seem like much, but in gaming terms its HUGE, especially when vs okes rolling with < 10

what do i need to do?

any advice would be AWESOME, all i want is a good low latency experience in gaming, will switching to capped make a difference?

PS, as a side note is the (2 27 ms 26 ms 28 ms nngy-ip-bb-1.east.dsl.telkomsa.net [105.224.124.1]) ASSIA giving me 27ms from the get go?
 
assia dsm interleave?

I don't get the same results as you but i'm not on assia dsm.
 
feel so lost at what to do, all i know is telkom sponsors the largest South African gaming league, but yet for the most part I cannot even play a match without having a time out, or calling for a substitute.

just want a good online experience is that so much to ask for?

assia dsm interleave?

I don't get the same results as you but i'm not on assia dsm.
 
Have you tried MTR or WIN MTR tests?

I presume you are completely sure that your line is okay? What SNR results do you have available?
 
Problem's back:
5321339727.png


So here's your winmtr:
Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                                  router -    0 |   22 |   22 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|         ipc-3-up.north.dsl.telkomsa.net -   17 |   12 |   10 |   10 |   34 |   74 |   24 |
|                           105.224.0.130 -    0 |   22 |   22 |   11 |   29 |   98 |   24 |
|           ipc-aggr-1.north.telkomsa.net -    0 |   22 |   22 |   14 |   34 |  100 |   31 |
|    cen-pr-02-be200-vl1.net.telkomsa.net -    0 |   22 |   22 |    9 |   31 |  102 |   22 |
|   rrba-ip-hsll-2-wan.telkom-ipnet.co.za -    0 |   22 |   22 |   13 |   31 |  103 |   27 |
|                             196.43.9.86 -    6 |   18 |   17 |  173 |  198 |  267 |  173 |
|                   ldn-b5-link.telia.net -    0 |   21 |   21 |  197 |  215 |  274 |  230 |
|                  ldn-bb3-link.telia.net -    0 |   22 |   22 |  189 |  206 |  275 |  200 |
|                  ash-bb3-link.telia.net -    0 |   21 |   21 |  265 |  288 |  354 |  296 |
|                   ash-b1-link.telia.net -    0 |   21 |   21 |  260 |  279 |  350 |  265 |
|    vadata-ic-157231-ash-bb1.c.telia.net -    0 |   21 |   21 |  263 |  283 |  347 |  266 |
|                           54.239.109.18 -    0 |   16 |   16 |  282 |  606 | 2508 |  298 |
|                           54.239.109.41 -    6 |   18 |   17 |  260 |  287 |  331 |  260 |
|                         205.251.245.172 -    0 |   21 |   21 |  266 |  288 |  350 |  303 |
|                   No response from host -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
 
Not really sure how it could even be a line fault, unless i use a different line when switching to a alternate ISP

last night played two competitive matches, first game on Telkoom ISP, my ping was 100ms and spiked to 180ms+ at times

switched to a free 1gb from a alt ISP and low and behold the second game i could actually kill people because my ping was 49ms

so ye line fault, I highly doubt that.

however, not sure what the state is of the KLOOF (NKLO) Exchange that I am connected to

as a side note, is setting up the PRIORITISATION tab a must or could it not be something that simple

Have you tried MTR or WIN MTR tests?

I presume you are completely sure that your line is okay? What SNR results do you have available?
 
Last edited:
Have been having authentication issues with my Telkom account for the last hour or two. Not sure if it is just related to my exchange, but switched to AH and all is up and running again. Just a heads up.
 
So do you have to wait for a Telkom technician to come install the antenna or can we do it by yourself ..
 
weekend was 100% for me, last night not so much, will check it out tonight again, if this is a week problem could it point to exchange congestion or my 2mb uncapped that is affected in the week due to policies?
 
Problem's back:
5321339727.png


So here's your winmtr:
Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                                  router -    0 |   22 |   22 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|         ipc-3-up.north.dsl.telkomsa.net -   17 |   12 |   10 |   10 |   34 |   74 |   24 |
|                           105.224.0.130 -    0 |   22 |   22 |   11 |   29 |   98 |   24 |
|           ipc-aggr-1.north.telkomsa.net -    0 |   22 |   22 |   14 |   34 |  100 |   31 |
|    cen-pr-02-be200-vl1.net.telkomsa.net -    0 |   22 |   22 |    9 |   31 |  102 |   22 |
|   rrba-ip-hsll-2-wan.telkom-ipnet.co.za -    0 |   22 |   22 |   13 |   31 |  103 |   27 |
|                             196.43.9.86 -    6 |   18 |   17 |  173 |  198 |  267 |  173 |
|                   ldn-b5-link.telia.net -    0 |   21 |   21 |  197 |  215 |  274 |  230 |
|                  ldn-bb3-link.telia.net -    0 |   22 |   22 |  189 |  206 |  275 |  200 |
|                  ash-bb3-link.telia.net -    0 |   21 |   21 |  265 |  288 |  354 |  296 |
|                   ash-b1-link.telia.net -    0 |   21 |   21 |  260 |  279 |  350 |  265 |
|    vadata-ic-157231-ash-bb1.c.telia.net -    0 |   21 |   21 |  263 |  283 |  347 |  266 |
|                           54.239.109.18 -    0 |   16 |   16 |  282 |  606 | 2508 |  298 |
|                           54.239.109.41 -    6 |   18 |   17 |  260 |  287 |  331 |  260 |
|                         205.251.245.172 -    0 |   21 |   21 |  266 |  288 |  350 |  303 |
|                   No response from host -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |    4 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Why do you think this is not adequate (hint: we don't know what speed service you have).

300ms to the U.S. is normal. Latency had an impact on throughput of TCP connections. So if you're on 2Mbps, this wouldn't be an unexpected result.
 
@ranger last night my ping was stupid again, so currently thinking my exchange could be the problem but I'm not 100% sure and would appreciate any sort of advice on this one, as gaming in the DGL is rather annoying if one suffers from high ping.

original post : http://mybroadband.co.za/vb/showthread.php/596707-Telkom-Internet-Uncapped-User-Feedback-%28Pt2%29?p=17581306&viewfull=1#post17581306

Then weekend ping was low, my 2mb line was syncing at 2.5mb, was reset to 2mb on friday, noticed yesterday that is was back to 2.5mb again, could this be the issue of it or is it my 2mb uncapped package that is being affected in the week?

I'm really getting frustrated and not sure what action to take or how to fix, would just like to have a decent ping when i game.

got sent a ticket on monday - 27CNK160516

would appreciate any advice or feedback :D
 
Top
Sign up to the MyBroadband newsletter
X