Afrihost Business Uncapped Feedback

Status
Not open for further replies.
Been on the Afrihost Business account since the begining of the month, and so far its been really great. Big difference compared to the so called "premium" account I was on at Mweb. I can now actually watch a Youtube video without waiting an hour to stream. One thing though videos on Steam, especially the game trailers (which seem to be higher quality than the normal videos on Steam) , have terrible streaming issues. Watching the same video on Youtude works like a charm. Maybe this needs to be looked into?
 
Last edited:
Another week has passed and I am still without the functional premium internet I am paying for. When is this matter going to fixed?
 
Code: 
ping to 105-236-8-129-esr-lo.mtnbusiness.co.za [105.236.8.129]

>ping 105.236.8.129 -l 4096 -n 100

Pinging 105.236.8.129 with 4096 bytes of data:
Reply from 105.236.8.129: bytes=4096 time=72ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=71ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=76ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=71ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=81ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=74ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=71ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=90ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=74ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=334ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=264ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=486ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=781ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=921ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=86ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=363ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=609ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=793ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=858ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=127ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=344ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=822ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=71ms TTL=254
Request timed out.
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=72ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=73ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=72ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=73ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=72ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=81ms TTL=254
Request timed out.
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=75ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=72ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=71ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Request timed out.
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=89ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=1016ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=83ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=104ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=77ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=117ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=68ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=71ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=99ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=75ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=76ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=97ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=94ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=613ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=659ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=218ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=410ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=75ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=68ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=188ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Code: 
Ping statistics for 105.236.8.129:
    Packets: Sent = 100, Received = 79, Lost = 21 (21% loss),
Approximate round trip times in milli-seconds:
    Minimum = 68ms, Maximum = 1016ms, Average = 181ms

 
Last edited:
Gatecrasher said:
Code: 
ping to 105-236-8-129-esr-lo.mtnbusiness.co.za [105.236.8.129]

>ping 105.236.8.129 -l 4096 -n 100

Pinging 105.236.8.129 with 4096 bytes of data:
Reply from 105.236.8.129: bytes=4096 time=72ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=71ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=76ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=71ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=81ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=74ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=71ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=90ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=74ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=334ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=264ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=486ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=781ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=921ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=86ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=363ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=609ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=793ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=858ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=127ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=344ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=822ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=71ms TTL=254
Request timed out.
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=72ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=73ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=72ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=73ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=72ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=81ms TTL=254
Request timed out.
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=75ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=72ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=71ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Request timed out.
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=89ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=1016ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=83ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=104ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=77ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=117ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=68ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=71ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=99ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=75ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=76ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=97ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=94ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=613ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=659ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=218ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=410ms TTL=254
Request timed out.
Reply from 105.236.8.129: bytes=4096 time=70ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=75ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=68ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=188ms TTL=254
Reply from 105.236.8.129: bytes=4096 time=69ms TTL=254
Code: 
Ping statistics for 105.236.8.129:
    Packets: Sent = 100, Received = 79, Lost = 21 (21% loss),
Approximate round trip times in milli-seconds:
    Minimum = 68ms, Maximum = 1016ms, Average = 181ms

Click to expand...

Hi Gatecrasher

If I was in your situation with telkom problems, as I don't use my phone number and don't mind it changing, I would just order a new tel line, upgrade it to ADSL, hoping that it will get put on a new card or something and hopefully the problem will be solved, then cancel the other line. Drastic and probably a little time consuming (best case senario 2-4 weeks) but anything to take away the frustration? If you ask for the closer package (R20 per month), there is no installation fee, then just cancel the closer package afterwards :)
 
wingnut771 said:
Hi Gatecrasher

If I was in your situation with telkom problems, as I don't use my phone number and don't mind it changing, I would just order a new tel line, upgrade it to ADSL, hoping that it will get put on a new card or something and hopefully the problem will be solved, then cancel the other line. Drastic and probably a little time consuming (best case senario 2-4 weeks) but anything to take away the frustration? If you ask for the closer package (R20 per month), there is no installation fee, then just cancel the closer package afterwards :)
Click to expand...

If it were just my line... a good plan. But it is the whole town. And Telkom's response is to tweak a few things and report that the latency has improved. Even though the problem has nothing to do with latency.

Another Grahamstown forumite wrote this to me:

The technician was here a few minutes ago. He knew straight away why I logged a fault and didnt bother coming inside. As your technician said, it's the whole town. I asked if its a congested exchange and he said he is quite sure that it is not as the problem started very suddenly. He suspects that it happened on that Sunday when the municipality blacked out the town.

Anyway, he said he reported it multiple times to his head office because every call-out he gets is due to this. Apparently they are looking into it but still havent found the problem. I guess we will have to wait it out.
Click to expand...
 
Last edited:
Gatecrasher said:
If it were just my line... a good plan. But it is the whole town. And Telkom's response is to tweak a few things and report that the latency has improved. Even though the problem has nothing to do with latency.

Another Grahamstown forumite wrote this to me:
Click to expand...

Bummer dude :(

So what u saying is that the whole town is on one exchange? And that everyone there is suffering and no-one is okay? If you answer no to any of those questions then my suggestions still stands don't you think?
 
It's been 11 Days of not so amazing. I believe it is going to be fixed on Sunday. When the Arts Festival ends. Luckily, I'm not a conspiracy theorist.
 
How do I change from the Uncapped 4mb Bundle to the Business Uncapped 4mb bundle?
Essentially maintaining the bundle pricing.
 
Go to the Clientzone, unbundle your current package, , then upgrade to what ever it is you want and then re-bundle.
You will be charged prorate immediately.
https://clientzone.afrihost.com/

Or phone the support number, or SMS "help" to 32541
 
jannier said:
Go to the Clientzone, unbundle your current package, , then upgrade to what ever it is you want and then re-bundle.
You will be charged prorate immediately.
https://clientzone.afrihost.com/

Or phone the support number, or SMS "help" to 32541
Click to expand...

Thank you kindly I am now on the 4mb Business Bundle.

Right now though I am experiencing some poor throughput speeds:

Local:
Test conducted on 6/7/2013 22:33:26
Download Speed: 848 kbps (106 KB/sec transfer rate)
Upload Speed: 423 kbps (52.9 KB/sec transfer rate)
Latency: 54 ms

International:

Test conducted on 6/7/2013 22:36:25
Download Speed: 654 kbps (81.8 KB/sec transfer rate)
Upload Speed: 402 kbps (50.3 KB/sec transfer rate)
Latency: 210 ms
 
It sometime takes a little while before the system knows you are upgraded,
Maybe turn off your modem/router for 10 mins and then try again.

If still bad, contact the support center.
 
Well, the weekend came, and the weekend went. And still nothing has changed. Still getting massive packet loss and tortuously slow speeds. I'm wondering what i have to do to fix this. Become a Telkom employee and do it myself?
 
Been on Uncapped 1Mbps for two weeks know and impressed, well worth the extra money if you need a reliable line 24/7.

I will add that I am experiencing some lag (contention) on my line but I've always experienced this on the entry level ADSL line - its an exchange issue regardless of my ISP.
 
Seriously? Seriously?

After two weeks, this is what I get from Afrihost's Critical Care:

Good day Antony I trust yo are well :) Thank you so much for getting back to us requesting feedback, I just got off a call with Telkom and a work-order has been created we are waiting for the next available tech to attend to this fault your patience is highly appreciated Please do not hesitate to contact us if we may be of further assistance. Warm Regards Sydney
Click to expand...

Why does this sound like square one in Telkom fault reporting?

Whereas last week this had already been escalated to D-TECH and they were already investigating and working on it.

All I wanted was feedback and resolution from the ON-GOING issue. I don't want the next available tech, I want the people who were already working on it to actually fix it.
 
After reading that AH had sorted out their capacity issues with MTN, and seeing the results of the latest ISP survey, I decided to trial a 10mbps uncapped Business ADSL account.

Let me preface my feedback so far by asking: are there any problems with AH's network at the moment? Either in general or in the Western Cape?

I ask because I was expecting something amazing from an account that is essentially your top-tier, premium offering - and am severely underwhelmed.

During the day speeds seem to fluctuate, though overall browsing speed in general seems reasonably snappy and I can happily stream videos of any quality. NNTP downloads however are very unreliable speed-wise, constantly ramping up and slowing down between half and 90% of line speed. (I could not reach full line speed during the day even once - something I would think would be a no brainer on an account that is marketed as uncapped, unshaped, unmonitored, etc etc. But - not a deal breaker so far.

Confusion sets in after hours though. I had assumed that once business hours are over, performance would stabilize and/or improve. Not so, as the account deteriorated sharply as the evening went on. Browsing was patchy as hell, and orders of magnitude slower than daytime speeds. Sites which were quick and responsive during the day hardly loaded or had to be refreshed. International music streaming services were buffering (these use a miniscule amount of bandwidth and performed admirably during the day) and hardly loading info pages.

And all of this got WORSE as the evening went on. My wife even asked why the heck the internet was so slow. (we're usually on Openweb Gold)

By 10pm I could no longer even stream a 720p video from Youtube reliably, buffering so frequently I actually gave up.

I have to say I'm disappointed, and unless there's currently a network issue, will be avoiding returning to AH yet again.
 
That is very odd, I do not experience the same, mine has been perfect.

I suggest you post some local and international trace routes next time things slow down.
Hopefully they can spot the cause.
 
I'm still using the account and evaluating, so I'll continue to give feedback. I'll test again tonight and post results.

As a matter of interest - the following is the result of an international speed test taken on the mybb speed test page a few mins ago:

Test conducted on 7/9/2013 9:19:49 AM

Download Speed: 4022 kbps (502.8 KB/sec transfer rate)
Upload Speed: 812 kbps (101.5 KB/sec transfer rate)
Latency: 201 ms

Is this normal for 10mbps business ADSL during daytime?

Local seems fine, besides the shoddy latency, which is I expected from MTN's local peering:

Test conducted on 7/9/2013 9:22:35 AM

Download Speed: 7797 kbps (974.6 KB/sec transfer rate)
Upload Speed: 846 kbps (105.8 KB/sec transfer rate)
Latency: 40 ms
 
It all depends how much the route is congested or the server on the other end of the test.
It also depends on the contention ratio en-route.

I did the test 2 times and copied the 2nd test figures

MYBB INTL:
Test conducted on 7/9/2013 11:02:35 AM

Download Speed: 5153 kbps (644.1 KB/sec transfer rate)
Upload Speed: 797 kbps (99.6 KB/sec transfer rate)
Latency: 156 ms

MYBB LOCAL:
Test conducted on 7/9/2013 11:04:55 AM

Download Speed: 7893 kbps (986.6 KB/sec transfer rate)
Upload Speed: 854 kbps (106.8 KB/sec transfer rate)
Latency: 38 ms
 
Cool, so that's par for the course then. My concern is more about the severe degradation of the service at night. I'll see how things go tonight get in touch with AH for some diagnostics / feedback if there's a repeat of yesterday.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X