Afrihost Uncapped ADSL Feedback

Status
Not open for further replies.
Just spoke to someone from Afrihost who gave me a decent explanation for all this.

From what I can gather, the situation is as follows:
Deleted the rest as to much to repeat.. .

Even late at night I am lucky to get over 0.5mb on my 4mb line and all i am doing is gaming and maybe FB in the background..
 
@ClintonExsteen

I'm not an Afrihost employee so I can't state anything as fact, but from what I gathered in the conversation I had earlier with an Afrihost representative and based on my own logs and the trends that shows for the last 5 days or so, and speed test I've run myself on my line, it would definitely seem like the actual LINE speeds are not the issue. In other words, a normal line speed test SHOULD still be giving you full speed or close if the actual line is functioning normally and your hardware is ok.

You should ONLY be seeing targeted throttling for roughly 16 hours out of a 24 hour cycle. From around 7 in the morning to 11 at night, and even then the throttling should be targeting specific ports / protocols.

If you are seeing your actual line speed reporting wrong on a speed test, then something else might also be going on.

My line speed reports full speed when I do a speed test. But any port 563 SSL downloads are clearly throttled to 120 Kbps during that 16 hour throttling window. However, during that same window, other things appear to be fine, streaming HD video is fine even while I'm downloading at 120Kbps on port 563.
 
@ afrihost

Tracing route to www.afrihost.co.za [196.38.88.139]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms sx762.dummy.porta.siemens.net [10.0.0.2]
2 * 96 ms 61 ms 105-236-7-193-esr-lo.mtnbusiness.co.za [105.236.
7.193]
3 99 ms * 71 ms ipc-recieve-jh-1a.za.mtnbusiness.net [41.181.178
.5]
4 91 ms 55 ms 57 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
5 64 ms * 67 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.114]
6 93 ms 67 ms 87 ms jh-cr-2.za--jh-dca-2.za-a.mtnns.net [196.44.0.22
4]
7 57 ms 266 ms 55 ms jh-pr-1.za--jh-cr-2.za.mtnns.net [196.44.0.222]

8 59 ms 119 ms 112 ms 41-208-29-125.mtnns.net [41.208.29.125]
9 85 ms 75 ms * 168.209.1.140
10 60 ms 82 ms 57 ms core2a-bry-ge1-1-0.isnet.net [168.209.100.242]
11 62 ms 177 ms 64 ms csw1-b-jup-bry-gi3-1.ip.isnet.net [168.209.217.2
1]
12 74 ms 67 ms 76 ms 196.34.134.105
13 71 ms 137 ms 145 ms gw.aserv.co.za [196.33.227.1]
14 104 ms 126 ms 57 ms www.afrihost.com [196.38.88.139]

Trace complete.

speedtest results are the same no matter what isp i use
i contact afrihost support but watson never came back 2 me
 
@ClintonExsteen

I'm not an Afrihost employee so I can't state anything as fact, but from what I gathered in the conversation I had earlier with an Afrihost representative and based on my own logs and the trends that shows for the last 5 days or so, and speed test I've run myself on my line, it would definitely seem like the actual LINE speeds are not the issue. In other words, a normal line speed test SHOULD still be giving you full speed or close if the actual line is functioning normally and your hardware is ok.

You should ONLY be seeing targeted throttling for roughly 16 hours out of a 24 hour cycle. From around 7 in the morning to 11 at night, and even then the throttling should be targeting specific ports / protocols.

If you are seeing your actual line speed reporting wrong on a speed test, then something else might also be going on.

My line speed reports full speed when I do a speed test. But any port 563 SSL downloads are clearly throttled to 120 Kbps during that 16 hour throttling window. However, during that same window, other things appear to be fine, streaming HD video is fine even while I'm downloading at 120Kbps on port 563.


I am using the speedtest app on mybb and what i have posted is what AH accounts are running at... just spent some cash to do a test with another ISP
Test conducted on 14 November 2012 13:29
Download Speed: 2360 kbps (295 KB/sec transfer rate)
Upload Speed: 412 kbps (51.5 KB/sec transfer rate)
Latency: 174 ms

So it is not my line........
 
if you were IS and you were losing the client-base, wouldn't you rather them move all at once than in dribs and drabs?? par for the course I would say
Seems like a good way to gain some of that business back by poisoning Afrihost/Axxess' well so people flock back to IS reseller ISP's. NOT cool if this is the case.
 
Rather spam an Afrihost rep via PM or something, don't flood the thread!
 
Rather spam an Afrihost rep via PM or something, don't flood the thread!

How exactly is that useful? Can I read your PM that you have sent and see that at least someone else is having the same or related issue?

But yes... every 1 - 2 min tracert is too much. Just use RBP if you feel it is spammy...
 
just explain it to me.

look at no 7

7 57 ms 266 ms 55 ms jh-pr-1.za--jh-cr-2.za.mtnns.net [196.44.0.222]

266ms??
 
Pr⊕phet:

What do you mean? My issue is with flooding the thread with the same Trace route the whole time, not with posting it at all.
 
Pr⊕phet:

What do you mean? My issue is with flooding the thread with the same Trace route the whole time, not with posting it at all.

I misread, reread my ninja edit and see I have reported it.
 
I have reported you for thread spam

+1

just explain it to me.

look at no 7

7 57 ms 266 ms 55 ms jh-pr-1.za--jh-cr-2.za.mtnns.net [196.44.0.222]

266ms??

EVERYONE is having problems. You flooding the thread isn't helping. Check on the last page there is a pretty good explanation of what's going on.
 
I think the bottom line here is very simple. Their migration hasn't gone quite as planned and the network is not currently coping with the load.

We can all post speed test results and latency reports until the cows come home. It isn't going to change anything.

I suspect that, depending on where you are physically located right now, results may vary too. So I might only be experiencing targeted throttling with avg latencies while somebody else has horrific latency and someone else has general speed / throttling issues for everything and not just downloads.

The point is, all of those things are symptoms of ONE underlying issue. The network is NOT coping right now.

Obviously AH don't want to admit that after all the fanfare about how awesome the MTN partnership would make everything and how all the old problems would vanish and everything would be utopia, so instead they are desperately trying to deal with the situation as fast as possible.

Given that we have pretty much confirmed that our problems are NOT due to some new draconian threshold system or abuse policy and not because someone at Afrihost sold us the biggest scam in history and intentionally lied to us, we now basically have 2 very simple choices:

1. Accept that there is a network issue that IS being dealt with and that this happens in IT, a lot, and it SHOULD be resolved by January, and decide that you can live with that.

2. Consider this whole debacle the last straw. Kick something, hard. Utter a few decent obscenties directed at AH to make yourself feel better. Then cancel your account and move on.

No amount of further complaining, jumping up and down, throwing tantrums like children or any other form of desperate nerd outrage is going to make AH fix the problem any faster.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X