Afrihost Business Uncapped Feedback

Status
Not open for further replies.
jeanres said:
@i.got~issues leave the other account connected for a hour or so, and run a speed test, I think you might be on the Wynberg exchange which is congested.
Click to expand...

I am using the WebAfrica account and have been since yesterday.
ZERO ISSUES.

The Afrihost Business account is being used by a friend in Muizenburg ... since yesterday.
Same issues as I experienced.

The AH speedtest was done by her and that is her result.
 
i.got~issues said:
Those where to the MTN speedtest server... this is to the Vodacom one...

View attachment 108040

View attachment 108038
Click to expand...

I was talking about the 130ms one from AH. Seems fishy to me.

Now that we've ruled out your line, I think we can say something is up with the account between your house and the internet. Possibly the IPC, yes, but it could also be something else.
 
Zertop said:
I was talking about the 130ms one from AH. Seems fishy to me.

Now that we've ruled out your line, I think we can say something is up with the account between your house and the internet. Possibly the IPC, yes, but it could also be something else.
Click to expand...

How long have you been at Afrihost? Did you get a nice bonus last year?
 
cortexenslaver said:
I woke up this morning AGAIN to find that AH put another new staffer on my ticket, and he decided at 01:00 this morning that my attenuation was a bit high.............. so he dropped my line speed to 8MB :wtf:

There was, and IS nothing wrong with my line! Read ALL the comments on the ENTIRE ticket before making useless assumptions, and ridiculous suggestions AH!

The only account that does not work properly is AH Business Uncapped.... ALL other ISP accounts work perfectly on my line.... even the AH 1GB free works perfectly. I have asked for over 2 weeks for a new 10MB Business Uncapped account to test, but this gets ignored and side-stepped.
Click to expand...

This should have been dealt with by our Critical Care team, and it looks like it somehow went to the general support floor. I've asked the department manager to look into this and take over the enquiry :(
 
Chevron said:
How long have you been at Afrihost? Did you get a nice bonus last year?
Click to expand...

Me, around - well... nothing.

Come on Chevron, explain to me the high ping to the AH account? Yes - the IPC is congested (explaining the slow speeds), however 130ms to CPT? Come on....

We know its not the line, but surely something could be wrong with the path taken?
 
Seems MTN is experiencing latency issues:

Tracing route to 41.221.0.33 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.2.254
2 6 ms 5 ms 5 ms 105-236-6-129-esr-lo.mtnbusiness.co.za [105.236.6.129]
3 310 ms 120 ms 11 ms 41.181.221.250
4 140 ms 196 ms 191 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
5 10 ms 9 ms 9 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
6 191 ms 9 ms 9 ms 41.181.139.109
7 446 ms 130 ms 174 ms rrba-ip-se-2-wan.telkom-ipnet.co.za [196.25.58.17]
8 12 ms 9 ms 8 ms 196.43.25.137
9 235 ms 219 ms 254 ms 196.43.39.166
10 376 ms 407 ms 353 ms ecn-telecommunications-gw.telkom-ipnet.co.za [196.25.8.42]
11 339 ms 362 ms 346 ms 41.221.0.2
12 279 ms 296 ms 304 ms 41.221.0.33

The exchange is fine as can be seen from hop 2. It’s definitely a problem at MTN

Reply from 197.242.89.170: bytes=32 time=27ms TTL=49
Reply from 197.242.89.170: bytes=32 time=259ms TTL=49
Reply from 197.242.89.170: bytes=32 time=28ms TTL=49
Reply from 197.242.89.170: bytes=32 time=297ms TTL=49
Reply from 197.242.89.170: bytes=32 time=27ms TTL=49
Reply from 197.242.89.170: bytes=32 time=363ms TTL=49
Reply from 197.242.89.170: bytes=32 time=28ms TTL=49
Reply from 197.242.89.170: bytes=32 time=28ms TTL=49
Reply from 197.242.89.170: bytes=32 time=249ms TTL=49
Reply from 197.242.89.170: bytes=32 time=29ms TTL=49
Reply from 197.242.89.170: bytes=32 time=300ms TTL=49
Reply from 197.242.89.170: bytes=32 time=30ms TTL=49
Reply from 197.242.89.170: bytes=32 time=358ms TTL=49
Reply from 197.242.89.170: bytes=32 time=28ms TTL=49
Request timed out.
Reply from 197.242.89.170: bytes=32 time=28ms TTL=49
Reply from 197.242.89.170: bytes=32 time=301ms TTL=49
Reply from 197.242.89.170: bytes=32 time=28ms TTL=49
Reply from 197.242.89.170: bytes=32 time=316ms TTL=49
Reply from 197.242.89.170: bytes=32 time=28ms TTL=49
Reply from 197.242.89.170: bytes=32 time=392ms TTL=49
Reply from 197.242.89.170: bytes=32 time=28ms TTL=49

Ping statistics for 197.242.89.170:
Packets: Sent = 206, Received = 203, Lost = 3 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 416ms, Average = 161ms
 
Zertop said:
Yea, thats what its saying :/ However - Afrihost ordered new bandwidth last year october, when they saw an increase, however - Telkom has not yet fulfilled their order.

Also - in order to make sure the new bandwidth makes a difference, they have just placed an order for even more bandwidth than what was originally ordered.
Click to expand...

So they order bandwidth. it doesn't come. They continue to sign up new clients. And the existing clients are still charged full price for their "premium" product which is in all honestly no better than the normal product. ISP business really is a win-win for the ISP.
 
savage said:
If you CANT deliver on your high quality service, why MUST we continue to pay for this high quality service? ***** happens, Telkom screwed you, it happens all the time. Why must WE pay for it?
Click to expand...

Because Profit!
 
i.got~issues said:
I am using the WebAfrica account and have been since yesterday.
ZERO ISSUES.

The Afrihost Business account is being used by a friend in Muizenburg ... since yesterday.
Same issues as I experienced.

The AH speedtest was done by her and that is her result.
Click to expand...
Also resorted to an IS based account the last 2 days, which was provided by a friendly MyBB member.

It is an uncapped test account.
I haven't really checked it, but I think it is a bit shaped during the day, but I haven't seen speeds slower than about 250kB/s during the day on Http downloads and most of the time it is higher.
From about 18:00 is full line speed on my 4Mbps line.

Unfortunately it will only last another couple of days, hopefully long enough to let my stress & agro levels drop to fight my AH account again in the new month.

I only now realize how much this AH experience is working me up.
I must add that I have a couple of TI bull**** behind me as well.
 
i.got~issues said:
Gosh, you took a break from streaming twitch on WA to post here.


You sure your costume fits OK. :D
Click to expand...

Why did you create that? I've been recommending any account that's been better than Afrihost lately. For those that don't want stars I recommend Axxess.

Unlike Zertop's blind allegiance.
 
Yep, its screwed:

Pinging 105.236.6.129 with 32 bytes of data:
Reply from 105.236.6.129: bytes=32 time=271ms TTL=254
Reply from 105.236.6.129: bytes=32 time=7ms TTL=254
Reply from 105.236.6.129: bytes=32 time=306ms TTL=254
Reply from 105.236.6.129: bytes=32 time=342ms TTL=254
Reply from 105.236.6.129: bytes=32 time=6ms TTL=254
Reply from 105.236.6.129: bytes=32 time=433ms TTL=254
Reply from 105.236.6.129: bytes=32 time=7ms TTL=254
Reply from 105.236.6.129: bytes=32 time=123ms TTL=254
Reply from 105.236.6.129: bytes=32 time=236ms TTL=254
Reply from 105.236.6.129: bytes=32 time=41ms TTL=254
Reply from 105.236.6.129: bytes=32 time=205ms TTL=254
Reply from 105.236.6.129: bytes=32 time=6ms TTL=254
Reply from 105.236.6.129: bytes=32 time=238ms TTL=254
Reply from 105.236.6.129: bytes=32 time=271ms TTL=254
Reply from 105.236.6.129: bytes=32 time=193ms TTL=254
Reply from 105.236.6.129: bytes=32 time=292ms TTL=254
Reply from 105.236.6.129: bytes=32 time=91ms TTL=254
Reply from 105.236.6.129: bytes=32 time=242ms TTL=254
Reply from 105.236.6.129: bytes=32 time=8ms TTL=254
Reply from 105.236.6.129: bytes=32 time=312ms TTL=254
Reply from 105.236.6.129: bytes=32 time=320ms TTL=254
Reply from 105.236.6.129: bytes=32 time=129ms TTL=254
Reply from 105.236.6.129: bytes=32 time=380ms TTL=254
Reply from 105.236.6.129: bytes=32 time=8ms TTL=254
Reply from 105.236.6.129: bytes=32 time=139ms TTL=254
Reply from 105.236.6.129: bytes=32 time=6ms TTL=254
Reply from 105.236.6.129: bytes=32 time=209ms TTL=254
Reply from 105.236.6.129: bytes=32 time=6ms TTL=254
Reply from 105.236.6.129: bytes=32 time=278ms TTL=254
Reply from 105.236.6.129: bytes=32 time=309ms TTL=254

Ping statistics for 105.236.6.129:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 433ms, Average = 180ms
 
Superspeed said:
Yep, its screwed:

Pinging 105.236.6.129 with 32 bytes of data:
Reply from 105.236.6.129: bytes=32 time=271ms TTL=254
Reply from 105.236.6.129: bytes=32 time=7ms TTL=254
Reply from 105.236.6.129: bytes=32 time=306ms TTL=254
Reply from 105.236.6.129: bytes=32 time=342ms TTL=254
Reply from 105.236.6.129: bytes=32 time=6ms TTL=254
Reply from 105.236.6.129: bytes=32 time=433ms TTL=254
Reply from 105.236.6.129: bytes=32 time=7ms TTL=254
Reply from 105.236.6.129: bytes=32 time=123ms TTL=254
Reply from 105.236.6.129: bytes=32 time=236ms TTL=254
Reply from 105.236.6.129: bytes=32 time=41ms TTL=254
Reply from 105.236.6.129: bytes=32 time=205ms TTL=254
Reply from 105.236.6.129: bytes=32 time=6ms TTL=254
Reply from 105.236.6.129: bytes=32 time=238ms TTL=254
Reply from 105.236.6.129: bytes=32 time=271ms TTL=254
Reply from 105.236.6.129: bytes=32 time=193ms TTL=254
Reply from 105.236.6.129: bytes=32 time=292ms TTL=254
Reply from 105.236.6.129: bytes=32 time=91ms TTL=254
Reply from 105.236.6.129: bytes=32 time=242ms TTL=254
Reply from 105.236.6.129: bytes=32 time=8ms TTL=254
Reply from 105.236.6.129: bytes=32 time=312ms TTL=254
Reply from 105.236.6.129: bytes=32 time=320ms TTL=254
Reply from 105.236.6.129: bytes=32 time=129ms TTL=254
Reply from 105.236.6.129: bytes=32 time=380ms TTL=254
Reply from 105.236.6.129: bytes=32 time=8ms TTL=254
Reply from 105.236.6.129: bytes=32 time=139ms TTL=254
Reply from 105.236.6.129: bytes=32 time=6ms TTL=254
Reply from 105.236.6.129: bytes=32 time=209ms TTL=254
Reply from 105.236.6.129: bytes=32 time=6ms TTL=254
Reply from 105.236.6.129: bytes=32 time=278ms TTL=254
Reply from 105.236.6.129: bytes=32 time=309ms TTL=254

Ping statistics for 105.236.6.129:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 433ms, Average = 180ms
Click to expand...

Yea dude, thats your second hop :/ (usually indicating a line issue as you know :( )

What happens when you recreate your port? (Wow, I havnt given that advice in a while :D )
 
i.got~issues said:
Well PM him then. Pot and kettle syndrome.
Click to expand...

What you on about?

At least 20 people in this thread have proved the cape IPC issue, even the Afripeople themselves have acknowledged it, yet zertop still thinks not IPC issue. Either he works for AH or is retarded.

And he gave you hope wasting your time as well.

I really don't care what account you use. Some people even been praising the cybersmart business accounts.


But wasting people's time like this is just wrong.
 
Superspeed said:
Seems MTN is experiencing latency issues:

Tracing route to 41.221.0.33 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.2.254
2 6 ms 5 ms 5 ms 105-236-6-129-esr-lo.mtnbusiness.co.za [105.236.6.129]
3 310 ms 120 ms 11 ms 41.181.221.250
4 140 ms 196 ms 191 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
5 10 ms 9 ms 9 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
6 191 ms 9 ms 9 ms 41.181.139.109
7 446 ms 130 ms 174 ms rrba-ip-se-2-wan.telkom-ipnet.co.za [196.25.58.17]
8 12 ms 9 ms 8 ms 196.43.25.137
9 235 ms 219 ms 254 ms 196.43.39.166
10 376 ms 407 ms 353 ms ecn-telecommunications-gw.telkom-ipnet.co.za [196.25.8.42]
11 339 ms 362 ms 346 ms 41.221.0.2
12 279 ms 296 ms 304 ms 41.221.0.33

The exchange is fine as can be seen from hop 2. It’s definitely a problem at MTN

Reply from 197.242.89.170: bytes=32 time=27ms TTL=49
Reply from 197.242.89.170: bytes=32 time=259ms TTL=49
Reply from 197.242.89.170: bytes=32 time=28ms TTL=49
Reply from 197.242.89.170: bytes=32 time=297ms TTL=49
Reply from 197.242.89.170: bytes=32 time=27ms TTL=49
Reply from 197.242.89.170: bytes=32 time=363ms TTL=49
Reply from 197.242.89.170: bytes=32 time=28ms TTL=49
Reply from 197.242.89.170: bytes=32 time=28ms TTL=49
Reply from 197.242.89.170: bytes=32 time=249ms TTL=49
Reply from 197.242.89.170: bytes=32 time=29ms TTL=49
Reply from 197.242.89.170: bytes=32 time=300ms TTL=49
Reply from 197.242.89.170: bytes=32 time=30ms TTL=49
Reply from 197.242.89.170: bytes=32 time=358ms TTL=49
Reply from 197.242.89.170: bytes=32 time=28ms TTL=49
Request timed out.
Reply from 197.242.89.170: bytes=32 time=28ms TTL=49
Reply from 197.242.89.170: bytes=32 time=301ms TTL=49
Reply from 197.242.89.170: bytes=32 time=28ms TTL=49
Reply from 197.242.89.170: bytes=32 time=316ms TTL=49
Reply from 197.242.89.170: bytes=32 time=28ms TTL=49
Reply from 197.242.89.170: bytes=32 time=392ms TTL=49
Reply from 197.242.89.170: bytes=32 time=28ms TTL=49

Ping statistics for 197.242.89.170:
Packets: Sent = 206, Received = 203, Lost = 3 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 416ms, Average = 161ms
Click to expand...

We're busy testing on our side. While we're not seeing anything for major concern, we definitely want to make sure there is nothing wobbling on our side :(
 
Chevron said:
Why did you create that? I've been recommending any account that's been better than Afrihost lately. For those that don't want stars I recommend Axxess.

Unlike Zertop's blind allegiance.
Click to expand...

You know what. Listen here. There is a reason I stick with Afrihost. I have tried the Lot... MWEB, Axxess, TI, Openweb and WA. All of them, for me, have had some quite shocking experiences, as well as some quite good ones. However, they didn't help me when I asked, nor provided me with extras for being a customer. They blatantly treated me as a client whom they wouldn't mind losing. (This is generalising, Openweb had great support, however slow speeds.)

Yes - I do preach Afrihost quite high, not because of a "blind allegiance", but rather because EVERY single time I have an issue, EVERY single time something is wrong, they are quick to respond and quick to help (My experience over the past few months, I haven't really had any support tickets lately - so I cannot comment on their recent support structure). Yes - their network is crap at the moment, I know. But watch - when they come out of it (Like they did last time a few years ago), all the other ISP clients who left because of the bad connection will come running back. A few months ago, MWEB had issues. After them, Telkom had issues. It's a big loop.

If you are unable to look through the downfalls of a company and look towards the future. I am sorry for you. Afrihost has a plan to make it better! I don't see the need to leave now just to come back in a few months time? Stick with WebAfrica then? Really - there is no need to come into these forums and devalue a product, just because you don't like it. I know there are issues. Believe me, I am experiencing them too - however seriously, get over it? I will help people, who I think could have an issue elsewhere, whenever I like - so please stop trying to discredit my input. Yes, there is an IPC issue - however, in the case of i.got~issues - he had 1000ms ping to all of his accounts? So, I thought it could be a line issue. 20 People out of 100's of Afrihost clients active on these forums means that the issue is not completely widespread (surely??). Yes, again there are capacity issues, however is it an issue for me to try help people? Come on?

If you would like to have an argument, please PM me - I don't think the other forum members would like us to have it out in public. I would much prefer not having one, however it is up to you.

Z
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X