Telkom Internet Uncapped User Feedback.

Status
Not open for further replies.
ranger said:
Been very busy.

There were some bugs in the traffic management policy delivered by the vendor that was deployed on the weekend. It also resulted in excessive resource utilisation on Monday afternoon and evening (causing the slow response). Bugfixes (some supplied by us and vetted by the vendor, some supplied by the vendor) we deployed yesterday around 14h00 to prevent hitting the high CPU utilisation.

The bugfixes resulted in an unexpected change (the traffic management policy is now working exactly, whereas previously it was over-shooting by 10%). Unfortunately, the behaviour could not be verified in QA, as we are missing one component that is related in this interaction (we will add this component to QA before we make any further changes).

We were informed by the call centre around 22h30, and increased the bandwidth values by 10% last night at 23h00 to accommodate this difference.

Unfortunately, I made a one-character typo when implementing in Bellville, which resulted in very little traffic going through the site. It took a while to show up, and I fixed it as soon as I noticed it.

The experience in Gauteng looks good, and the numbers in Bellville look very similar, but we will keep an eye on it today.

Please keep providing feedback. Other people are also reading the thread, and even if I don't always reply, the feedback does help us improve the experience you receive.
Click to expand...

Quoting incase others missed this post :).

Thanks once again for providing feedback, sounds like that vendor needs a kick up the rear :D.
 
Hi. So does this mean the Cape Town IPC upgrade is done? but not enough band width was allocated to the Northern suburbs?

ranger said:
Been very busy.

There were some bugs in the traffic management policy delivered by the vendor that was deployed on the weekend. It also resulted in excessive resource utilisation on Monday afternoon and evening (causing the slow response). Bugfixes (some supplied by us and vetted by the vendor, some supplied by the vendor) we deployed yesterday around 14h00 to prevent hitting the high CPU utilisation.

The bugfixes resulted in an unexpected change (the traffic management policy is now working exactly, whereas previously it was over-shooting by 10%). Unfortunately, the behaviour could not be verified in QA, as we are missing one component that is related in this interaction (we will add this component to QA before we make any further changes).

We were informed by the call centre around 22h30, and increased the bandwidth values by 10% last night at 23h00 to accommodate this difference.

Unfortunately, I made a one-character typo when implementing in Bellville, which resulted in very little traffic going through the site. It took a while to show up, and I fixed it as soon as I noticed it.

The experience in Gauteng looks good, and the numbers in Bellville look very similar, but we will keep an eye on it today.

Please keep providing feedback. Other people are also reading the thread, and even if I don't always reply, the feedback does help us improve the experience you receive.
Click to expand...
 
Yes very slow here in Strand, Helderberg, Cape Town area. Using my Afrihost prepaid now which seems better. Is there a problem?

And all service consultants busy at TI.
 
FFS now they say my 4Mbit uncapped is throttled, but TI usage says green normal user and Saix shows I used 66GB. WTF? Still on the phone got transferred to fnw
 
nazz said:
FFS now they say my 4Mbit uncapped is throttled, but TI usage says green normal user and Saix shows I used 66GB. WTF? Still on the phone got transferred to fnw
Click to expand...

Ok my account is not throttled and Telkom have network outage / problems in the Western Cape areas. When I asked about refund for downtime I was explained that they will automatically refund me for the downtime. wtf hehe.
 
@ranger, my internet was still crawling this morning when I left home. Durban.
 
@Ranger

Getting similar issues to what I had with Edit Dota 2 latency issues is back. High latency in Teamspeak but tracert is fine.
See: http://postimg.org/image/egk3muic1/

Then compare to tracert:
Tracing route to chat.wage.co.za [41.185.60.13]
over a maximum of 30 hops:

1 13 ms 10 ms 11 ms 224-80-1.dsl.subscriber.telkomsa.net [105.224.80
.1]
2 10 ms 13 ms 11 ms 226-0-6.dsl.subscriber.telkomsa.net [105.226.0.6
]
3 10 ms 10 ms 10 ms 226-0-13.dsl.subscriber.telkomsa.net [105.226.0.
13]
4 11 ms 11 ms 10 ms 165.165.214.213
5 13 ms 10 ms 13 ms 196.43.52.66
6 10 ms 11 ms 10 ms wnls-cr1-vl-101.wa.co.za [196.220.59.225]
7 13 ms 11 ms 11 ms 41.185.60.13
 
Last edited:
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X