Telkom Internet Capped/Uncapped User Feedback (Pt2)

The quota will probably only occur on first correct mobile authentication (that was the way it was when I left, there were plans to change that, but I guess not finished yet.).

Please do the last two checks in my previous post.
Thanks for your help. I will look into it. I did log a fault with them.
 
When FUP is not currently applied, shaped traffic protocols are not shaped (so your uncapped account behaves like a SoftCap account) while the priority pass is active.

When FUP is being applied (IOW between 19h00 and 21h00 while on FUP level 1), your account won't be throttled while the priority pass is active.

Concrete example:
- You have 2Mbps uncapped
- You reached more than 90GB outside NightSurfer time this month at 19:30
- At 19:30, you are throttled to 1Mbps (having been limited to 2Mbps before that)
- At 20:30, you use a priority pass
- The portal shows you that you have an active priority pass that expires at 21h30
- From 20:30 to 20:59:59 you are no longer throttled as if you were not in FUP1 (you are limited to 2Mbps as usual)
- From 21:00:00 until 21:29:59 your torrents are not shaped
- From 21:30 your torrents may be shaped if there is high demand.

Changes are immediate/exact, however existing "flows" (e.g. tcp connections, or udp packets with same source/dest ip/port) may not be changed immediately. So, e.g. if you had a single-TCP connection download running (e.g. FTP), I hope it is resumeable ...

Clear? Make sense?
I'm on 40 uncapped home, but my international have been poor. What is the max usage per day or pm. I also an issue on my line which I also logged a call for.
 
I'm on 40 uncapped home, but my international have been poor. What is the max usage per day or pm. I also an issue on my line which I also logged a call for.
What does customerportal.telkomsa.net say?

If it doesn't say anything about FUP, your problem is not related to throttling.

(It may be due to shaping as a result of demand exceeding capacity, and traffic with higher latency would be affected more by shaping due to the way mosy TCP congestion control algorithms work. But it could also be congestion somewhere beyond Telkom Internet's control. mtr / traceroutes may help narrow it down).

(FUP1 is at 50%, so the doughnut would have to be half full of colour - I think orange?).
 
(The MyBB app seems to be having an issue with acknowledgement of new comments)
 
Last edited:
What does customerportal.telkomsa.net say?

If it doesn't say anything about FUP, your problem is not related to throttling.

(It may be due to shaping as a result of demand exceeding capacity, and traffic with higher latency would be affected more by shaping due to the way mosy TCP congestion control algorithms work. But it could also be congestion somewhere beyond Telkom Internet's control. mtr / traceroutes may help narrow it down).

(FUP1 is at 50%, so the doughnut would have to be half full of colour - I think orange?).
Donut is fine, could be my line though. Why would Telkom run out of capacity when they upgraded the MSAN and rolling out fibre. Does not make sense or am I missing something.

International cables are running circles around us and yet no ISP have enough capacity, especially the south which is almost dead from 7pm till 10pm
 
Donut is fine, could be my line though. Why would Telkom run out of capacity when they upgraded the MSAN and rolling out fibre. Does not make sense or am I missing something.

The current costing/funding model used for broadband services is broken. It may have maybe made sense in the SAIX-usage (pre-IPConnect) days.

At present, the broadband speed-based "rental" funds the backhaul (costed using contention ratios), and bandwidth is provisioned accordingly. The problem comes in when usage exceeds the "planned" usage, and there is insufficient capacity, there is no business case for the product im question to incur more costs, because the revenue can't increase by doing so (of course, revenue may decrease if you don't).

There were talks of changing this, having e.g. IPComnect fund the backhaul. In thos case, there is a no-brainer business case, as backhaul upgrades will lead to more IPC capacity sold.

But, you may have to comvince 2 product managers that only one of them now has a job ...

(These are the kinds of reasons I left, people know what the right thing to do is, but can't communicate it to management, or management doesn't try and understanf or doesn't care. Hopefully the people who are left will eventually manage to get the correct decisions taken).

International cables are running circles around us and yet no ISP have enough capacity, especially the south which is almost dead from 7pm till 10pm

1)It's a very competitive market
2)Uncapped is difficult to get right. The current FUP thresholds may be a bit too high with current input costs and product prices, but Telkom Internet was the first ISP to comprehensively and accurately piblicly disclose their full FUP policy, so at the time we maybe didn't have quite enough data to make the nest decision. Maybe we listened to existing customers too much and didn't model enough?
3)At Telkom Internet's volumes and with the staff attrition at Wholesale/Openserve, there can be huge (many-month) delays between ordering and getting IPConnect (or in Telkom Internet's case, also national amd international, since they must ask Openserve first) capacity.

In the lead-up to migrating to IPC, we needed 6 weeks from.ordering to getting capacity. The last upgrades I was around for were ordered 4 months before we needed it, and delivered more than 6 months later than required.
 
Sorry if this has been discussed but I'm to lazy to read and don't have the patience to read now. I'm getting abnormal high ping during peak hours. I'm on 20mb/10mb fibre connection

here is a traceroute of the server I'm having issues with. It also affect some international servers but can't test that now as I don't have the ip address. For example playing Rainbow six siege getting 174ping during off peak hours but during peak hours anything from 6:30pm onwards I'm getting 240-300ms ping.

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.174]
2 * * * Request timed out.
3 5 ms 6 ms 5 ms 105-187-232-57.telkomsa.net [105.187.232.57]
4 5 ms 5 ms 6 ms 105-187-232-194.telkomsa.net [105.187.232.194]
5 9 ms 8 ms 8 ms ipc-aggr-1.north.telkomsa.net [105.224.0.13]
6 55 ms 51 ms 45 ms jb1.telkomsa.net [105.187.252.102]
7 53 ms 53 ms 55 ms 196-60-9-24.ixp.joburg [196.60.9.24]
8 59 ms 56 ms 55 ms core-access-switch1.jnb1.host-h.net [197.189.193.1]
9 52 ms 49 ms 50 ms row-access-switch1-row11-12.jnb1.host-h.net [197.189.193.41]
10 55 ms 48 ms 44 ms 129.232.206.41
 
WOW thanks for making my experience in Counter Strike suck

2 11 ms 11 ms 11 ms nngy-ip-bb-1.east.dsl.telkomsa.net [105.224.124.1]
3 460 ms 697 ms 702 ms 105-187-232-137.telkomsa.net [105.187.232.137]
4 15 ms 14 ms 12 ms 105.229.0.170
5 13 ms 12 ms 13 ms cust-aggr-1.east.telkomsa.net [105.229.0.29]
6 26 ms 26 ms 26 ms cen-pr-02-be200-vl1.net.telkomsa.net [105.228.0.17]
7 26 ms 25 ms 25 ms cen-pr-02-be200-vl1.net.telkomsa.net [105.228.0.17]
8 26 ms 27 ms 26 ms 105-187-252-98.ti-sen.telkomsa.net [105.187.252.98]
9 26 ms 26 ms 26 ms 196-60-9-22.ixp.joburg [196.60.9.22]
10 40 ms 45 ms 42 ms 192.168.210.39
11 27 ms 26 ms 27 ms 155.133.238.58

Trace complete.
 
Telkom portal seems to be down system wise my side and then telkom connection limited to around 5k a second... issues in Durban here.

Tracing route to facebook.com [31.13.90.36]
over a maximum of 30 hops:

2 * * * Request timed out.
3 1840 ms 255 ms 36 ms 105-187-232-130.telkomsa.net [105.187.232.130]
4 50 ms 89 ms 218 ms cust-aggr-2.east.telkomsa.net [105.229.0.13]
5 432 ms 110 ms 673 ms ndn-ip-hsll-1.telkom-ipnet.co.za [165.165.235.173]
6 1186 ms 252 ms 294 ms ndn-ip-bpe-2-tengig-0-1-0-3.telkom-ipnet.co.za [196.43.51.245]
7 248 ms 228 ms 203 ms ndn-ip-p-1-tgig-0-4-3-0.telkom-ipnet.co.za [41.147.240.53]
8 219 ms 1074 ms 227 ms wblv-ip-p-1-pos-0-4-0-0.telkom-ipnet.co.za [41.147.240.21]
9 328 ms 380 ms 560 ms lon-ip-bpe-1-bundle-pos-202.telkom-ipnet.co.za [41.147.242.38]
10 1013 ms 531 ms 518 ms lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.43.9.58]
11 332 ms 203 ms 226 ms linx.br02.lhr1.tfbnw.net [195.66.225.121]
12 1372 ms 2007 ms 917 ms po161.asw02.lhr6.tfbnw.net [31.13.31.100]
13 364 ms 556 ms 276 ms po243.psw04.lhr3.tfbnw.net [157.240.42.169]
14 1185 ms 1634 ms 444 ms 173.252.67.189
15 260 ms 616 ms 260 ms edge-star-mini-shv-01-lhr3.facebook.com [31.13.90.36]

W.o.w. Guess its time to head outside today.
 
Last edited:
WOW thanks for making my experience in Counter Strike suck

2 11 ms 11 ms 11 ms nngy-ip-bb-1.east.dsl.telkomsa.net [105.224.124.1]
3 460 ms 697 ms 702 ms 105-187-232-137.telkomsa.net [105.187.232.137]
4 15 ms 14 ms 12 ms 105.229.0.170
5 13 ms 12 ms 13 ms cust-aggr-1.east.telkomsa.net [105.229.0.29]
6 26 ms 26 ms 26 ms cen-pr-02-be200-vl1.net.telkomsa.net [105.228.0.17]
7 26 ms 25 ms 25 ms cen-pr-02-be200-vl1.net.telkomsa.net [105.228.0.17]
8 26 ms 27 ms 26 ms 105-187-252-98.ti-sen.telkomsa.net [105.187.252.98]
9 26 ms 26 ms 26 ms 196-60-9-22.ixp.joburg [196.60.9.22]
10 40 ms 45 ms 42 ms 192.168.210.39
11 27 ms 26 ms 27 ms 155.133.238.58

Trace complete.

Yeah, I don't even attempt multiplayer racing of any kind either.
 
Telkom portal seems to be down system wide and then telkom connection limited to around 5k a second... issues in Durban here.
Checked mine roughly the same time as your post and it was working just fine.
 
Checked mine roughly the same time as your post and it was working just fine.

Thanks bwana, adjusted. It said system down on the screen. Speeds improved too. edit: wait no.... system still down this side for their portal. Speeds improved though. Naa youtube is also bust, can't stream anything. Amazed this site works. Perhaps international issues but that wouldn't explain high pings locally though on the trace routes right?
 
Last edited:
My internet is so slow. ping to 8.8.8 is 108ms and international is 311ms

C:\Users\Nelis>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 RT-AC88U-96D8 [192.168.1.174]
2 * * * Request timed out.
3 * * * Request timed out.
4 58 ms 60 ms 56 ms 105.224.0.162
5 56 ms 56 ms * ipc-aggr-1.north.telkomsa.net [105.224.0.13]
6 * * * Request timed out.
7 99 ms 99 ms 106 ms google.ixp.joburg [196.60.8.166]
8 108 ms * 108 ms 72.14.239.35
9 108 ms 108 ms 108 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

C:\Users\Nelis>ping 8.8.8.8 -t

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=108ms TTL=55
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=108ms TTL=55
Reply from 8.8.8.8: bytes=32 time=108ms TTL=55
Reply from 8.8.8.8: bytes=32 time=108ms TTL=55
Reply from 8.8.8.8: bytes=32 time=108ms TTL=55
Reply from 8.8.8.8: bytes=32 time=108ms TTL=55
Request timed out.

Ping statistics for 8.8.8.8:
Packets: Sent = 9, Received = 6, Lost = 3 (33% loss),
Approximate round trip times in milli-seconds:
Minimum = 108ms, Maximum = 108ms, Average = 108ms
Control-C
^C
C:\Users\Nelis>ping bbc.co.uk -t

Pinging bbc.co.uk [151.101.64.81] with 32 bytes of data:
Reply from 151.101.64.81: bytes=32 time=108ms TTL=56

Ping statistics for 151.101.64.81:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 108ms, Maximum = 108ms, Average = 108ms
Control-C
^C
C:\Users\Nelis>ping guru3d.com -t

Pinging guru3d.com [89.188.28.131] with 32 bytes of data:
Reply from 89.188.28.131: bytes=32 time=312ms TTL=50
Reply from 89.188.28.131: bytes=32 time=311ms TTL=50
Reply from 89.188.28.131: bytes=32 time=311ms TTL=50
Reply from 89.188.28.131: bytes=32 time=311ms TTL=50

Ping statistics for 89.188.28.131:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 311ms, Maximum = 312ms, Average = 311ms
 
Top
Sign up to the MyBroadband newsletter
X