Telkom Internet Capped/Uncapped User Feedback (Pt2)

Having trouble with international speeds:
speedof.me_14-12-08.jpg

@ranger - you mentioned that Ookla's MyBB speedtests are not accurate and that I should use alternative speedstest, so here goes.
Same results on "test my net" and Ookla speedtest.net
This is currently a recurring problem for what seems to be affecting not only my connection - international is problematic this month.
Any feedback/update/explanation?

Local speeds = normal.
 
Meh, after a few weeks of everything being fine, I'm now back to same old story, local fine, international buggered

http://speedtest.ookla.com/result/2777878943.png
http://speedtest.ookla.com/result/2777879650.png

Edit: same on other test sites
http://testmy.net/yHlcsQP.5smWiGN.png

Same as a while ago, tracers all fine, pings all fine, just bloody slow international speed, gaming is impossible

Traceroute has started…

traceroute: Warning: bbc.co.uk has multiple addresses; using 212.58.244.18
traceroute to bbc.co.uk (212.58.244.18), 64 hops max, 72 byte packets
1 10.0.0.2 (10.0.0.2) 1.257 ms 0.698 ms 0.693 ms
2 rrba-ip-bng-1.north.dsl.telkomsa.net (105.224.208.1) 10.020 ms 12.721 ms 9.726 ms
3 ipc-1-up.north.dsl.telkomsa.net (105.224.0.6) 13.734 ms 12.832 ms 12.928 ms
4 ipc-aggr-1.north.telkomsa.net (105.224.0.13) 12.390 ms 11.555 ms 12.305 ms
5 165.165.216.221 (165.165.216.221) 12.174 ms 12.298 ms 13.211 ms
6 lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za (196.43.9.46) 198.809 ms 198.779 ms 198.638 ms
7 xe-0-1-0-19.r00.londen10.uk.bb.gin.ntt.net (83.231.146.245) 191.398 ms 189.851 ms 189.904 ms
8 ae-6.r22.londen03.uk.bb.gin.ntt.net (129.250.4.20) 203.917 ms 198.949 ms 200.867 ms
9 bbc-linx.pr01.thdow.bbc.co.uk (195.66.224.103) 192.459 ms 190.214 ms 191.533 ms
10 * * *
11 * * *
12 ae0.er01.telhc.bbc.co.uk (132.185.254.109) 201.281 ms 197.275 ms 197.798 ms
13 132.185.255.149 (132.185.255.149) 190.731 ms 190.541 ms 189.580 ms
14 fmt-vip72.telhc.bbc.co.uk (212.58.244.18) 200.733 ms 199.738 ms 200.117 ms
 
Last edited:
Besides the off slow downs that get posted here, how is the Telkom Uncapped offering otherwise?
 
Was better this morning.

Right now, not quite... on 4mb line:
2778426391.png
 
bwana said:
Didn't have an opportunity to check this morning but Hulu is streaming okay'ish this afternoon.
Click to expand...

My issue is with youtube, vimeo seems fine. Have not tried hulu or other sites. When you open youtube it defaults to 240p and still splutters.
 
shanezn said:
Same on my side. Been having issues since Sunday night with YouTube.
Speeds have been pretty erratic as well.
Click to expand...

Maybe I should wait with getting my 20mb telkom internet fiber for R999 and stick with my alternate ISP 4mb adsl?
 
anyone having issues with TI in the North of Guateng. see my tracert below and ping to telkom.co.za

Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 10.0.0.2
2 1456 ms 1460 ms 1676 ms 105.224.40.1
3 1545 ms 1373 ms 1441 ms ipc-1-up.north.dsl.telkomsa.net [105.224.0.6]
4 1390 ms 1346 ms 1374 ms ipc-aggr-1.north.telkomsa.net [105.224.0.13]
5 1395 ms 1562 ms 1962 ms 196.25.166.217
6 1485 ms 1639 ms 1502 ms 196.43.39.162
7 1425 ms 1552 ms 1492 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
8 1387 ms 1371 ms 1378 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.30]
9 1407 ms 1350 ms 178 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.


Pinging telkom.co.za [196.43.22.222] with 32 bytes of
Reply from 196.43.22.222: bytes=32 time=1455ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1527ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1476ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1488ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1482ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1415ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1389ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1392ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1433ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1414ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1395ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1382ms TTL=246
Request timed out.
Reply from 196.43.22.222: bytes=32 time=1440ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1382ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1376ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1436ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1438ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1505ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1674ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1547ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1517ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1552ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1511ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1483ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1485ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1534ms TTL=246
Request timed out.
Reply from 196.43.22.222: bytes=32 time=1776ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1504ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1310ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1354ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1380ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1388ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1420ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1359ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1428ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1512ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1479ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1670ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1868ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1545ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1792ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1670ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1529ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1635ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1552ms TTL=246
Reply from 196.43.22.222: bytes=32 time=1451ms TTL=246
 
You, sir, are not alone. Speeds and pings were fine during the daylight hours of today, and now this:

Tracing route to google.co.za [74.125.233.3]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 118 ms 114 ms 114 ms 105-224-40-1.north.dsl.telkomsa.net [105.224.40.
1]
3 117 ms 117 ms 114 ms ipc-1-up.north.dsl.telkomsa.net [105.224.0.6]
4 112 ms 108 ms 107 ms ipc-aggr-1.north.telkomsa.net [105.224.0.13]
5 161 ms 110 ms 111 ms jb1-pr-01-te8-3.net.telkomsa.net [105.187.249.2]

6 126 ms 126 ms 126 ms jb1-google-gw.net.telkomsa.net [105.187.249.22]

7 114 ms 114 ms 109 ms 72.14.237.239
8 117 ms 124 ms 140 ms jnb01s07-in-f3.1e100.net [74.125.233.3]

Trace complete.

Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 76 ms 77 ms 73 ms 105-224-40-1.north.dsl.telkomsa.net [105.224.40.
1]
3 72 ms 81 ms 81 ms ipc-1-up.north.dsl.telkomsa.net [105.224.0.6]
4 82 ms 81 ms 86 ms ipc-aggr-1.north.telkomsa.net [105.224.0.13]
5 87 ms 90 ms 87 ms 165.165.216.221
6 80 ms 81 ms 80 ms 196.43.39.162
7 88 ms 92 ms 93 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
8 96 ms 101 ms 101 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.34]
9 172 ms 100 ms 99 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.

Not as bad as yours, but it hampers the service speeds.
 
Pings seem to have improved now as the network quietens down (maybe?).

Tracing route to google.co.za [74.125.233.3]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 31 ms 35 ms 32 ms 105-224-40-1.north.dsl.telkomsa.net [105.224.40.
1]
3 31 ms 31 ms 32 ms ipc-1-up.north.dsl.telkomsa.net [105.224.0.6]
4 43 ms 41 ms 42 ms ipc-aggr-1.north.telkomsa.net [105.224.0.13]
5 34 ms 33 ms 33 ms jb1-pr-01-te8-3.net.telkomsa.net [105.187.249.2]

6 39 ms 41 ms 42 ms jb1-google-gw.net.telkomsa.net [105.187.249.22]

7 53 ms 52 ms 50 ms 72.14.237.239
8 56 ms 58 ms 55 ms jnb01s07-in-f3.1e100.net [74.125.233.3]

Trace complete.
 
Well I've decided enough is enough. This uncapped story is just not working for me. Having tested over the last few months with TI uncapped 4 mb, six different TI capped accounts, and an Afrihost capped account all on my 10 mb line, I've come to the conclusion that TI just isn't cutting the mustard any more.

Whenever things get flaky on a TI account, which is most of the time lately, capped or uncapped, I switch to Afrihost and everything is fine. I keep getting page load timeouts, youtube buffering, slow nntp - yeah, yeah, we've all heard it all before.

I sat on the phone yesterday to 10210 for an hour waiting before I hung up. Trying again today. I'll just keep paying for my line with Telkom, but Afrihost will be my primary ISP from now on. Their issues seem to be sorted, for me at any rate.

The only thing I was worried about was the performance of their free news server, but having pulled half a dozen files from them in the last couple of days and having them come in at 1 Mb per second I'm converted.

Bye Bye TI, it was nice while it lasted.

/unsubscribes from this thread.
 
Grouter said:
Well I've decided enough is enough. This uncapped story is just not working for me. Having tested over the last few months with TI uncapped 4 mb, six different TI capped accounts, and an Afrihost capped account all on my 10 mb line, I've come to the conclusion that TI just isn't cutting the mustard any more.

Whenever things get flaky on a TI account, which is most of the time lately, capped or uncapped, I switch to Afrihost and everything is fine. I keep getting page load timeouts, youtube buffering, slow nntp - yeah, yeah, we've all heard it all before.

I sat on the phone yesterday to 10210 for an hour waiting before I hung up. Trying again today. I'll just keep paying for my line with Telkom, but Afrihost will be my primary ISP from now on. Their issues seem to be sorted, for me at any rate.

The only thing I was worried about was the performance of their free news server, but having pulled half a dozen files from them in the last couple of days and having them come in at 1 Mb per second I'm converted.

Bye Bye TI, it was nice while it lasted.

/unsubscribes from this thread.
Click to expand...

Well, considering that the experience on TI is more often like below, who can blame you?

speedof.me_14-12-10.jpg

TI? Ranger? Anyone?

*digging through cupboard for 56kbps US Robotics dial-up modem*
 
Has anyone experienced billing issues for the December billing run? My monthly bill is usually about R805 and then I get about R150 in discount on that so R650 per month. I am currently in my last month on contract with them and they hit me with a R 1191.08 bill??? No discount applied and they did not send me a detailed bill to show me what is what. I have a 20 mb line and 4 meg uncapped account (I have my reasons) so no way should it cost this must? I also do not have a phone to make phone calls on the line.

To add insult to injury, I cant get through to their call centre. Sorry we are experiencing high call volumes. No queue, just sorry here is your balance now go pay it? Never had an issue and now in my last month I get this.
 
Everything is just timing out this morning, had to switch over to my backup account
 
Server Not Found and Slow To Load

Is there a problem with TI the last couple of days? Half the sites I try to load come back with a "Server not found" error in the browser - local and international sites like MSN, Mozilla, DSTV are just a few. When I reset the router, the pages load. Browsing is also very slow. Speedtest shows everything's fine, but it takes 30 seconds to load a page on a lot of sites that usually load quickly. Am on 2mb uncapped.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X