South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
There is a failure on the IPNet core network, affecting traffic between regions. Thus, Gauteng is worst affected on international traffic. Durban and Cape Town seem to be affected mainly for content in Gauteng, but not international content. There is no SAIX notice yet, and we haven't received any other official communication.
There is a failure on the IPNet core network, affecting traffic between regions. Thus, Gauteng is worst affected on international traffic. Durban and Cape Town seem to be affected mainly for content in Gauteng, but not international content. There is no SAIX notice yet, and we haven't received any other official communication.
There's no doubt you've been put on a 10Mb exchange with those speeds.


There is a failure on the IPNet core network, affecting traffic between regions. Thus, Gauteng is worst affected on international traffic. Durban and Cape Town seem to be affected mainly for content in Gauteng, but not international content. There is no SAIX notice yet, and we haven't received any other official communication.
lol, holding since 11:30 for cancellations....
still holding and its now 12:12. Even the crap music has stopped playing. Now I only get recorded voice every few minutes telling to please hold etc etc.
This really is a genius tactic by Telkom
Call was answered exactly after 1 hour of holding. What I do not however understand is, why must I now wait for another call to verify that I am cancelling? Especially after having to answer security questions?
Whatever you do to manage bandwidth, it should not be a surprise to the client. That's my beef.We have been working on other approaches to managing abuse on our uncapped accounts, but the development is not complete yet, so it isn't an immediate solution to current problems. However, a lot of people have complained about things like rolling windows (e.g. IS star rating), and we are hoping to not punish people who have the one bad month, but at the same time we know we need to fix the current experience. Unfortunately, the past 3 weeks haven't been very productive (too many key people on leave), so there is still a lot of work to be done.
There are some initiatives that should bear some fruit in the next 2 to 3 weeks (but these are dependent on external parties to get things in place).
Call was answered exactly after 1 hour of holding. What I do not however understand is, why must I now wait for another call to verify that I am cancelling? Especially after having to answer security questions?
Call was answered exactly after 1 hour of holding. What I do not however understand is, why must I now wait for another call to verify that I am cancelling? Especially after having to answer security questions?
I'm confused,
Why is my line streaming terribly yet the speedtest looks like this?
View attachment 116678
Afrihost capped account streaming just fine in HD.
Still getting bad lag from up north... and just a question, why do we go through India?
If I'm not mistaken, Twitch.tv uses a CDN that disables ping requests as a method of alleviating stress from their servers. This is also a simple way to prevent a mass attack of pings (DDOS).I get the same thing when I run a traceroot to twitch.tv...
...
Tracing route to twitch.tv [192.16.71.171]
over a maximum of 30 hops:
1 21 ms 13 ms 9 ms ti-224-164-01.telkomadsl.co.za [105.224.164.1]
2 57 ms 55 ms 55 ms ti-229-0-06.telkomadsl.co.za [105.229.0.6]
3 56 ms 58 ms 58 ms ti-229-0-29.telkomadsl.co.za [105.229.0.29]
4 60 ms 59 ms 62 ms tbnb-ip-hsll-1-wan.telkom-ipnet.co.za [165.165.2
35.173]
5 226 ms 227 ms 225 ms lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za [196.
43.9.46]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 ^C