Afrihost CAPPED ADSL Feedback (MTN)

Status
Not open for further replies.
Other than that initial 20 minute burst it's back to crap now!! Barely 10% of max line speed!!! :mad:

View attachment 166401

Also getting slow speeds on my downloads today. Line not running at 100% today.

The speeds will still not be as good as it should be, our Team is pushing hard to get the network management improvements in place and operational as quickly as possible.
 
The speeds will still not be as good as it should be, our Team is pushing hard to get the network management improvements in place and operational as quickly as possible.

Are we talking of Minutes, Hours or Days?

In other words should I persist and wait for the current download to complete, abort and try again later today or just give up, head to the Golf Course and worry about it tomorrow?
 
Are we talking of Minutes, Hours or Days?

In other words should I persist and wait for the current download to complete, abort and try again later today or just give up, head to the Golf Course and worry about it tomorrow?

I am certainly optimistic that we will get it done today still!

Not that I think a round of golf is a bad idea... ;)
 
The previous changes and updates were routine and should not have affected performance at all, in fact it should have resulted in increased bandwidth overhead.

I'm sad to say this was not the case, and now we are busy correcting this, to ensure that we do get the performance out of our network that our clients expect.

Although intensions were good it was still an IMACD Change. If it worked out, a win for Afrihost (and the clients actually see that AH is trying to improve the experience to the client), if it didn't (in this case) then everybody is aware of the issue, instead of ranting for 3 days about Afrihost's poor service!

I'm not sure why your response wasn't something more like "That is actually a good idea and I'll take it further with management to investigate the possibility of such a communication"?
 
I'm starting to wonder if the "network management software" hasn't been the biggest problem all along. It's obviously a severely flaky solution if it takes the better part of a day to reload and causes issues like this in the first place.
 
I'm starting to wonder if the "network management software" hasn't been the biggest problem all along. It's obviously a severely flaky solution if it takes the better part of a day to reload and causes issues like this in the first place.

The previous bandwidth issue was definitely caused by the lack of IPC capacity, our Shaping and Bandwidth management system is unique, and differs completely from most other ISPs. This is awesome as it makes our Uncapped accounts uniquely different from most other ISPs, but it does mean at times it takes a bit longer to troubleshoot and correct any issues.
 
Although intensions were good it was still an IMACD Change. If it worked out, a win for Afrihost (and the clients actually see that AH is trying to improve the experience to the client), if it didn't (in this case) then everybody is aware of the issue, instead of ranting for 3 days about Afrihost's poor service!

I'm not sure why your response wasn't something more like "That is actually a good idea and I'll take it further with management to investigate the possibility of such a communication"?

The lack of communication is definitely not on purpose, it is something I think we can improve on, and it is something I am trying to change. I do agree with you that keeping our clientbase up to date can definitely help in situations such as the one we are experiencing now.
 
Last edited:
Crumbs... anyone having Afrihost authentication issues?

Cannot authenticate on either of my AH Capped accounts.

I just checked, there doesn't appear to be any authentication issues on our network, could you quickly shoot me your usernames so that I can check up on this.
 
Most recent speedtest from our 40Mb line in PE.



Tracing route to afrihost.com [197.242.144.102]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms [192.168.4.253]
2 9 ms 8 ms 9 ms 105-236-10-65-esr-lo.mtnbusiness.co.za [105.236.10.65]
3 34 ms 33 ms 34 ms 41.181.221.254
4 33 ms 33 ms 33 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 34 ms 34 ms 34 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 34 ms 34 ms 34 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
7 49 ms 49 ms 52 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]
8 59 ms 59 ms 58 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.221]
9 65 ms 65 ms 64 ms 196.31.220.10
10 55 ms 56 ms 56 ms 196.31.220.21
11 57 ms 57 ms 57 ms 196.31.63.202
12 49 ms 49 ms 49 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
13 58 ms 57 ms 57 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.
 
I feel you. I've been told that I live in JHB so many times that I've stopped bothering reporting it as an issue.

Maybe the Ghost in the Machine is telling you subtly to move to Johannesburg. ;)

On a more serious note, is the routing on your Afrihost account running through Cape Town or Johannesburg?
 
Last edited:
Maybe the Ghost in the Machine is telling you subtly to move to Johannesburg. ;)

On a more serious note, is the routing on your Afrihost account running through Cape Town or Johannesburg?

When I tells I live in JHB or when it tells me I live in CPT? Honestly I'm not really phased. I just assumed that it had something to do with blocks of IP's being handed out. After a while it sorts it's self out.

Besides when it thinks I live in JHB and I do a speed test to cpt I get 11 ping over 750km! Pretty good going if you ask me :P
 
Most recent speedtest from our 40Mb line in PE.



Tracing route to afrihost.com [197.242.144.102]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms [192.168.4.253]
2 9 ms 8 ms 9 ms 105-236-10-65-esr-lo.mtnbusiness.co.za [105.236.10.65]
3 34 ms 33 ms 34 ms 41.181.221.254
4 33 ms 33 ms 33 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 34 ms 34 ms 34 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 34 ms 34 ms 34 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
7 49 ms 49 ms 52 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]
8 59 ms 59 ms 58 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.221]
9 65 ms 65 ms 64 ms 196.31.220.10
10 55 ms 56 ms 56 ms 196.31.220.21
11 57 ms 57 ms 57 ms 196.31.63.202
12 49 ms 49 ms 49 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
13 58 ms 57 ms 57 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

My solution has now been to connect with a Webafrica account. I hope Afrihost has this resolved by next week.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X