Telkom Internet Capped/Uncapped User Feedback (Pt2)

R

ranger

Expert Member
Joined
May 2, 2007
Messages
2,062
ArrieOos said:
I get two different messages...

Tritracker portal says AUP (power user) and Customer portal says FUP1...
Click to expand...

As of the launch of dynamic FUP and Customer portal in Dec., tracker was deprecated and getting no new features, and the plan was going to turn it down by April 2017. That may have changed.

Tracker should mainly still work, except that it doesn't know about FUP1 and FUP2, and will show FUP3 as FUP/AUP (but e.g. acknowledgememt should work).

(With the implementation of dynamic FUP, the values where you used to hit old FUP became the new FUP1 limits, except for one or two products which deviated from the models for an unknown reason)

ArrieOos said:
1) Has the customer portal replaced the tritracker portal and
Click to expand...

For everything except where you find links to it in Customerportal:
- notification settings (was supposed to be available in customerportal by some time in March, I had seen builds with the front-end pieces by Jan.)
- prioritisation feature

ArrieOos said:
2) Is the new FUP the new name for old AUP (on tritracker)? In new policy doc FUP and AUP means different things. In new policy FUP is about use and AUP is about unlawful/unethical behavior?
Click to expand...

We had always referred to it as FUP internally, since before we migrated to IPC on 1 Feb 2013. I can't remember the exact wording in tracker and customer-facing documents, but I thought we referred to FUP ...
 
R

ranger

Expert Member
Joined
May 2, 2007
Messages
2,062
Spontaneous spinach said:
I think FUP 3 was restricted speed at a time period of 24/7, FUP 2 was 7-12
Click to expand...
FUP1: speed = 0.5 * product_speed if ((19 < hour < 21) && !prioritypass)

FUP2: speed = 0.25 * product_speed if ((18 < hour < 22) && !prioritypass)

FUP3: speed = max(0.125 * product_speed, 384k) if ((7 < hour < 23) && !prioritypass

(This is from memory. No, this isn't exactly how the code works; providing a valid implementation that would work on the platform would probably only make sense to about 15 people in SA as the proprietary DSL - domain specific language - is very specific to one vendor of one type of product, e.g. it doesn't have an if-then-else contruct most people would recognise)
 
Last edited:
H

Hummercellc

Expert Member
Joined
Jan 6, 2008
Messages
3,451
Seems Telkom are routing traffic to the IS network destined for Jo'burg via Cape Town from Durban??
Anyway to get this fixed?
Edit: I am getting the same results on DSL and LTE, going via CPT.

Telkom Account:
1 * * *
2 105-187-252-217.ti-sen.telkomsa.net (105.187.252.217) 17.673 ms 18.441 ms 18.055 ms
3 cust-aggr-2.east.telkomsa.net (105.229.0.13) 15.752 ms 18.745 ms 15.703 ms
4 105-187-252-46.ti-sen.telkomsa.net (105.187.252.46) 19.371 ms 20.167 ms 20.858 ms
5 105-187-252-46.ti-sen.telkomsa.net (105.187.252.46) 31.638 ms 30.084 ms 30.466 ms
6 196-10-140-126.ixp.capetown (196.10.140.126) 40.283 ms 42.910 ms 40.070 ms
7 mi-za-cpt-p7-te0-7-0-0.ip.isnet.net (168.209.2.12) 40.513 ms 39.867 ms 40.991 ms
8 168.209.100.101 (168.209.100.101) 67.920 ms 60.211 ms 52.130 ms
9 core1-pkl-tg0-7-0-0.ip.isnet.net (168.209.1.162) 61.107 ms 56.541 ms 52.182 ms
10 cdsl1-rba-te1-1.ip.isnet.net (196.26.0.217) 58.067 ms 60.542 ms 52.907 ms
11 clns-tt-28.isdsl.net (196.35.63.107) 53.266 ms 60.164 ms 62.133 ms


Afrihost Account:
1 * * *
2 dbn-up2.ip.adsl.co.za (169.1.5.173) 10.764 ms 10.827 ms 13.860 ms
3 dbn-up2.ip.adsl.co.za (169.1.5.174) 10.418 ms 12.501 ms 10.694 ms
4 dbn-in1.ip.adsl.co.za (169.1.5.204) 15.685 ms 14.558 ms 16.194 ms
5 169-1-21-32.ip.afrihost.co.za (169.1.21.32) 17.762 ms 19.632 ms 18.530 ms
6 is.ixp.joburg (196.60.8.126) 21.439 ms 20.057 ms 20.707 ms
7 core1-pkl-tg0-7-0-0.ip.isnet.net (168.209.1.162) 26.743 ms 25.005 ms 28.214 ms
8 cdsl1-rba-te1-1.ip.isnet.net (196.26.0.217) 29.307 ms 27.878 ms 27.070 ms
9 clns-tt-28.isdsl.net (196.35.63.107) 27.997 ms 28.869 ms 28.509 ms

Mweb Account:
1 * * *
2 197-82-5-249.dbn.mweb.co.za (197.82.5.249) 11.433 ms 10.489 ms 11.396 ms
3 501.po-channel10.trv-ipc-1.optinet.net (197.82.5.250) 15.173 ms 15.821 ms 15.189 ms
4 vl92.trv-hscore-1.optinet.net (197.82.2.3) 16.388 ms 16.809 ms 15.592 ms
5 101.te0-0-0.vic-pr-1.optinet.net (197.80.7.5) 16.990 ms 16.600 ms 18.592 ms
6 is.jinx.net.za (196.223.14.10) 16.191 ms 16.007 ms 17.790 ms
7 core1-pkl-tg0-7-0-0.ip.isnet.net (168.209.1.162) 22.396 ms 22.888 ms 23.989 ms
8 cdsl1-rba-te1-4.ip.isnet.net (168.209.1.175) 25.382 ms 24.076 ms 26.790 ms
9 clns-tt-28.isdsl.net (196.35.63.107) 27.186 ms 26.726 ms 27.193 ms
 
Last edited:
R

ranger

Expert Member
Joined
May 2, 2007
Messages
2,062
Hummercellc said:
Seems Telkom are routing traffic to the IS network destined for Jo'burg via Cape Town from Durban??
Anyway to get this fixed?
Edit: I am getting the same results on DSL and LTE, going via CPT.
Click to expand...

This can happen if the inter-site links between Gauteng and Durban are down. Those links were quite unreliable (lots of fibre breaks on the only available route).

It may be worthwhile trying a traceroute to ns2.telkomsa.net, if it goes via Cape Town, it's definitely the Gauteng->Durban circuits down.

Since Dec., Durban LTE users take the same routes.

If the issue persists for more than 24 hours, post an update, and I will ask streaker about it.
 
H

Hummercellc

Expert Member
Joined
Jan 6, 2008
Messages
3,451
ranger said:
This can happen if the inter-site links between Gauteng and Durban are down. Those links were quite unreliable (lots of fibre breaks on the only available route).

It may be worthwhile trying a traceroute to ns2.telkomsa.net, if it goes via Cape Town, it's definitely the Gauteng->Durban circuits down.

Since Dec., Durban LTE users take the same routes.

If the issue persists for more than 24 hours, post an update, and I will ask streaker about it.
Click to expand...

Thanks Ranger :)

Here is the Trace Route to ns2.telkomsa.net.
1 * * *
2 105-187-252-217.ti-sen.telkomsa.net (105.187.252.217) 14.296 ms 15.524 ms 14.677 ms
3 cust-aggr-2.east.telkomsa.net (105.229.0.13) 19.808 ms 18.037 ms 18.178 ms
4 cen-pr-01-be200-vl1.net.telkomsa.net (105.228.0.18) 28.142 ms 28.509 ms 27.550 ms
5 cen-pr-01-be200-vl1.net.telkomsa.net (105.228.0.18) 29.018 ms 29.538 ms 25.730 ms
6 ns2.telkomsa.net (105.224.1.4) 27.358 ms 28.406 ms 27.464 ms

IS traffic taking the scenic route :whistling: same as the past week.
1 * * *
2 105-187-252-217.ti-sen.telkomsa.net (105.187.252.217) 14.955 ms 16.055 ms 15.736 ms
3 cust-aggr-2.east.telkomsa.net (105.229.0.13) 17.696 ms 17.504 ms 16.055 ms
4 105-187-252-46.ti-sen.telkomsa.net (105.187.252.46) 25.797 ms 25.040 ms 26.936 ms
5 105-187-252-46.ti-sen.telkomsa.net (105.187.252.46) 27.674 ms 29.195 ms 28.941 ms
6 196-10-140-126.ixp.capetown (196.10.140.126) 40.167 ms 49.924 ms 35.892 ms
7 mi-za-cpt-p7-te0-7-0-0.ip.isnet.net (168.209.2.12) 46.899 ms 43.642 ms 44.911 ms
8 168.209.100.101 (168.209.100.101) 77.622 ms 70.563 ms 70.573 ms
9 core1-pkl-tg0-7-0-0.ip.isnet.net (168.209.1.162) 60.648 ms 61.138 ms 67.459 ms
10 cdsl1-rba-te1-1.ip.isnet.net (196.26.0.217) 63.473 ms 73.869 ms 63.934 ms
11 clns-tt-28.isdsl.net (196.35.63.107) 69.611 ms 68.574 ms 65.302 ms
 
M

Mannemarak

Well-Known Member
Joined
May 6, 2013
Messages
263
could this explain my horse ***** lag lately?

Hummercellc said:
Seems Telkom are routing traffic to the IS network destined for Jo'burg via Cape Town from Durban??
Anyway to get this fixed?
Edit: I am getting the same results on DSL and LTE, going via CPT.

Telkom Account:
1 * * *
2 105-187-252-217.ti-sen.telkomsa.net (105.187.252.217) 17.673 ms 18.441 ms 18.055 ms
3 cust-aggr-2.east.telkomsa.net (105.229.0.13) 15.752 ms 18.745 ms 15.703 ms
4 105-187-252-46.ti-sen.telkomsa.net (105.187.252.46) 19.371 ms 20.167 ms 20.858 ms
5 105-187-252-46.ti-sen.telkomsa.net (105.187.252.46) 31.638 ms 30.084 ms 30.466 ms
6 196-10-140-126.ixp.capetown (196.10.140.126) 40.283 ms 42.910 ms 40.070 ms
7 mi-za-cpt-p7-te0-7-0-0.ip.isnet.net (168.209.2.12) 40.513 ms 39.867 ms 40.991 ms
8 168.209.100.101 (168.209.100.101) 67.920 ms 60.211 ms 52.130 ms
9 core1-pkl-tg0-7-0-0.ip.isnet.net (168.209.1.162) 61.107 ms 56.541 ms 52.182 ms
10 cdsl1-rba-te1-1.ip.isnet.net (196.26.0.217) 58.067 ms 60.542 ms 52.907 ms
11 clns-tt-28.isdsl.net (196.35.63.107) 53.266 ms 60.164 ms 62.133 ms


Afrihost Account:
1 * * *
2 dbn-up2.ip.adsl.co.za (169.1.5.173) 10.764 ms 10.827 ms 13.860 ms
3 dbn-up2.ip.adsl.co.za (169.1.5.174) 10.418 ms 12.501 ms 10.694 ms
4 dbn-in1.ip.adsl.co.za (169.1.5.204) 15.685 ms 14.558 ms 16.194 ms
5 169-1-21-32.ip.afrihost.co.za (169.1.21.32) 17.762 ms 19.632 ms 18.530 ms
6 is.ixp.joburg (196.60.8.126) 21.439 ms 20.057 ms 20.707 ms
7 core1-pkl-tg0-7-0-0.ip.isnet.net (168.209.1.162) 26.743 ms 25.005 ms 28.214 ms
8 cdsl1-rba-te1-1.ip.isnet.net (196.26.0.217) 29.307 ms 27.878 ms 27.070 ms
9 clns-tt-28.isdsl.net (196.35.63.107) 27.997 ms 28.869 ms 28.509 ms

Mweb Account:
1 * * *
2 197-82-5-249.dbn.mweb.co.za (197.82.5.249) 11.433 ms 10.489 ms 11.396 ms
3 501.po-channel10.trv-ipc-1.optinet.net (197.82.5.250) 15.173 ms 15.821 ms 15.189 ms
4 vl92.trv-hscore-1.optinet.net (197.82.2.3) 16.388 ms 16.809 ms 15.592 ms
5 101.te0-0-0.vic-pr-1.optinet.net (197.80.7.5) 16.990 ms 16.600 ms 18.592 ms
6 is.jinx.net.za (196.223.14.10) 16.191 ms 16.007 ms 17.790 ms
7 core1-pkl-tg0-7-0-0.ip.isnet.net (168.209.1.162) 22.396 ms 22.888 ms 23.989 ms
8 cdsl1-rba-te1-4.ip.isnet.net (168.209.1.175) 25.382 ms 24.076 ms 26.790 ms
9 clns-tt-28.isdsl.net (196.35.63.107) 27.186 ms 26.726 ms 27.193 ms
Click to expand...
 
S

streaker

Active Member
Joined
Jan 24, 2008
Messages
47
Hummercellc,

Can you test again? Should be resolved now. We have had some issues with our peering in Durban


Hummercellc said:
Seems Telkom are routing traffic to the IS network destined for Jo'burg via Cape Town from Durban??
Anyway to get this fixed?
Edit: I am getting the same results on DSL and LTE, going via CPT.

Telkom Account:
1 * * *
2 105-187-252-217.ti-sen.telkomsa.net (105.187.252.217) 17.673 ms 18.441 ms 18.055 ms
3 cust-aggr-2.east.telkomsa.net (105.229.0.13) 15.752 ms 18.745 ms 15.703 ms
4 105-187-252-46.ti-sen.telkomsa.net (105.187.252.46) 19.371 ms 20.167 ms 20.858 ms
5 105-187-252-46.ti-sen.telkomsa.net (105.187.252.46) 31.638 ms 30.084 ms 30.466 ms
6 196-10-140-126.ixp.capetown (196.10.140.126) 40.283 ms 42.910 ms 40.070 ms
7 mi-za-cpt-p7-te0-7-0-0.ip.isnet.net (168.209.2.12) 40.513 ms 39.867 ms 40.991 ms
8 168.209.100.101 (168.209.100.101) 67.920 ms 60.211 ms 52.130 ms
9 core1-pkl-tg0-7-0-0.ip.isnet.net (168.209.1.162) 61.107 ms 56.541 ms 52.182 ms
10 cdsl1-rba-te1-1.ip.isnet.net (196.26.0.217) 58.067 ms 60.542 ms 52.907 ms
11 clns-tt-28.isdsl.net (196.35.63.107) 53.266 ms 60.164 ms 62.133 ms


Afrihost Account:
1 * * *
2 dbn-up2.ip.adsl.co.za (169.1.5.173) 10.764 ms 10.827 ms 13.860 ms
3 dbn-up2.ip.adsl.co.za (169.1.5.174) 10.418 ms 12.501 ms 10.694 ms
4 dbn-in1.ip.adsl.co.za (169.1.5.204) 15.685 ms 14.558 ms 16.194 ms
5 169-1-21-32.ip.afrihost.co.za (169.1.21.32) 17.762 ms 19.632 ms 18.530 ms
6 is.ixp.joburg (196.60.8.126) 21.439 ms 20.057 ms 20.707 ms
7 core1-pkl-tg0-7-0-0.ip.isnet.net (168.209.1.162) 26.743 ms 25.005 ms 28.214 ms
8 cdsl1-rba-te1-1.ip.isnet.net (196.26.0.217) 29.307 ms 27.878 ms 27.070 ms
9 clns-tt-28.isdsl.net (196.35.63.107) 27.997 ms 28.869 ms 28.509 ms

Mweb Account:
1 * * *
2 197-82-5-249.dbn.mweb.co.za (197.82.5.249) 11.433 ms 10.489 ms 11.396 ms
3 501.po-channel10.trv-ipc-1.optinet.net (197.82.5.250) 15.173 ms 15.821 ms 15.189 ms
4 vl92.trv-hscore-1.optinet.net (197.82.2.3) 16.388 ms 16.809 ms 15.592 ms
5 101.te0-0-0.vic-pr-1.optinet.net (197.80.7.5) 16.990 ms 16.600 ms 18.592 ms
6 is.jinx.net.za (196.223.14.10) 16.191 ms 16.007 ms 17.790 ms
7 core1-pkl-tg0-7-0-0.ip.isnet.net (168.209.1.162) 22.396 ms 22.888 ms 23.989 ms
8 cdsl1-rba-te1-4.ip.isnet.net (168.209.1.175) 25.382 ms 24.076 ms 26.790 ms
9 clns-tt-28.isdsl.net (196.35.63.107) 27.186 ms 26.726 ms 27.193 ms
Click to expand...
 
M

Mannemarak

Well-Known Member
Joined
May 6, 2013
Messages
263
just heard a radio advert for telkom 4mb, being on telkom already on 2mb uncapped, is this 4mb deal for new customers, if i heard right i'll end up saving money going to the 4mb deal

any one has a link for more info?

also what if i take said package but exchange is stuffed and 4mb ends up being sheeat
 
Last edited:
isie

isie

Honorary Master
Joined
Jan 16, 2010
Messages
12,604
Mannemarak said:
just heard a radio advert for telkom 4mb, being on telkom already on 2mb uncapped, is this 4mb deal for new customers, if i heard right i'll end up saving money going to the 4mb deal

any one has a link for more info?

also what if i take said package but exchange is stuffed and 4mb ends up being sheeat
Click to expand...

I can't get on the Telkom site but iirc its only valid till today only?
 
S

Spontaneous spinach

Expert Member
Joined
Nov 17, 2013
Messages
1,394
Mannemarak said:
just heard a radio advert for telkom 4mb, being on telkom already on 2mb uncapped, is this 4mb deal for new customers, if i heard right i'll end up saving money going to the 4mb deal

any one has a link for more info?

also what if i take said package but exchange is stuffed and 4mb ends up being sheeat
Click to expand...
Just phone an upgrade to a 4mb package , the deal is available for new and old subscribers.
 
M

Mannemarak

Well-Known Member
Joined
May 6, 2013
Messages
263
phoned, and did it :D

holding thumbs it doesnt bite me in the backside

how long generally before they flip the switch ?

:D
 
H

Hummercellc

Expert Member
Joined
Jan 6, 2008
Messages
3,451
streaker said:
Hummercellc,

Can you test again? Should be resolved now. We have had some issues with our peering in Durban
Click to expand...

Hi streaker,

Yes thank you! To you and ranger :)
latency is now 15-18ms lower, but still a tad higher than Afrihost & Mweb.

Telkom
1 * * *
2 105-187-252-217.ti-sen.telkomsa.net (105.187.252.217) 15.511 ms 16.565 ms 15.646 ms
3 cust-aggr-2.east.telkomsa.net (105.229.0.13) 19.325 ms 19.527 ms 19.019 ms
4 jb1-pr-02-te1-1-0.net.telkomsa.net (105.187.249.6) 31.055 ms 30.785 ms 31.053 ms
5 jb1-pr-02-te1-1-0.net.telkomsa.net (105.187.249.6) 31.024 ms 30.887 ms 31.120 ms
6 is.ixp.joburg (196.60.8.126) 41.498 ms 41.484 ms 45.163 ms
7 core1-pkl-tg0-7-0-0.ip.isnet.net (168.209.1.162) 47.867 ms 41.200 ms 41.372 ms
8 cdsl1-rba-te1-1.ip.isnet.net (196.26.0.217) 42.415 ms 46.506 ms 45.147 ms
9 clns-tt-28.isdsl.net (196.35.63.107) 41.779 ms 51.575 ms 41.458 ms

Afrihost
1 * * *
2 dbn-up2.ip.adsl.co.za (169.1.5.173) 12.713 ms 13.769 ms 14.830 ms
3 dbn-up2.ip.adsl.co.za (169.1.5.174) 19.554 ms 19.647 ms 19.572 ms
4 dbn-in1.ip.adsl.co.za (169.1.5.204) 19.912 ms 19.762 ms 19.683 ms
5 169-1-21-32.ip.afrihost.co.za (169.1.21.32) 22.025 ms 22.058 ms 22.005 ms
6 is.ixp.joburg (196.60.8.126) 28.439 ms 28.811 ms 29.311 ms
7 core1-pkl-tg0-7-0-0.ip.isnet.net (168.209.1.162) 28.148 ms 29.587 ms 29.010 ms
8 cdsl1-rba-te1-1.ip.isnet.net (196.26.0.217) 30.313 ms 31.573 ms 30.267 ms
9 clns-tt-28.isdsl.net (196.35.63.107) 32.024 ms 32.836 ms 31.823 ms
 
You must log in or register to reply here.
Top