Telkom Internet Uncapped User Feedback.

[LomWoss]

You don't need to do that, PM me your username, and please include a traceroute to a site that you deem slow. (I am still travelling, so I may not necessarily be able to respond before Monday).

Thanks for looking at this ranger. No rush on this, enjoy the holiday and then when your back at work, we can get out the whip. I'll PM you my details and then you can check it out at your own leisure. You'll probably find that come Monday the new month rolls over and everything gets reset for the month and it all suddenly works like it should, well I'm hoping at any rate

 

[MightyMuffinMan]

Back to full line speed on torrents.

I assume telkom is actively managing bandwidth hogs as the day changes to protect QOS.

Also its done very well.

 

[MickZA]

ROFL - I don't believe it, here we are discussing soft-capping and I get the following email from Telkom:

View attachment 44585

... still no mention of uncapped accounts.

Back to full line speed on torrents.

I assume telkom is actively managing bandwidth hogs as the day changes to protect QOS.

Also its done very well.

... and the TI Tracker warning doesn't mention being soft-capped:

The bandwidth consumption on your uncapped account has reached a stage whereby it is having a negative impact on the general performance of our network. In terms of the Telkom Internet Acceptable Use Policy, your account will be managed in a manner that allows us to optimise network efficiency for all users.

Looks like there are no set GB soft-cap limits but, as MightyMuffinMan says, it seems as if you the abuse the network TI will send you to the "naughty corner" for a while but the punishment is not as onerous as that imposed by some other ISPs atm.

 

[killkom]

I have one of these accounts now and I am quite disappointed

I have a 10 meg mweb uncapped account and that has been messed up by this seacom cable issue so I understand its a bit up and down

I also have a 10 meg telkom uncapped account and when I created it I asked if this would be affected by seacom and I was told no it isn't

So why is it that when I try use it for hulu or netflix or you tube its constantly buffering I get throttled to 1 meg on my 7 meg line

I clicked download at about 11pm at night for a game I purchased from origin which was about 20 gigs when it started I was getting the full speed of the line so I thought cool but I went back at about 5am and it had only downloaded 15% and it was limited to 1 meg again. OVERNIGHT COME ON!!!!!!

I changed the account to my mweb account and it went to full speed and finished in a couple of hours DURING THE DAY!!!!

So this is by far the worst uncapped service I have ever seen actually uncapped should not be in its name my mweb web account with the cable break is far better than this.

What's the point of throttling someone from the first meg you download I mean I understand if after a large amount of data but right from the beginning that makes this a rubbish product

 

[Hectic]

I have one of these accounts now and I am quite disappointed

I have a 10 meg mweb uncapped account and that has been messed up by this seacom cable issue so I understand its a bit up and down

I also have a 10 meg telkom uncapped account and when I created it I asked if this would be affected by seacom and I was told no it isn't

So why is it that when I try use it for hulu or netflix or you tube its constantly buffering I get throttled to 1 meg on my 7 meg line

I clicked download at about 11pm at night for a game I purchased from origin which was about 20 gigs when it started I was getting the full speed of the line so I thought cool but I went back at about 5am and it had only downloaded 15% and it was limited to 1 meg again. OVERNIGHT COME ON!!!!!!

I changed the account to my mweb account and it went to full speed and finished in a couple of hours DURING THE DAY!!!!

So this is by far the worst uncapped service I have ever seen actually uncapped should not be in its name my mweb web account with the cable break is far better than this.

What's the point of throttling someone from the first meg you download I mean I understand if after a large amount of data but right from the beginning that makes this a rubbish product

Surely you must have read the other post here where we mostly claim how grt our product work. Nobody would lie about it, but now you come tell us that you are throttled from the beginning and that it is a rubbish product.

I can understand that you are frustrated, comming from an IS based ISP with the recent problem, but you can't surely be that naive?

There is a problem with the speed.maybe you are on a basic uncapped package (1meg) instead of the actual package you want.
Maybe your dl was impacted by the huge DDos attack, maybe it was a Telkom IPC or some other Telkom issue.
Maybe there was a problem with the Origin servers during the night.

Contact the Helpdesk to ensure you are on the right speed package.
Do a speedtest, traceroute and post it and maybe you will receive some usefull feedback and you can try and turn it around and get back to downloading.

 

[Hectic]

Apologies for the double post:

Yesterday I posted here with traceroutes and Ping tests where I indicated that the latency were very high locally and internationally.
A few minutes later I edited and said it was all okay again.

Since then I have found that the latency seems to jump around a lot. At times I can't do speedtests. Other times my speedtests seems to reflect my normal speed, but actual downloads are in the region of 370KB/s compared to my normal 420-430 KB/s range.

I did phone Telkom yeserday and they could not find any problem in my area.

This morning I phoned 3 times , just to be confronted by 3 "less sharp pencils". They had no idea what I was talking about when I used the words "Ping & latency" They kept on asking asking "what is your exact problem" and "what is that?"

I eventually asked the last guy to recreate my port. 5 seconds later he told me it was done.
In my experience they normally ask to switch off the router and then recreate, I might be wrong though.

My question then.
Are any of you experiencing this, especially the PE, Uitenhage boys?
Have done less than 100GB on the line, so I do not believe that is an issue.

We did have some nasty winds and a bit of rain the last few days.

I have tested with AH as well and the avg speed is about 350KB/s, so about 20KB/s slower than with TI, although the latency was a lot better.

 

[ranger]

Thanks for looking at this ranger. No rush on this, enjoy the holiday and then when your back at work, we can get out the whip. I'll PM you my details and then you can check it out at your own leisure. You'll probably find that come Monday the new month rolls over and everything gets reset for the month and it all suddenly works like it should, well I'm hoping at any rate

As in the PM I sent, you are on TIBasicUncapped as far back as I can see, so unless there is an inconsistency in your account between the last two systems (one that I don't have access to, one that I have very limited and inconvenient access to), you are on (and being billed for) 1Mbps. I logged a ticket for this to be resolved (probably by Tuesday, but maybe up to Wednesday), since I can't do anything about this myself.

 

[ranger]

I have one of these accounts now and I am quite disappointed

From your description it is almost certain you have a 1Mbps account, not a 10Mbps account.

(eish, the ability to see what speed uncapped account you have is the one thing I wanted to have added on the tracker for uncapped users, but for some reason it hasn't been done yet ...)

I have a 10 meg mweb uncapped account and that has been messed up by this seacom cable issue so I understand its a bit up and down

I also have a 10 meg telkom uncapped account and when I created it I asked if this would be affected by seacom and I was told no it isn't

AFAIK we have ZERO capacity on Seacom.

Please PM me your TI username, and the email address you would like to receive notification on when issues are resolved, and I will try and check your account to verify what uncapped account you have, and log a ticket for whatever the issue appears to be. Unfortunately, due to the long weekend, I don't think anything can be done about it via our billing team until Tuesday (but you can try verify with the call centre if they can fix it).

 

[ranger]

Is it only me or has the net gone downhill suddenly?

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\>tracert foxconn.com

Tracing route to foxconn.com [210.80.95.166]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Billion.810VNTX [10.0.0.2]
2 199 ms 288 ms 300 ms 224-140-1.dsl.subscriber.telkomsa.net [
40.1]
3 259 ms 19 ms 18 ms 226-0-6.dsl.subscriber.telkomsa.net [
]
4 26 ms 26 ms 26 ms 226-0-13.dsl.subscriber.telkomsa.net [
13]
5 26 ms 26 ms 25 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.45]

No exchange congestion here.

6 202 ms 177 ms 175 ms ams-ip-dir-globalc-pos-4-0-0.telkom-ipnet.co.za
[196.43.18.26]
7 552 ms 345 ms 343 ms ge13-42.br01.hkg04.pccwbtn.net [63.218.2.201]
8 * * * Request timed out.
9 351 ms 356 ms 410 ms 0.ge-6-1-2-XT3.HKG2.Alter.Net [210.80.3.113]
10 394 ms 343 ms 381 ms 0.so-2-0-2.XT3.TPE1.Alter.Net [210.80.49.242]
11 448 ms 351 ms 345 ms POS5-0-0.GW1.TPE1.ALTER.NET [210.80.2.42]
12 354 ms 625 ms 473 ms honhai-tw-gw.customer.alter.net [219.90.63.114]

Doesn't look too bad, Hong Kong is a long way away.

C:\Users\>tracert saix.net

Tracing route to saix.net [196.25.1.204]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Billion.810VNTX [10.0.0.2]
2 343 ms 359 ms 386 ms 224-140-1.dsl.subscriber.telkomsa.net [
40.1]
3 429 ms 436 ms 436 ms 226-0-6.dsl.subscriber.telkomsa.net [
]
4 290 ms 292 ms 311 ms 226-0-13.dsl.subscriber.telkomsa.net [
13]
5 341 ms 349 ms 343 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.45]
6 347 ms 355 ms 356 ms wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [1
96.43.11.30]
7 * wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [196.43.11.30] repo
rts: Destination net unreachable.

The firewall in front of saix.net doesn't allow ICMP to it. A better local address is capetown.spdtst.saix.net (or rosebank for people not in the Western Cape):

$ traceroute capetown.spdtst.saix.net
traceroute to capetown.spdtst.saix.net (196.25.37.14), 30 hops max, 60 byte packets
1 224-84-1.dsl.subscriber.telkomsa.net (105.224.84.1) 15.074 ms 17.319 ms 19.214 ms
2 226-0-6.dsl.subscriber.telkomsa.net (105.226.0.6) 22.855 ms 24.997 ms 27.712 ms
3 226-0-13.dsl.subscriber.telkomsa.net (105.226.0.13) 30.147 ms 33.934 ms 35.134 ms
4 wblv-ip-hsll-1-wan.telkom-ipnet.co.za (196.25.39.45) 37.298 ms 39.966 ms 42.659 ms
5 196.43.51.26 (196.43.51.26) 45.533 ms 48.444 ms 50.513 ms
6 wbs-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za (196.25.37.2) 53.411 ms !X 15.297 ms !X *

C:\Users\>tracert 8.8.8.8

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 Billion.810VNTX [10.0.0.2]
2 203 ms 9 ms 9 ms 224-140-1.dsl.subscriber.telkomsa.net [
40.1]
3 113 ms 26 ms 25 ms 226-0-6.dsl.subscriber.telkomsa.net [105.226.0.6
]
4 174 ms 202 ms 116 ms 226-0-13.dsl.subscriber.telkomsa.net [105.226.0.
13]
5 214 ms 292 ms 200 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.45]

This looks like exchange congestion (but it is difficult to be 100% sure).

$ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 224-84-1.dsl.subscriber.telkomsa.net (105.224.84.1) 15.017 ms 16.697 ms 19.163 ms
2 226-0-6.dsl.subscriber.telkomsa.net (105.226.0.6) 23.027 ms 24.765 ms 27.198 ms
3 226-0-13.dsl.subscriber.telkomsa.net (105.226.0.13) 30.164 ms 32.890 ms 36.791 ms
4 wblv-ip-hsll-1-wan.telkom-ipnet.co.za (196.25.39.45) 37.685 ms 39.931 ms 42.464 ms
5 lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za (196.43.9.58) 189.118 ms 191.829 ms 194.036 ms
6 196.25.191.146 (196.25.191.146) 196.569 ms 159.204 ms 160.083 ms
7 209.85.240.61 (209.85.240.61) 162.037 ms 171.841 ms 167.724 ms
8 209.85.253.92 (209.85.253.92) 171.292 ms 209.85.253.94 (209.85.253.94) 174.026 ms 209.85.253.92 (209.85.253.92) 176.095 ms
9 209.85.240.28 (209.85.240.28) 184.851 ms 187.157 ms 189.143 ms
10 216.239.49.38 (216.239.49.38) 194.197 ms 169.901 ms 216.239.49.36 (216.239.49.36) 173.024 ms
11 * * *
12 google-public-dns-a.google.com (8.8.8.8) 170.624 ms 173.082 ms 175.594 ms

C:\Users\Ronald>tracert telkom.co.za

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

1 <1 ms <1 ms <1 ms Billion.810VNTX [10.0.0.2]
2 288 ms 305 ms 310 ms 224-140-1.dsl.subscriber.telkomsa.net [
40.1]
3 343 ms 360 ms 336 ms 226-0-6.dsl.subscriber.telkomsa.net [
]
4 369 ms 359 ms 359 ms 226-0-13.dsl.subscriber.telkomsa.net [
13]
5 368 ms 383 ms 381 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.45]

Almost certainly exchange congestion

6 48 ms 49 ms 48 ms 196.43.39.166
7 317 ms 325 ms 49 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
8 288 ms 292 ms 313 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.30]
9 341 ms 353 ms 346 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.

Edit:
Seems okay again.

I only saw your post after you edited it ... and it seemed fine (I am currently in the Western Cape, with a 1Mbps line).

 

[MickZA]

Yesterday I posted here with traceroutes and Ping tests where I indicated that the latency were very high locally and internationally.
A few minutes later I edited and said it was all okay again.

Since then I have found that the latency seems to jump around a lot. At times I can't do speedtests. Other times my speedtests seems to reflect my normal speed, but actual downloads are in the region of 370KB/s compared to my normal 420-430 KB/s range.
Are any of you experiencing this, especially the PE, Uitenhage boys?
Have done less than 100GB on the line, so I do not believe that is an issue.

Just done some testing and agree with your findings.

The problem seems to be TI uncapped related as axxess, Afrihost & TI capped accounts are giving stable MyBB speedtest results, international latency as follows:

TI uncapped: 280 - 290ms
TI capped: 250-255ms
Afrihost & axxess: 215-220ms

Month end tinkering by TI maybe?

 

[Pooky]

Hey all, how is your experience if you use 2mb Telkom uncapped? How much usage do you do and do they throttle you?

 

[Jonaling]

Anyone know if the Do uncapped for 10 Mbps for R699 is shaped?

 

[Hectic]

I finally reached the limit and my torrents are throttled. But browsing is running very well. (actually running torrent at 1/4 line speed and still browsing with no problems.)

Total downloaded (2 MB uncapped) - 386GB
Total uploaded - 45 GB

from http://userstats.adsl.saix.net/

Youtube streaming very well.
Have yet to test gaming.(however have afrihost 1 GB per month for that)

Very happy with new setup and don't mind the usage limit and its better than last month (Did go abit overboard this month with HD torrents and HD youtube.


from http://userstats.adsl.saix.net/

Sessions68
Online Time (Seconds) 2305073
Upload (Bytes) 42 197 320 122
Download (Bytes) 405 036 548 014
Combined (Bytes) 447 233 868 136


also: Message on https://secure.telkomsa.net/titracker/ S

@Pooky

 

[Hectic]

No exchange congestion here.



Doesn't look too bad, Hong Kong is a long way away.



The firewall in front of saix.net doesn't allow ICMP to it. A better local address is capetown.spdtst.saix.net (or rosebank for people not in the Western Cape):

$ traceroute capetown.spdtst.saix.net
traceroute to capetown.spdtst.saix.net (196.25.37.14), 30 hops max, 60 byte packets
1 224-84-1.dsl.subscriber.telkomsa.net (105.224.84.1) 15.074 ms 17.319 ms 19.214 ms
2 226-0-6.dsl.subscriber.telkomsa.net (105.226.0.6) 22.855 ms 24.997 ms 27.712 ms
3 226-0-13.dsl.subscriber.telkomsa.net (105.226.0.13) 30.147 ms 33.934 ms 35.134 ms
4 wblv-ip-hsll-1-wan.telkom-ipnet.co.za (196.25.39.45) 37.298 ms 39.966 ms 42.659 ms
5 196.43.51.26 (196.43.51.26) 45.533 ms 48.444 ms 50.513 ms
6 wbs-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za (196.25.37.2) 53.411 ms !X 15.297 ms !X *




This looks like exchange congestion (but it is difficult to be 100% sure).

$ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 224-84-1.dsl.subscriber.telkomsa.net (105.224.84.1) 15.017 ms 16.697 ms 19.163 ms
2 226-0-6.dsl.subscriber.telkomsa.net (105.226.0.6) 23.027 ms 24.765 ms 27.198 ms
3 226-0-13.dsl.subscriber.telkomsa.net (105.226.0.13) 30.164 ms 32.890 ms 36.791 ms
4 wblv-ip-hsll-1-wan.telkom-ipnet.co.za (196.25.39.45) 37.685 ms 39.931 ms 42.464 ms
5 lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za (196.43.9.58) 189.118 ms 191.829 ms 194.036 ms
6 196.25.191.146 (196.25.191.146) 196.569 ms 159.204 ms 160.083 ms
7 209.85.240.61 (209.85.240.61) 162.037 ms 171.841 ms 167.724 ms
8 209.85.253.92 (209.85.253.92) 171.292 ms 209.85.253.94 (209.85.253.94) 174.026 ms 209.85.253.92 (209.85.253.92) 176.095 ms
9 209.85.240.28 (209.85.240.28) 184.851 ms 187.157 ms 189.143 ms
10 216.239.49.38 (216.239.49.38) 194.197 ms 169.901 ms 216.239.49.36 (216.239.49.36) 173.024 ms
11 * * *
12 google-public-dns-a.google.com (8.8.8.8) 170.624 ms 173.082 ms 175.594 ms



Almost certainly exchange congestion



I only saw your post after you edited it ... and it seemed fine (I am currently in the Western Cape, with a 1Mbps line).

Not sure what is going on Ranger, but my exchange was upgraded 2 weeks ago, so not sure why that high latency figures point to the exchange and seconds later all is fine again.

 

[Pooky]

@Pooky

Thanks, that seems very good.

 

[Hectic]

Just done some testing and agree with your findings.

The problem seems to be TI uncapped related as axxess, Afrihost & TI capped accounts are giving stable MyBB speedtest results, international latency as follows:

TI uncapped: 280 - 290ms
TI capped: 250-255ms
Afrihost & axxess: 215-220ms

Month end tinkering by TI maybe?

Thx Micky. Weird. Torrents are running at full speed atm.

 

[MightyMuffinMan]

Hey all, how is your experience if you use 2mb Telkom uncapped? How much usage do you do and do they throttle you?

At least read the last 5 pages of posts in the tread before asking a question. Pro forum tip.

Surely you must have read the other post here where we mostly claim how grt our product work. Nobody would lie about it, but now you come tell us that you are throttled from the beginning and that it is a rubbish product.

I agree. Trouble shoot the product first. And as another user found out he was incorrectly placed on a 1 MB account instead of his 2 MB account. (somewhere here ranger posted the isssue and that it would be resolved)

 

[MightyMuffinMan]

Thought I'd mention this in a separate post.

Is it just me or does telkom accounts have a pad European jitter compared to other ISPs

What I mean is that the ping is similar if not better than other ISP yet connection will randomly stop and start for like a millisecond when in a game (only noticeable in games) regardless of game or server.

 

[killkom]

Hi I have a 10 meg acount it looks good on speed test.net

Netflix and hulu is definitely shaped its wierd the menus and selection scenes are actually quite fast but when a movie starts it just falls apart I have a free fnb capped account and it works best out of all of them at the moment but out of fnb mweb telkom telkom looses hands down.

Netflix and hulu works better with mweb much less buffering than telkom currently works best with fnb

Downloads go to full speed for a while I have a bit meter and can monitor this after a couple of hours it drops off to 1 meg.

Also The assumptIon that there is something wrong with the origin servers is not founded since its running at 1 meg on telkom when I switch to mweb if goes to full speed

I am not new to broadband I have several accounts from different ISPs and this for me does not match them.

 

[ranger]

I am not new to broadband I have several accounts from different ISPs and this for me does not match them.

Please post a traceroute, to confirm which site you are going through. Cape Town is still running higher utilisation than we had planned for, and some physical work is required to increase capacity there.

(speed won't be affected by how long the download has been running, but by the utilisation on the network, and there are some variances by region. For example, in the Cape Town site, while utilisation is high during the day - as one would expect - it increases further from around 15h30 to peak at around 22h30, and only drops below the 09h00 utilisation after midnight)