Telkom Internet Uncapped User Feedback.

Status
Not open for further replies.
Gboss said:
For a while yesterday I was beginning to believe that Ti was now going through the "slow down" that OW and AH clients are complaining about.
Click to expand...
I had problems with BBC iPlayer Radio 4 yesterday between 16:00 - 18:30 which is very unusual, buffering every 2mins or so even on low bandwidth.

Pinging bbc.co.uk was normal at around 185ms and switching to a TI capped account made no difference, just one of those things I guess.
 
Something isn't right here in Lichtenburg, I have increased latency on all accounts (tested yesterday with a telkom test account) and all seem to give me local latency of 55+ ms no matter which ISP or account. I had latency of 24 ms in the past and now it's all terrible, everything buffers, the speed stay the same just the latency went up. What can cause this phenomena?
 
elriconess said:
Something isn't right here in Lichtenburg, I have increased latency on all accounts (tested yesterday with a telkom test account) and all seem to give me local latency of 55+ ms no matter which ISP or account. I had latency of 24 ms in the past and now it's all terrible, everything buffers, the speed stay the same just the latency went up. What can cause this phenomena?
Click to expand...

Have you done a tracert to a local site as well as an iternational site?
 
Gboss said:
Have you done a tracert to a local site as well as an iternational site?
Click to expand...

International:

Tracing route to www.bbc.net.uk [212.58.244.66]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 10.0.0.2
2 17 ms 17 ms 17 ms 105-236-9-129-esr-lo.mtnbusiness.co.za [105.236.
9.129]
3 36 ms 35 ms 35 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178
.77]
4 27 ms 25 ms 25 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
5 36 ms 36 ms 35 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 24 ms 21 ms 23 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 207 ms 205 ms 205 ms bbc-linx.pr01.thdow.bbc.co.uk [195.66.224.103]
8 * * * Request timed out.
9 * * * Request timed out.
10 193 ms 192 ms 192 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
11 214 ms 214 ms 216 ms 132.185.255.149
12 201 ms 203 ms 201 ms bbc-vip111.telhc.bbc.co.uk [212.58.244.66]

Trace complete.

Local:

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

1 1 ms <1 ms <1 ms 10.0.0.2
2 17 ms 17 ms 51 ms 105-236-9-129-esr-lo.mtnbusiness.co.za [105.236.
9.129]
3 35 ms 34 ms 35 ms ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178
.65]
4 50 ms 70 ms 74 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
5 35 ms 35 ms 37 ms am-cr-2.nl--am-cr-nl-b.mtnns.net [196.44.31.171]

6 35 ms 35 ms 36 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 52 ms 51 ms 48 ms rrba-ip-se-2-wan.telkom-ipnet.co.za [196.25.58.1
7]
8 51 ms 50 ms 49 ms 196.43.25.137
9 52 ms 50 ms 51 ms 196.43.51.78
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 telkom-sa-tienet-gw.telkom-ipnet.co.za [196.25.54.62] reports: Destination
net unreachable.

Trace complete.
 
elriconess said:
International:

Tracing route to www.bbc.net.uk [212.58.244.66]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 10.0.0.2
2 17 ms 17 ms 17 ms 105-236-9-129-esr-lo.mtnbusiness.co.za [105.236.
9.129]
3 36 ms 35 ms 35 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178
.77]
4 27 ms 25 ms 25 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
5 36 ms 36 ms 35 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 24 ms 21 ms 23 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 207 ms 205 ms 205 ms bbc-linx.pr01.thdow.bbc.co.uk [195.66.224.103]
8 * * * Request timed out.
9 * * * Request timed out.
10 193 ms 192 ms 192 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
11 214 ms 214 ms 216 ms 132.185.255.149
12 201 ms 203 ms 201 ms bbc-vip111.telhc.bbc.co.uk [212.58.244.66]

Trace complete.

Local:

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

1 1 ms <1 ms <1 ms 10.0.0.2
2 17 ms 17 ms 51 ms 105-236-9-129-esr-lo.mtnbusiness.co.za [105.236.
9.129]
3 35 ms 34 ms 35 ms ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178
.65]
4 50 ms 70 ms 74 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
5 35 ms 35 ms 37 ms am-cr-2.nl--am-cr-nl-b.mtnns.net [196.44.31.171]

6 35 ms 35 ms 36 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 52 ms 51 ms 48 ms rrba-ip-se-2-wan.telkom-ipnet.co.za [196.25.58.1
7]
8 51 ms 50 ms 49 ms 196.43.25.137
9 52 ms 50 ms 51 ms 196.43.51.78
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 telkom-sa-tienet-gw.telkom-ipnet.co.za [196.25.54.62] reports: Destination
net unreachable.

Trace complete.
Click to expand...

Why are you posting in the TI uncapped section when you are using Afrihost as your ISP?

Also Afrihost had some or may be still experiencing DSL issues this morning.
If you think it is a Telkom related problem, try contacting TelkomZA for some help.
 
RoMark said:
Why are you posting in the TI uncapped section when you are using Afrihost as your ISP?

Also Afrihost had some or may be still experiencing DSL issues this morning.
If you think it is a Telkom related problem, try contacting TelkomZA for some help.
Click to expand...

Used an incorrect Account.

International:

Tracing route to www.bbc.net.uk [212.58.246.90]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 10.0.0.2
2 17 ms 17 ms 17 ms ti-224-156-01.telkomadsl.co.za [105.224.156.1]
3 35 ms 35 ms 35 ms ti-224-0-38.telkomadsl.co.za [105.224.0.38]
4 118 ms 35 ms 35 ms ti-228-0-13.telkomadsl.co.za [105.228.0.13]
5 60 ms 23 ms 23 ms rndf-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.41]
6 205 ms 205 ms 205 ms lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.
43.9.58]
7 208 ms 207 ms 207 ms ldn-b5-link.telia.net [62.115.35.89]
8 219 ms 220 ms 219 ms atos-ic-151907-ldn-b5.c.telia.net [80.239.132.14
2]
9 * * * Request timed out.
10 * * * Request timed out.
11 212 ms 211 ms 211 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
12 226 ms 223 ms 223 ms 132.185.255.164
13 209 ms 209 ms 209 ms bbc-vip011.cwwtf.bbc.co.uk [212.58.246.90]

Trace complete.

Local:

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

1 1 ms <1 ms <1 ms 10.0.0.2
2 18 ms 18 ms 18 ms ti-224-156-01.telkomadsl.co.za [105.224.156.1]
3 49 ms 48 ms 49 ms ti-224-0-38.telkomadsl.co.za [105.224.0.38]
4 48 ms 48 ms 49 ms ti-228-0-13.telkomadsl.co.za [105.228.0.13]
5 48 ms 49 ms 47 ms 196.25.124.8
6 49 ms 49 ms 49 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.37]
7 38 ms 37 ms 39 ms 196.43.51.78
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 telkom-sa-tienet-gw.telkom-ipnet.co.za [196.25.54.62] reports: Destination
net unreachable.

Trace complete.
 
Was about to rant about dismal torrent speeds during the day and just now my browsing also slowed to a crawl :mad:

Turns out the torrent I started yesterday is now going like the clappers hence the slow browsing speed. One of those rather arb torrents with 114 seeders & 296 leechers.... running at full line speed :D
 
Last edited:
Something isn't okay with my Exchange or Telkom network:

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

1 1 ms <1 ms 2 ms Billion.400G [10.0.0.2]
2 17 ms 17 ms 17 ms ti-224-156-01.telkomadsl.co.za [105.224.156.1]
3 50 ms 219 ms 231 ms ti-224-0-38.telkomadsl.co.za [105.224.0.38]
4 254 ms 232 ms 212 ms ti-228-0-13.telkomadsl.co.za [105.228.0.13]
5 216 ms 215 ms 215 ms 196.25.124.8
6 50 ms 49 ms 49 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.37]
7 38 ms 38 ms 37 ms 196.43.51.78
8 * * * Request timed out.
9 * * telkom-sa-tienet-gw.telkom-ipnet.co.za [196.25.54.62] re
ports: Destination net unreachable.

Trace complete.


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

1 1 ms <1 ms 1 ms Billion.400G [10.0.0.2]
2 17 ms 18 ms 17 ms ti-224-156-01.telkomadsl.co.za [105.224.156.1]
3 49 ms 49 ms 48 ms ti-224-0-38.telkomadsl.co.za [105.224.0.38]
4 112 ms 61 ms 209 ms ti-228-0-13.telkomadsl.co.za [105.228.0.13]
5 49 ms 48 ms 48 ms 196.25.124.8
6 49 ms 49 ms 49 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.37]
7 38 ms 37 ms 38 ms 196.43.51.78
8 telkom-sa-tienet-gw.telkom-ipnet.co.za [196.25.54.62] reports: Destination
net unreachable.

Trace complete.
 
Something seems to be wrong tonight, im on a 2Meg TI Uncapped account Based in Wilropark Roodepoort JHB, and this is my speeds and tracert:

Last Result: (JHB Server)
Download Speed: 714 kbps (89.3 KB/sec transfer rate)
Upload Speed: 151 kbps (18.9 KB/sec transfer rate)
Latency: 66 ms
10/15/2013 9:07:22 PM

Last Result: (International)
Download Speed: 259 kbps (32.4 KB/sec transfer rate)
Upload Speed: 138 kbps (17.3 KB/sec transfer rate)
Latency: 236 ms
10/15/2013 9:25:25 PM

Last Result: (cape Town)
Download Speed: 848 kbps (106 KB/sec transfer rate)
Upload Speed: 83 kbps (10.4 KB/sec transfer rate)
Latency: 54 ms
10/15/2013 9:26:33 PM

Tracert (Local):

Tracert toTelkom.co.za.jpg


Tracert (International):

Tracrt intl.jpg
 
kimimaro said:
Hope its problem because this what telkomza said

"The test account proved that your problem is not line or exchange related but due to shaping on the ISP account,
Please refer the user to the AUP, and recommend that they schedule their P2P for off-peak (23h00 to 07h00).

Downloading at (23h00 to 07h00) gives me speeds that are less then 10 KB/s, This has been happening for 2 months. This month i havent been able to download 1 gig. Depressing.
Click to expand...

Same with me, I'm in Pretoria East and my torrents are extremely slow any time of the day for around 2 months. Normal downloads appear to be fine. This is not the way it used to be from Telkom, they said the only shaping was time based and torrents used to run well all day if I would let them.

There is no question that Telkom is strangling torrent downloads. It must be regional, not everyone is experiencing these lousy DL speeds on torrent. Telkom............................used to could.................
 
I've been browsing through this thread (took me a bloody while, seeing as we're on page 359 already :P) and TI is on my list of options for when my line goes 10mbps during November. At the moment, my options are:

1) Afrihost Home Uncapped 10mbps
2) Afrihost Capped 200GB (not gonna be enough, with Netflix HD streaming)
3) Telkom Home Uncapped 10mbps

So in terms of option 3 - how are you guys experiencing TI's residential Uncapped lately? Is it going through the same latency problems as the other ISP's? (AH, OW, etc)? And how harsh is the shaping?

Easily 90% of my account's usage would be Netflix streaming (via UnoTelly)... which could easily account for about 200+GB if most of the content comes down in HD (which it probably will on 10mbps). However, I also use my home ADSL to VPN into my work network in the evenings and on weekends, if I need to get some work done and don't feel like taking my laptop in to the office. Then there are the occasional HTTP downloads. As for torrents... well, I don't torrent ALL the time, but I do from time to time. Maybe about 20 - 30GB a month worth of torrents, probably less, usually.
 
Last edited:
I'm quite happy with TI as my ISP. There've been some issues here and there, but the good outweighs the bad, in my case anyway. Can't comment on torrents, because I don't use them, but I haven't had any problems for a long time with http dl's. Line always performs at full speed at pretty much any part of the day I've needed to use it. I schedule the big dl's for after 11pm, as advised, but even when I've needed to download at any time, it's been fine. Give TI a try. Sign up for 12 months and reap the benefits of a 25% discount ;)
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X