Telkom Internet Capped/Uncapped User Feedback (Pt2)

That is the case presently. Daytime torrents are throttled quite badly.

Now you want to make us use the midnight run.

I don't think this is going to be popular. Look also at the top users of other ISPs (yes, they list them). Compared to them we're download amateurs.

Our 10Mbps consumer uncapped leader does over 1TB every month.

We can't help that you're amateurs :p, or do you need video tutorials on how to schedule?
 
105.229.x.x is causing abysmal speeds and higher pings again. Please stop routing through it since it's clearly struggling.
Pings fluctuating between 40 and 150 to 105.229.0.6. tbnb-ip-hsll-1-wan.telkom-ipnet.co.za seems to be timing out now and then too.
Code:
  1     1 ms    <1 ms    <1 ms  10.0.0.2
  2    10 ms    10 ms     9 ms  ti-224-164-01.telkomadsl.co.za [105.224.164.1]
  3   126 ms   116 ms   119 ms  105.229.0.6
  4    47 ms    46 ms    45 ms  105.229.0.29
  5    62 ms    44 ms    46 ms  tbnb-ip-hsll-1-wan.telkom-ipnet.co.za [165.165.235.173]
  6    55 ms    57 ms   142 ms  rrba-ip-lir-1-gig-5-0-0.telkom-ipnet.co.za [196.43.52.38]
  7    61 ms    65 ms    58 ms  72.14.212.1
  8   126 ms    64 ms    56 ms  64.233.174.57
  9    63 ms    55 ms    56 ms  jnb01s02-in-f15.1e100.net [74.125.233.79]

Trace complete.
 
105.229.x.x is causing abysmal speeds and higher pings again. Please stop routing through it since it's clearly struggling.
Pings fluctuating between 40 and 150 to 105.229.0.6. tbnb-ip-hsll-1-wan.telkom-ipnet.co.za seems to be timing out now and then too.
Code:
  1     1 ms    <1 ms    <1 ms  10.0.0.2
  2    10 ms    10 ms     9 ms  ti-224-164-01.telkomadsl.co.za [105.224.164.1]
  3   126 ms   116 ms   119 ms  105.229.0.6
  4    47 ms    46 ms    45 ms  105.229.0.29
  5    62 ms    44 ms    46 ms  tbnb-ip-hsll-1-wan.telkom-ipnet.co.za [165.165.235.173]
  6    55 ms    57 ms   142 ms  rrba-ip-lir-1-gig-5-0-0.telkom-ipnet.co.za [196.43.52.38]
  7    61 ms    65 ms    58 ms  72.14.212.1
  8   126 ms    64 ms    56 ms  64.233.174.57
  9    63 ms    55 ms    56 ms  jnb01s02-in-f15.1e100.net [74.125.233.79]

Trace complete.

While it looks like it may be on our side, it isn't conclusive. With the high variability on the other hops, it can possible be DSLAM congestion or another issue on the ADSL network ( that happened to be lower when traceroute was on hop 2). I saw behaviour like this quite often when my DSLAM was congested.

Results from mtr, winmtr, or ping plotter would be better, as they avoid this behaviour by ping all hops simultaneously.

Nevertheless I will have a look at anything that may affect users going through Durban, and I believe Durban is currently at the top of the list for bandwidth upgrades.
 
While it looks like it may be on our side, it isn't conclusive. With the high variability on the other hops, it can possible be DSLAM congestion or another issue on the ADSL network ( that happened to be lower when traceroute was on hop 2). I saw behaviour like this quite often when my DSLAM was congested.

Results from mtr, winmtr, or ping plotter would be better, as they avoid this behaviour by ping all hops simultaneously.

Nevertheless I will have a look at anything that may affect users going through Durban, and I believe Durban is currently at the top of the list for bandwidth upgrades.

Here's a tracert from WinMTR:
To google.co.za:
Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                                10.0.0.2 -    0 |   49 |   49 |    0 |    1 |   13 |    1 |
|          ti-224-164-01.telkomadsl.co.za -    0 |   49 |   49 |    8 |   12 |   31 |   11 |
|                             105.229.0.6 -    0 |   49 |   49 |   41 |   48 |   66 |   50 |
|                            105.229.0.29 -    3 |   45 |   44 |   42 |   50 |   64 |   48 |
|   tbnb-ip-hsll-1-wan.telkom-ipnet.co.za -    3 |   45 |   44 |   42 |   48 |   63 |   48 |
|rrba-ip-lir-1-gig-5-0-0.telkom-ipnet.co.za -    0 |   49 |   49 |   53 |   61 |   84 |   57 |
|                             72.14.212.1 -    3 |   45 |   44 |   53 |   59 |   79 |   59 |
|                           64.233.174.57 -    3 |   45 |   44 |   53 |   60 |   82 |   57 |
|               jnb01s02-in-f15.1e100.net -    0 |   49 |   49 |   53 |   61 |   84 |   60 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Thanks for informing me of this wonderful tool!

The ping has gone down a bit, but the speeds are still quite bad. Can't stream above 360p YouTube and Twitch is unwatchable.

The reason I don't think that it's due to the local DSLAM is because a mate in Howick is getting the same problem. I don't think that those first two hops are the same for our areas.
 
Last edited:
Here's a tracert from WinMTR:
To google.co.za:
Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                                10.0.0.2 -    0 |   49 |   49 |    0 |    1 |   13 |    1 |
|          ti-224-164-01.telkomadsl.co.za -    0 |   49 |   49 |    8 |   12 |   31 |   11 |
|                             105.229.0.6 -    0 |   49 |   49 |   41 |   48 |   66 |   50 |
|                            105.229.0.29 -    3 |   45 |   44 |   42 |   50 |   64 |   48 |
|   tbnb-ip-hsll-1-wan.telkom-ipnet.co.za -    3 |   45 |   44 |   42 |   48 |   63 |   48 |
|rrba-ip-lir-1-gig-5-0-0.telkom-ipnet.co.za -    0 |   49 |   49 |   53 |   61 |   84 |   57 |
|                             72.14.212.1 -    3 |   45 |   44 |   53 |   59 |   79 |   59 |
|                           64.233.174.57 -    3 |   45 |   44 |   53 |   60 |   82 |   57 |
|               jnb01s02-in-f15.1e100.net -    0 |   49 |   49 |   53 |   61 |   84 |   60 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Thanks for informing me of this wonderful tool!

The ping has gone down a bit, but the speeds are still quite bad. Can't stream above 360p YouTube and Twitch is unwatchable.

The reason I don't think that it's due to the local DSLAM is because a mate in Howick is getting the same problem. I don't think that those first two hops are the same for our areas.

The 23ms difference between best and worst times on hop 2 (the edge service router, first IP hop after the DSLAM, before our IPC link) is propagated (and will be magnified in the case of TCP) through the rest of the hops, so almost certainly DSLAM congestion.

PM me your username and I will try and see whether we can get any info ...

The second hop must be the same for users of the same ISP on the same DSLAM.
 
So...my account(uncapped) has been blocked due to excessive downloading. I thought that after 80 gigs of downloading, my account would get shaped...
 
So...my account(uncapped) has been blocked due to excessive downloading. I thought that after 80 gigs of downloading, my account would get shaped...

It shouldn't be blocked, but throttled. If you mean all traffic is redirected to a page on tracker, log in, accept rhat you have been informed you are in breach of the AUP, and you will have slowe internet for a few days
If you can't accept for some reason, PM me your username and I will accept on ypur behalf (the call centre should be able to, but even though they were informed weeks in advance, seem to not know how).
 
It shouldn't be blocked, but throttled. If you mean all traffic is redirected to a page on tracker, log in, accept rhat you have been informed you are in breach of the AUP, and you will have slowe internet for a few days
If you can't accept for some reason, PM me your username and I will accept on ypur behalf (the call centre should be able to, but even though they were informed weeks in advance, seem to not know how).

Pm'd
 
Decided I'm gonna cancel my uncapped account with telkom and move to another ISP.
Seems I did 88 Gigabytes worth of downloading (along with 12 Gigabytes up) and my internet has been shaped horribly, I can't even open GMail properly.
I did so many speed tests, but the speed was so slow they never completed. Finally managed one and this what I get for a 2 Meg line



Anyone care to recommend me a new ISP
 
Decided I'm gonna cancel my uncapped account with telkom and move to another ISP.
Seems I did 88 Gigabytes worth of downloading (along with 12 Gigabytes up) and my internet has been shaped horribly, I can't even open GMail properly.
I did so many speed tests, but the speed was so slow they never completed. Finally managed one and this what I get for a 2 Meg line



Anyone care to recommend me a new ISP

Same happened to me. Looks like you have to schedule your bulk downloads to 12am-6am or you will get throttled to 384k at around 100gb.

I might stay another month and schedule my downloads better to see how it turns out. The only other ISP in the same price range is WA which doesn't seem much better with their star rating system.
 
Last edited:
Crystal Web. I also left Telkom Internet last month. Have been with Crystal Web since 1 June. Have done about 180GB so far on my 2MB line. Left home this morning and NZBs were moving along at +-205 kilobytes per second.

SHHHHHH!!!!!! DAMMIT!!@!!!!!!SDFGSDERW#$@#$@%@#$%$#!@#$@$~!!!!!!!
 
2Mb/s

1.png

2.png

3580428170.png

3580435199.png

Code:
traceroute to www.saix.net (196.25.1.204), 30 hops max, 60 byte packets
 1  * * *
 2  ti-224-16-01.telkomadsl.co.za (105.224.16.1)  27.002 ms  28.942 ms  30.951 ms
 3  105.229.0.6 (105.229.0.6)  126.949 ms  129.060 ms  132.935 ms
 4  105.229.0.29 (105.229.0.29)  42.865 ms  44.908 ms  48.875 ms
 5  tbnb-ip-hsll-1-wan.telkom-ipnet.co.za (165.165.235.173)  49.420 ms  52.343 ms  56.813 ms
 6  wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za (196.43.11.30)  80.816 ms  58.069 ms  58.041 ms
 7  wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za (196.43.11.30)  36.033 ms !X * *

Pings are high due to 105.229.0.6 which is something new, was not like this before so it looks like backhaul issues.
 
Last edited:
If 2Mb/s is getting throttled around 100GB is it then safe to assume 4Mb/s is 200GB , maybe 250GB if downloads are scheduled between 12-6 ? I hate that this is all guess work, Telkom should think about getting something more interactive/detailed than just a normal user - power user bar.
 
If 2Mb/s is getting throttled around 100GB is it then safe to assume 4Mb/s is 200GB , maybe 250GB if downloads are scheduled between 12-6 ? I hate that this is all guess work, Telkom should think about getting something more interactive/detailed than just a normal user - power user bar.

My 4meg was throttled at 292GB for May and 300GB for June. This month all downloads were done between 00h00 and 06h00.
 
Does local traffic count differently towards FUP? Or is it only 0-6am?
 
Top
Sign up to the MyBroadband newsletter
X