Telkom Internet Capped/Uncapped User Feedback (Pt2)

Indian said:
Thanks for info!
I don't download much using Night Surfer. I generally get throttled at 85-90 GB per month. So, will hope for upgrade to 4 mbps or will have to use another ISP which gives at least 150-175 GB.
Click to expand...

Hope for? I don't see TI doing free speed bumps again anytime soon (within say the next 5 years) so you'll be in trouble if you hold your breath.
 
I've heard different things, so just to clear it up, if i cancel today when will the account stop working?
 
SCHUMI-4-EVA said:
Hope for? I don't see TI doing free speed bumps again anytime soon (within say the next 5 years) so you'll be in trouble if you hold your breath.
Click to expand...

Remember my friend
Hope is a good thing! May be best of things!

Jokes apart, thanks for advice. I am going to shop around then for Data
 
Hi ranger.

Please can you help. The problem that existed about two weeks ago between DBN and CPT seems to be back sadly.

1 <1 ms <1 ms <1 ms 10.0.0.2
2 31 ms 30 ms 30 ms ndn-ip-esr-3.east.dsl.telkomsa.net [105.224.12.1]
3 38 ms 40 ms 44 ms ipc-1-up.east.dsl.telkomsa.net [105.229.0.6]
4 47 ms 33 ms 32 ms ipc-aggr-2.east.dsl.telkomsa.net [105.229.0.13]
5 462 ms 444 ms 452 ms ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
6 441 ms 455 ms 487 ms ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
7 500 ms 521 ms 522 ms optinet.ct1.napafrica.net [196.10.140.15]
8 * 500 ms 559 ms bu-ether1.cpt-p-1.optinet.net [197.84.7.33]
9 475 ms 463 ms 476 ms vl12.cpt-hscore-2.optinet.net [197.84.5.254]
10 436 ms 431 ms 512 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
11 520 ms 509 ms * 197-85-139-78.cpt.mweb.co.za [197.85.139.78]
12 447 ms 488 ms 441 ms intoxicated.co.za [197.85.190.43]

Again it seems to be ct1-pr-01-te0-0-0.net.telkomsa.net at fault.

Another problem i have experienced is that in the two weeks where the problem was gone, i got a consistant 10 -15% packet loss to all the CPT gaming servers. My ping was fine but the packet loss was terrible. This packet loss was also related to my ISP as it dissipeared on different accounts.

Thanks very much for your help.
 
Also having issues tonight:
Tracing route to wbs-ip-dlr-1-1.telkom-ipnet.co.za [196.25.37.14]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms home.gateway [10.0.0.2]
2 15 ms 10 ms 10 ms wblv-ip-esr-3.south.dsl.telkomsa.net [105.224.80
.1]
3 114 ms 108 ms 103 ms ipc-1-up.south.dsl.telkomsa.net [105.226.0.6]
4 92 ms 97 ms 99 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13]

5 100 ms 98 ms 97 ms 196.25.103.93
6 559 ms 538 ms 542 ms wbs-ip-hsll-1-gig-2-1-0.telkom-ipnet.co.za [196.
43.52.62]
7 599 ms 595 ms 588 ms wbs-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za [
196.25.37.2]
8 533 ms 522 ms 508 ms wbs-ip-dlr-1-1.telkom-ipnet.co.za [196.25.37.14]


Trace complete.
Click to expand...

International also looking dismal:
Tracing route to bbc.co.uk [212.58.246.103]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway [10.0.0.2]
2 10 ms 10 ms 8 ms wblv-ip-esr-3.south.dsl.telkomsa.net [105.224.80
.1]
3 110 ms 111 ms 106 ms ipc-1-up.south.dsl.telkomsa.net [105.226.0.6]
4 98 ms 94 ms 93 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13]

5 102 ms 105 ms 104 ms 196.25.103.93
6 689 ms 713 ms 717 ms lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.
43.9.58]
7 878 ms 876 ms 863 ms ldn-b5-link.telia.net [62.115.35.89]
8 820 ms 812 ms 802 ms atos-ic-151907-ldn-b5.c.telia.net [80.239.132.14
2]
9 * * * Request timed out.
10 * * * Request timed out.
11 726 ms 719 ms 723 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
12 888 ms 899 ms 901 ms 132.185.255.165
13 876 ms 851 ms 816 ms fmt-vip132.cwwtf.bbc.co.uk [212.58.246.103]

Trace complete.
Click to expand...
 
Last edited:
Also having issues. International is down for me.

Only website that is working is bing and MSN.

It is like a blast back to the past when there was separate internets for local and international.
 
We were able to increase capacity for the Southern users. Hope your experience is more to your liking tonight
 
streaker said:
We were able to increase capacity for the Southern users. Hope your experience is more to your liking tonight
Click to expand...

Thanks but it does not help for the latency issues experienced on TI. ct1-pr-01-te0-0-0.net.telkomsa.net (105.187.249.138) is still a major issue and nothing is being done about it unfortunately.

Code: 
traceroute to 152.111.192.244 (152.111.192.244), 30 hops max, 60 byte packets
 1  gateway (10.0.0.2)  1.481 ms  2.074 ms  2.574 ms
 2  * * *
 3  ipc-1-up.east.dsl.telkomsa.net (105.229.0.21)  69.143 ms  69.936 ms  70.906 ms
 4  ipc-1-up.east.dsl.telkomsa.net (105.229.0.22)  71.374 ms  71.783 ms  72.727 ms
 5  * ipc-aggr-2.east.dsl.telkomsa.net (105.229.0.13)  76.157 ms  78.179 ms
 6  dbn-pr-01-be200-vl1.net.telkosma.net (105.229.0.34)  81.316 ms  56.748 ms  58.987 ms
 7  ct1-pr-01-te0-0-0.net.telkomsa.net (105.187.249.138)  351.999 ms  354.440 ms  356.738 ms
 8  ct1-pr-01-te0-0-0.net.telkomsa.net (105.187.249.138)  359.852 ms  362.121 ms  362.792 ms
 9  optinet.ct1.napafrica.net (196.10.140.145)  464.006 ms  464.763 ms *
10  te0-7-0-3.cpt-p-2.optinet.net (197.84.7.2)  374.048 ms bu-ether1.cpt-p-1.optinet.net (197.84.7.33)  348.906 ms te0-7-0-3.cpt-p-2.optinet.net (197.84.7.2)  341.460 ms
11  vl12.cpt-hscore-2.optinet.net (197.84.5.254)  341.784 ms vl11.cpt-hscore-1.optinet.net (197.84.5.238)  441.907 ms  442.100 ms
12  vp-02-14.bb.ctn.c27.za.net (196.28.178.70)  347.567 ms 196.28.178.66 (196.28.178.66)  445.310 ms vp-02-14.bb.ctn.c27.za.net (196.28.178.70)  347.831 ms
13  196.41.144.34 (196.41.144.34)  445.173 ms  440.557 ms gig5-1-cpt-opt-65-1.optinet.net (196.41.133.234)  346.449 ms
14  * gig5-1-cpt-opt-65-1.optinet.net (196.41.133.234)  351.228 ms *
 
ponder said:
Thanks but it does not help for the latency issues experienced on TI. ct1-pr-01-te0-0-0.net.telkomsa.net (105.187.249.138) is still a major issue and nothing is being done about it unfortunately.

Code: 
traceroute to 152.111.192.244 (152.111.192.244), 30 hops max, 60 byte packets
 1  gateway (10.0.0.2)  1.481 ms  2.074 ms  2.574 ms
 2  * * *
 3  ipc-1-up.east.dsl.telkomsa.net (105.229.0.21)  69.143 ms  69.936 ms  70.906 ms
 4  ipc-1-up.east.dsl.telkomsa.net (105.229.0.22)  71.374 ms  71.783 ms  72.727 ms
 5  * ipc-aggr-2.east.dsl.telkomsa.net (105.229.0.13)  76.157 ms  78.179 ms
 6  dbn-pr-01-be200-vl1.net.telkosma.net (105.229.0.34)  81.316 ms  56.748 ms  58.987 ms
 7  ct1-pr-01-te0-0-0.net.telkomsa.net (105.187.249.138)  351.999 ms  354.440 ms  356.738 ms
 8  ct1-pr-01-te0-0-0.net.telkomsa.net (105.187.249.138)  359.852 ms  362.121 ms  362.792 ms
 9  optinet.ct1.napafrica.net (196.10.140.145)  464.006 ms  464.763 ms *
10  te0-7-0-3.cpt-p-2.optinet.net (197.84.7.2)  374.048 ms bu-ether1.cpt-p-1.optinet.net (197.84.7.33)  348.906 ms te0-7-0-3.cpt-p-2.optinet.net (197.84.7.2)  341.460 ms
11  vl12.cpt-hscore-2.optinet.net (197.84.5.254)  341.784 ms vl11.cpt-hscore-1.optinet.net (197.84.5.238)  441.907 ms  442.100 ms
12  vp-02-14.bb.ctn.c27.za.net (196.28.178.70)  347.567 ms 196.28.178.66 (196.28.178.66)  445.310 ms vp-02-14.bb.ctn.c27.za.net (196.28.178.70)  347.831 ms
13  196.41.144.34 (196.41.144.34)  445.173 ms  440.557 ms gig5-1-cpt-opt-65-1.optinet.net (196.41.133.234)  346.449 ms
14  * gig5-1-cpt-opt-65-1.optinet.net (196.41.133.234)  351.228 ms *
Click to expand...


I need your source address to investigate this. Please reply here or PM me. Looks like an issue with the return path.
 
WHAT improvement ???????? :mad:


tracert capetown.spdtst.saix.net

Tracing route to wbs-ip-dlr-1-1.telkom-ipnet.co.za [196.25.37.14] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 27 ms 26 ms 28 ms wbs-ip-hsll-2-gi4-0-0-vl102.telkom-ipnet.co.za [105.226.0.21]
4 35 ms 33 ms 33 ms ipc-4-up.south.dsl.telkomsa.net [105.226.0.30]
5 167 ms 170 ms 167 ms ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57]
6 148 ms 146 ms 145 ms 165.165.214.213
7 142 ms 153 ms 154 ms 196.43.51.26
8 26 ms 27 ms 27 ms wbs-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za [196.25.37.2]
9 27 ms 27 ms 27 ms wbs-ip-dlr-1-1.telkom-ipnet.co.za [196.25.37.14]

Trace complete.
 
traceroute to wbs-ip-dlr-1-1.telkom-ipnet.co.za (196.25.37.14), 64 hops max, 72 byte packets
1 192.168.1.1 (192.168.1.1) 2.597 ms 1.257 ms 3.084 ms
2 * * *
3 wbs-ip-hsll-2-gi3-1-0-vl102.telkom-ipnet.co.za (105.226.0.29) 151.828 ms 190.985 ms 148.448 ms
4 ipc-4-up.south.dsl.telkomsa.net (105.226.0.30) 147.404 ms 147.205 ms 141.032 ms
5 ipc-aggr-1.south.dsl.telkomsa.net (105.226.0.13) 185.910 ms 187.222 ms 197.456 ms
6 wbs-ip-ll-1-wan.telkom-ipnet.co.za (165.165.221.153) 20.456 ms 19.367 ms 20.110 ms
7 wbs-ip-hsll-1-gig-2-1-0.telkom-ipnet.co.za (196.43.52.62) 47.011 ms 19.841 ms 19.759 ms
8 wbs-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za (196.25.37.2) 27.203 ms 27.902 ms 43.159 ms
9 capetown.spdtst.saix.net (196.25.37.14) 20.809 ms 20.109 ms 22.576 ms
 
I had no improvement in Dota 2 tonight, I once again had to switch to my backup WebAfrica account to play with low ping.
 
bwana said:
traceroute to wbs-ip-dlr-1-1.telkom-ipnet.co.za (196.25.37.14), 64 hops max, 72 byte packets
1 192.168.1.1 (192.168.1.1) 2.597 ms 1.257 ms 3.084 ms
2 * * *
3 wbs-ip-hsll-2-gi3-1-0-vl102.telkom-ipnet.co.za (105.226.0.29) 151.828 ms 190.985 ms 148.448 ms
4 ipc-4-up.south.dsl.telkomsa.net (105.226.0.30) 147.404 ms 147.205 ms 141.032 ms
5 ipc-aggr-1.south.dsl.telkomsa.net (105.226.0.13) 185.910 ms 187.222 ms 197.456 ms
6 wbs-ip-ll-1-wan.telkom-ipnet.co.za (165.165.221.153) 20.456 ms 19.367 ms 20.110 ms
7 wbs-ip-hsll-1-gig-2-1-0.telkom-ipnet.co.za (196.43.52.62) 47.011 ms 19.841 ms 19.759 ms
8 wbs-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za (196.25.37.2) 27.203 ms 27.902 ms 43.159 ms
9 capetown.spdtst.saix.net (196.25.37.14) 20.809 ms 20.109 ms 22.576 ms
Click to expand...

Bwana,

The response times increase on hop 3, before it enters Telkom Internet.

3 wbs-ip-hsll-2-gi3-1-0-vl102.telkom-ipnet.co.za (105.226.0.29) 151.828 ms 190.985 ms 148.448 ms

Seems like congestion on the backhaul
 
Big Bean said:
I had no improvement in Dota 2 tonight, I once again had to switch to my backup WebAfrica account to play with low ping.
Click to expand...

Big Bean,

Give me a source and destination address. Will have a look if something can be done about it.
 
streaker said:
I need your source address to investigate this. Please reply here or PM me. Looks like an issue with the return path.
Click to expand...

Thanks PM sent.

This issue has been around for a while now with people all over the show being affected by it.
 
streaker said:
Bwana,

The response times increase on hop 3, before it enters Telkom Internet.

3 wbs-ip-hsll-2-gi3-1-0-vl102.telkom-ipnet.co.za (105.226.0.29) 151.828 ms 190.985 ms 148.448 ms

Seems like congestion on the backhaul
Click to expand...

That is what YOU need to address with OpenServe, not us.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X