Afrihost Business Uncapped Feedback - 2

Status
Not open for further replies.
Africrap, 2 hours to download a 1gb file on a 10m account.
 
Cancellation put in.

If this "guaranteed full line speed at all times" problem gets resolved before the 25th, I will cancel my cancellation.
 
guys just stop ranting and "helping" afrihost coz obviously they do not care, i have stopped with any rants or "help" coz all they do is bin the stuff you send them, just look for another ISP.......

my internet is standing still just like all of yours, but "helping" them is not helping you.....
 
Having trouble streaming atm. Speed tests aren't nearly as fast as they should be. Rebooting router changed nothing.

According to Afrihost's network status page, both the North and South IPC's are experiencing too much demand. I can't understand how an ISP can run out of bandwidth for an entire country. Surely they can predict the capacity they need based on usage patterns? I've been happy with Afrihost for over two years now so I'm prepared to wait out a period of turbulence, but I only have so much patience. Especially not when everyone is singing Crystal Web's praises to high heaven.
 
10mbps Business, after 21:00. No P2P, no NNTP, just a regular Origin update. But oh well, thanks Afrihost.

Capture.jpg

If this isn't resolved before the 24th, I am cancelling.
 
Last edited:
Spoke too soon about improved latency on Axxess for Diablo 3. After a bit more testing it also has the same huge lag spikes as Afrihost. Strange thing is that Destiny still performs (read actually works) while it doesn't even connect on Afrihost.
 
i am ashamed to admit it.. i cancelled openweb to move to afrihost.. not because of poor service... but because of all the bad press... and um... i am regretting leaving them for AH :/

Dont be ashamed

I left OW because the account was terrible during the day, and moved to AH too. I believe it was the right thing to do at the time.

As for AH, I do believe they are having some issues at the moment, but I am also confident that they will sort it out.
If they do ... the worlds a happy place

If not .... we move on.

But, for me .... I am happy to give AH the benefit of the doubt for the next week or two and hopefully they will sort their issue out.
 
Dont be ashamed

I left OW because the account was terrible during the day, and moved to AH too. I believe it was the right thing to do at the time.

As for AH, I do believe they are having some issues at the moment, but I am also confident that they will sort it out.
If they do ... the worlds a happy place

If not .... we move on.

But, for me .... I am happy to give AH the benefit of the doubt for the next week or two and hopefully they will sort their issue out.

This is why I think that the best strategy is to cancel . If they improve before 25 cancel the cancellation .Not improve .....next . Under the assumption that they care , and this is a BIG assumption , maybe it will also give them some incentive to deal with the problem .
 
I canceled. I see on the clientzone theres a business optimization that you can switch off.... Anyone tried this?
 
I canceled. I see on the clientzone theres a business optimization that you can switch off.... Anyone tried this?

That's for p2p shaping. Most people here switch that off.
 
I canceled. I see on the clientzone theres a business optimization that you can switch off.... Anyone tried this?

Everyone turns it off, I also cancelled, I will revert that decision if things change, otherwise I'm off to a different ISP. Been testing and all the ones I tested delivered full network speed.
 
If this isn't resolved before the 24th, I am cancelling.

lol, just put your cancellation in. Idle threats don't mean anything, and you can uncancel before the 25th.

South Africans needs to start taking action and stop giving people so many second chances.
 
i love how on their network status page.. they list this problem as a "MEDIUM IMPACT".

I wonder how many of their clients consider this "MEDIUM" when you have an ISP that has run out of capacity nationally.
 
Doing some testing this morning... WA(shaped,capped) vs. AH(unshaped, uncapped)

Both sync at 10240kbps...

SAIX line speedtest:

Afrihost:
Last Result:
Download Speed: 4887 kbps (610.9 KB/sec transfer rate)
Upload Speed: 720 kbps (90 KB/sec transfer rate)
Latency: 61 ms
2014/10/09, 8:34:18 AM

WebAfrica
Last Result:
Download Speed: 8238 kbps (1029.8 KB/sec transfer rate)
Upload Speed: 810 kbps (101.3 KB/sec transfer rate)
Latency: 35 ms
2014/10/09, 8:44:08 AM

In terms of latency, AH is slightly better(20ms), but more erratic... lots of spikes right up to 2500ms. WA hovers around 40ms with the occasional spike to 500ms.

Interesting...
 
Last edited:
So after a week of trying to sort out MySQL connectivity issues with "critical care", having heard nothing this week I sent a follow up query to which I got the responses - "please let us know if you receive an error message" (for a complaint about packets dropping on a protocol) and "what was your account again?" (after being assured they were working on getting to the bottom of it a week ago).

Afrihost, your support is an embarrassment.
 
So after a week of trying to sort out MySQL connectivity issues with "critical care", having heard nothing this week I sent a follow up query to which I got the responses - "please let us know if you receive an error message" (for a complaint about packets dropping on a protocol) and "what was your account again?" (after being assured they were working on getting to the bottom of it a week ago).

Afrihost, your support is an embarrassment.

Do other ISPs work?
 
Something is definitely screwed up on the MTN network, at least for Diablo 3. Both Axxess and Afrihost shows huge amounts of packet loss. That can't be normal right?

AFRIHOST:
Code:
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           PC [192.168.0.11]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.0.1
                                2/ 100 =  2%   |
  2   30ms     4/ 100 =  4%     2/ 100 =  2%  105-236-4-193-esr-lo.mtnbusiness.co.za [105.236.4.193]
                                0/ 100 =  0%   |
  3   31ms     3/ 100 =  3%     1/ 100 =  1%  ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
                                0/ 100 =  0%   |
  4   34ms     2/ 100 =  2%     0/ 100 =  0%  tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
                                0/ 100 =  0%   |
  5   30ms     2/ 100 =  2%     0/ 100 =  0%  compj-cpt-1.mtnns.net [196.44.18.2]
                               98/ 100 = 98%   |
  6  ---     100/ 100 =100%     0/ 100 =  0%  ls-cr-2--tb-cr-1.uk-b.mtnns.net [196.44.31.113]
                                0/ 100 =  0%   |
  7  ---     100/ 100 =100%     0/ 100 =  0%  am-cr-1.nl--ls-cr-2.uk-a.mtnns.net  [196.44.31.183]
                                0/ 100 =  0%   |
  8  ---     100/ 100 =100%     0/ 100 =  0%  am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.141]
                                0/ 100 =  0%   |
  9  ---     100/ 100 =100%     0/ 100 =  0%  xe-4-1-0.edge5.Amsterdam1.Level3.net [212.72.41.89]

Trace complete.

AXXESS:
Code:
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           PC [192.168.0.11]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.0.1
                                1/ 100 =  1%   |
  2   30ms     6/ 100 =  6%     5/ 100 =  5%  105-236-4-193-esr-lo.mtnbusiness.co.za [105.236.4.193]
                                0/ 100 =  0%   |
  3   33ms     1/ 100 =  1%     0/ 100 =  0%  41.181.201.94
                                3/ 100 =  3%   |
  4   31ms     4/ 100 =  4%     0/ 100 =  0%  tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
                                2/ 100 =  2%   |
  5   31ms     6/ 100 =  6%     0/ 100 =  0%  compj-cpt-1.mtnns.net [196.44.18.2]
                               94/ 100 = 94%   |
  6  ---     100/ 100 =100%     0/ 100 =  0%  ls-cr-2.uk--tb-cr-1.za.mtnns.net [196.44.31.113]
                                0/ 100 =  0%   |
  7  ---     100/ 100 =100%     0/ 100 =  0%  am-cr-1.nl--ls-cr-2.uk-a.mtnns.net  [196.44.31.183]
                                0/ 100 =  0%   |
  8  ---     100/ 100 =100%     0/ 100 =  0%  am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.141]
                                0/ 100 =  0%   |
  9  ---     100/ 100 =100%     0/ 100 =  0%  xe-4-1-0.edge5.Amsterdam1.Level3.net [212.72.41.89]

Trace complete.

And for comparison here's one which someone else on WA did:
Code:
Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                          [192.168.0.200] 
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.0.2 
                                0/ 100 =  0%   |
  2  ---     100/ 100 =100%   100/ 100 =100%  196-210-142-***.dynamic.isadsl.co.za [196.210.142.***] 
                                0/ 100 =  0%   |
  3   19ms     0/ 100 =  0%     0/ 100 =  0%  196.38.73.113 
                                0/ 100 =  0%   |
  4   19ms     0/ 100 =  0%     0/ 100 =  0%  cdsl2-rba-vl150.ip.isnet.net [196.38.73.9] 
                                0/ 100 =  0%   |
  5   22ms     1/ 100 =  1%     1/ 100 =  1%  core2-pkl-t0-7-0-0.ip.isnet.net [168.209.1.163] 
                                0/ 100 =  0%   |
  6  190ms     2/ 100 =  2%     2/ 100 =  2%  168.209.246.3 
                                0/ 100 =  0%   |
  7  193ms     0/ 100 =  0%     0/ 100 =  0%  xe-4-3-2.edge3.London1.Level3.net [195.50.124.33] 

Trace complete.

Some good news is that Destiny seems to be working. For now at least. Will have to see how it goes after 10/11 when the "contention" kicks in hardest.
 
Do other ISPs work?

Yes. Perfectly. Repeatable.

Looking on wireshark, it looks like larger packets are dropped - MySQL packet size seems to depend on the SQL query and whether you turn compress on or off. MySQL queries that include binaries in the result tend to generate larger packets and therefore timeout. The result is hit or miss and random timeouts in client applications during debugging which is enough to ruin your day, esp if you're on a deadline. There are either serious fragmentation issues on AH or they are shaping.

Happens for 1-2 days then it's fine again. Started last Monday.
 
Last edited:
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X