Afrihost Business Uncapped Feedback

Status
Not open for further replies.
The issue is that this causing some serious productivity issues from a business perspective. Its seems unreasonable to have businesses suffer in favor of an Apple user. Even if Afrihost had to refund me for the entire month, that doesnt cover the financial loss due to unproductivity for the entire day that the internet is not working.

I would recommend throttling the IOS update during the day and opening it up after midnight.

I totally understand your POV view here. It's definitely something that I will raise, becuase it seems to me it worth looking at for future situations like this :(
 
I understand how a massive update from international servers can bog down the network capacity, but seriously, if other ISPs on the same MTN network can handle it (I heard axxess is fine?), then Afrihost should invest in more capacity to compensate. I don't want to be a part of a network where every time a new revision of iOS is released I have to deal with this. I am entirely for the idea of throttling the living **** out of the updates.
 
Even the Apple users in the offices are complaining about the internet and are okay with the IOS update being throttled.
 
I understand how a massive update from international servers can bog down the network capacity, but seriously, if other ISPs on the same MTN network can handle it (I heard axxess is fine?), then Afrihost should invest in more capacity to compensate. I don't want to be a part of a network where every time a new revision of iOS is released I have to deal with this. I am entirely for the idea of throttling the living **** out of the updates.

I think it's important to remember that we have a lot more users that Axxess and the breakdown of users, business, etc are probably very different. To my knowledge they were also affected to some extent.
 
I think it's important to remember that we have a lot more users that Axxess and the breakdown of users, business, etc are probably very different. To my knowledge they were also affected to some extent.
Yeah they have less users, but that also means less money. They have enough infrastructure for their user count; Afrihost does not.
 
This started for me the evening before before the IOS8 update release, so not buying it, sorry. And the real slowdown starts from about 4pm daily. Is there some logical reason why Apple users decide en masse that 4pm is a good time to update? I think not.
 
Yeah they have less users, but that also means less money. They have enough infrastructure for their user count; Afrihost does not.

We use the same network, so I think it's more likely that they didn't get as much demand for updates as we saw on our side, relatively :(
 
This started for me the evening before before the IOS8 update release, so not buying it, sorry. And the real slowdown starts from about 4pm daily. Is there some logical reason why Apple users decide en masse that 4pm is a good time to update? I think not.

The apple update was released on Wednesday evening around 7pm, and then continued consistently through yesterday.

We did not that demand picked up slightly earlier than usual in the South, but not to the point where we saw significant contention.
 
My AH account has been fine. Perhaps AH allocates bandwidth to different regions in the country and any contention is a local/provincial affair.
 
This started for me the evening before before the IOS8 update release, so not buying it, sorry. And the real slowdown starts from about 4pm daily. Is there some logical reason why Apple users decide en masse that 4pm is a good time to update? I think not.

My problem started on the 12th and it is also blamed on the iO8 update.
I did all the tracerts and ping screen-dumps on a couple of different accounts (on different days) to show them that there was a problem but looks like I wasted my time generating all the dumps.
I think support wants to close my ticket for SLA requirements and that is why I'm receiving the generic iO8 reply.
 
My AH account has been fine. Perhaps AH allocates bandwidth to different regions in the country and any contention is a local/provincial affair.

Contention is definitely specific to each region as they each have their own IPC capacity.
 
My problem started on the 12th and it is also blamed on the iO8 update.
I did all the tracerts and ping screen-dumps on a couple of different accounts (on different days) to show them that there was a problem but looks like I wasted my time generating all the dumps.
I think support wants to close my ticket for SLA requirements and that is why I'm receiving the generic iO8 reply.

That shouldn't be the case and I apologise if we've lumped you in the wrong category.

We haven't seen contention in the North prior to the Apple update, so this is definitely something we need to investigate properly.

Please PM me with the ticket reference :(
 
I mean refined beyond that though. PE uses the CT IPC, and CT users are complaining about contention.

I don't think we're that close to having IPC in PE or PTA separately, though it's obviously something we'd love to have.

We can't really distinguish different cities on the same IPC to effect any changes at that level :(
 
So if the IOS update resulted in ~25% more traffic on the network, at worst I should still be getting 75% of my usual throughput on my line, not the pathetic 10% to 15% that many experienced. At best, there should be enough spare capacity to absorb some of that extra IOS traffic. But accepting the worst case for now, does this "unexpected" demand have additional compound effects? If so, I would love an explanation of why.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X