plugger123
Senior Member
- Joined
- Apr 26, 2005
- Messages
- 520
- Reaction score
- 11
4MB Capped 12:30pm extremely slow. Anybody else having this?
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
I was just about to get this. Isn't this supposed to be full line speed at all times?
I have the same very slow speeds on Afrihost Business Uncapped![]()
same problem here :/
What is the max utilization percentage on the three IPC nodes during the day respectively.
Have also experienced slow capped Afrihost accounts for the last month at two different clients in CPT.
I have the same problem. Mostly evenings and weekend. Worse in bad weather. I've logged a call for this already. Twice. No improvement. I am on a 10 Meg capped account but I can just as well downgrade to a 1 or 2 meg. It is much worse than my experiende wtih MWEB and Cybersmart.
View attachment 85935
View attachment 85937
I know this is going to be painful to hear but disconnecting Afrihost and connecting with 4MB Telkom uncapped solved the speed issue. This could only mean it was coming from Afrihost.
In all fairness this is not a common occurrance, just a hair-pulling experience when you need to do something urgently and the reason you have a capped account is to avoid a slow connection. The main reason I use capped accounts is to be able to download that email quickly when I need it or download an update or software when I urgently need it... or view that web page to give me the info I need quickly.
The percentages change on the network depending on the usage patterns - I can't discuss numbers I'm afraid. We don't slow down any of our Capped accounts, ever![]()
Dear Afrihost.
I can confirm I had the exact same problem as OP, at around the same time (13:20).
Ping tests showed severe packet loss (28 % ~ 70 packets sent). Testing with the Telkom guest account showed zero packet loss.
Speed test was also a disaster (0.4Mbps down on a 10Mbps line), but with telkom guest full speed was observed.
There was most certainly some sort of issue somewhere.
However, when I tested again, around 6 PM, all was fine.