Telkom Internet Capped/Uncapped User Feedback (Pt2)

Mental said:
Code: 
Tracing route to google.co.za 
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.0.0.2
  2    10 ms    10 ms    10 ms  obfn-ip-bb-1.north.dsl.telkomsa.net [105.224.132
.1]
  3    20 ms    20 ms    19 ms  ipc-up-2.north.telkomsa.net [105.228.0.6]
  4    21 ms    19 ms    19 ms  ipc-aggr-2.north.telkomsa.net [105.228.0.13]
  5    21 ms    21 ms    20 ms  jb1-pr-01-te1-0.net.telkomsa.net [105.187.249.6]

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

  7    21 ms    21 ms    20 ms  72.14.237.239
  8    21 ms    20 ms    20 ms  jnb01s07-in-f3.1e100.net [74.125.233.3]

Trace complete.

streaming = constant buffering on 240p
Click to expand...

Rather try www.bbc.co.uk
 
Code: 
Tracing route to www.bbc.net.uk [212.58.246.92]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.0.0.2
  2    10 ms    10 ms    10 ms  obfn-ip-bb-1.north.dsl.telkomsa.net [105.224.132
.1]
  3    20 ms    20 ms    20 ms  ipc-up-2.north.telkomsa.net [105.228.0.6]
  4    21 ms    20 ms    20 ms  ipc-aggr-2.north.telkomsa.net [105.228.0.13]
  5    19 ms    19 ms    19 ms  cen-pr-01-be200-vl1.net.telkomsa.net [105.228.0.
18]
  6    20 ms    20 ms    24 ms  196.25.166.217
  7   198 ms   197 ms   199 ms  lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.
43.9.58]
  8   189 ms   206 ms   188 ms  tenge7-2.var01.ldn04.pccwbtn.net [63.218.243.17]

  9   198 ms   211 ms   217 ms  63-218-12-106.static.pccwglobal.net [63.218.12.1
06]
 10   198 ms   198 ms   197 ms  bbc-linx.pr01.thdow.bbc.co.uk [195.66.224.103]
 11     *        *        *     Request timed out.
 12   189 ms   189 ms   189 ms  ae0.er02.cwwtf.bbc.co.uk [132.185.254.90]
 13   200 ms   199 ms   200 ms  132.185.255.165
 14   189 ms   190 ms   189 ms  bbc-vip013.cwwtf.bbc.co.uk [212.58.246.92]

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

Code: 
  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     9 ms     9 ms     9 ms  eltg-ip-bb-1.south.dsl.telkomsa.net [105.224.140.1]
  3    26 ms    20 ms    20 ms  ipc-4-up.south.dsl.telkomsa.net [105.226.0.30]
  4    21 ms    20 ms    20 ms  ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57]
  5    27 ms    26 ms    26 ms  196.25.190.209
  6   173 ms   174 ms   174 ms  lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.43.9.58]
  7   181 ms   181 ms   186 ms  tenge7-2.var01.ldn04.pccwbtn.net [63.218.243.17]
  8   181 ms   181 ms   181 ms  63-218-12-106.static.pccwglobal.net [63.218.12.106]
  9   181 ms   183 ms   186 ms  bbc-linx.pr01.thdow.bbc.co.uk [195.66.224.103]
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12   175 ms   179 ms   180 ms  ae0.er01.telhc.bbc.co.uk [132.185.254.109]
 13   183 ms   182 ms   181 ms  132.185.255.149
 14   174 ms   174 ms   175 ms  bbc-vip113.telhc.bbc.co.uk [212.58.244.68]

Trace complete.
 
Hi Ranger.

I have to take my hat off to you, you guys did an amazing job - internet is flying again.

I have one question for you, though.
Can you explain to us how the titracker works?
To be more clear, what does it take to get into the "Power user" part of the bar, and what happens then?
I understand not all ISP's usually want to disclose AUP limits as such, but I just want to understand what I can and can't do.

You can be as geeky as you want in your description :)

again, thanks for fixing everything... Telkom is really running things well lately, my experience so far has been stellar (From the friendly staff, to the fast service, to the no-BS internet, to fixing faults)
 
Aqua_lung said:
Does telkom Internet block cryptocurrency ports? I'm unable to sync with the dogecoin network.
Click to expand...

Aqua_lung , are you still having problems? My first attempt with dogecoin didn't connect to the dogecoin network because I had a 6-month old version, and the DNS-based seeds hardcoded into that version were not available anymore. Upgrading to the current version allowed me to connect (at least to try syncing the blockchain).

All my testing indicated there shouldn't be any problems in any of the elements in the path that wr directly control.
 
Hi ranger, do you perhaps know whether P2P is meant to be blocked on SoftCap accounts? P2P has been blocked since I got the account, and TK staff are telling me this is normal. I thought SoftCap accounts had priority over Uncapped.

I have a sneaking suspicion that Telkom throttles/manages Softcap accounts when a 24 month contract is in place. :(

Not trying to be controversial, but this is the way I feel right now.
 
Last edited:
Totempole said:
Hi ranger, do you perhaps know whether P2P is meant to be blocked on SoftCap accounts? P2P has been blocked since I got the account, and TK staff are telling me this is normal. I thought SoftCap accounts had priority over Uncapped.

I have a sneaking suspicion that Telkom throttles/manages Softcap accounts when a 24 month contract is in place. :(

Not trying to be controversial, but this is the way I feel right now.
Click to expand...

This should not happen actually. It is most certainly not the case for me connecting via the Durban IPC. I use my 50gb softcap account as my main account for everything from streaming to gaming to downloading and it is one of the best performing accounts out there.

I can't speak for you since you are based in cpt so it might but a completely different experience but I can safely say I don't believe there is a blanket block on p2p for softcap accounts.
 
Totempole said:
Hi ranger, do you perhaps know whether P2P is meant to be blocked on SoftCap accounts?
Click to expand...

We don't block p2p, and have never blocked p2p for users in quota/not in FUP. In the past, we have blocked p2p for users over quota or in FUP (and the AUP/FUP makes provision for it).

We do however shape p2p for soft-cap accounts to the same extent as uncapped. This is supposed to change quite soon.

P2P has been blocked since I got the account, and TK staff are telling me this is normal. I thought SoftCap accounts had priority over Uncapped.
Click to expand...

Yes, except for p2p (unless you have an unshaped capped account which always has higher priority than anything). Again, that will change in a month or two.

I have a sneaking suspicion that Telkom throttles/manages Softcap accounts when a 24 month contract is in place. :(
Click to expand...

No, there is currently no way the billing system can tell us that an account is in contract or not ... we only get suspended/unsuspended/cancelled/upgrade/downgrade requests.
 
Ranger, can you help me explain or troubleshoot my issue. It starts every evening at 9pm. I am in joburg, Westdene to be precise.

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

1 1 ms 1 ms 1 ms 10.0.0.2
2 511 ms 450 ms 875 ms 105-224-40-1.north.dsl.telkomsa.net [105.224.40.
1]
3 1234 ms 1126 ms 1078 ms ipc-1-up.north.dsl.telkomsa.net [105.224.0.6]
4 722 ms 678 ms 696 ms ipc-aggr-1.north.telkomsa.net [105.224.0.13]
5 756 ms 766 ms 760 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.37]
6 548 ms 496 ms 512 ms 196.43.39.162
7 978 ms 597 ms 599 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
8 622 ms 575 ms 732 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.30]
9 651 ms 403 ms 634 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.
 
digitalp said:
Ranger, can you help me explain or troubleshoot my issue. It starts every evening at 9pm. I am in joburg, Westdene to be precise.

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

1 1 ms 1 ms 1 ms 10.0.0.2
2 511 ms 450 ms 875 ms 105-224-40-1.north.dsl.telkomsa.net [105.224.40.
1]
3 1234 ms 1126 ms 1078 ms ipc-1-up.north.dsl.telkomsa.net [105.224.0.6]
4 722 ms 678 ms 696 ms ipc-aggr-1.north.telkomsa.net [105.224.0.13]
5 756 ms 766 ms 760 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.37]
6 548 ms 496 ms 512 ms 196.43.39.162
7 978 ms 597 ms 599 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
8 622 ms 575 ms 732 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.30]
9 651 ms 403 ms 634 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.
Click to expand...

Looks very much like dslam congestion. When it is happening, dial up a guest@telkomadsl (password is guest) pppoe session from your pc, and ping the default gateway/remote end of your pppoe session, or traceroute to 196.25.1.1, and compare the first latency you see to hop 2 in the traceroute you do just before connecting as guest. If it looks similar, dslam is congested in evenings due to demand from your neighbours.
 
ranger said:
Looks very much like dslam congestion. When it is happening, dial up a guest@telkomadsl (password is guest) pppoe session from your pc, and ping the default gateway/remote end of your pppoe session, or traceroute to 196.25.1.1, and compare the first latency you see to hop 2 in the traceroute you do just before connecting as guest. If it looks similar, dslam is congested in evenings due to demand from your neighbours.
Click to expand...

Thanks. I think it is. Anything You can do to help with this congestion?
 
My telkom ticket has been open for 6 weeks now. Speeds are shocking atm. Guy came out and said nothing wrong yet my line speed and ping changes more than Zumas wife's.

I have a escalated again bit no response. @ranger can you maybe assist please?
 
MickZA said:
... I'll schedule a couple of linux torrents for nightsurfer tonight to see if my speed problem there has been resolved.
Click to expand...

Traffic.jpg

Nightsurfer p2p speeds still fubar, normal torrent download speed set at 215kB/s switching to 585kB/s between 23:30 and 07:00 for nightsurfer. Only 2 torrents from 14 completed.

@ranger, I'll see if I can set up smokeping for tonights run to check for local congestion.

BTW just to recap: up until mid December p2p would hit max speed around 01:00 and stay there until all well seeded torrents had completed - torrent mix has not changed.
 
Last edited:
ranger said:
We don't block p2p, and have never blocked p2p for users in quota/not in FUP. In the past, we have blocked p2p for users over quota or in FUP (and the AUP/FUP makes provision for it).

We do however shape p2p for soft-cap accounts to the same extent as uncapped. This is supposed to change quite soon.



Yes, except for p2p (unless you have an unshaped capped account which always has higher priority than anything). Again, that will change in a month or two.



No, there is currently no way the billing system can tell us that an account is in contract or not ... we only get suspended/unsuspended/cancelled/upgrade/downgrade requests.
Click to expand...

Thanks a lot ranger, I appreciate the info. At least I can understand the situation. I suppose that although they're not intentionally blocking P2P, they've shaped it to the point where zero throughput is possible.

Unfortunately, since this is a 24 month contract, I only have a couple of days left to get out of it.

I can't wait a couple of months for this to possibly be fixed or adjusted, as I only have a couple of days to get out of this contract. It's sad because if it weren't for this, Smart Home Advanced would have been perfect for me.

Thank you CPA. :)
 
So yesterday I changed my account from do Uncapped 4meg to a do Uncapped Premium Plus 10meg as my line is 10meg. I found that streaming was slower esp if i stream the Red Bull TV channel on xbox. Do I fall under different shaping policy now?

Pineslopes
 
Last edited:
Anyone know how to gwt hold of @Telkom in anyway... I have had an intermittant line for 6 months. My noise level and attenuation is ridiculous. But just xannot get any answers out of anybody.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X