Afrihost Uncapped ADSL Feedback

Status
Not open for further replies.
Now that Cape Town is purring, I'll spend some more time getting info and hopefully a revised ETA.

Cape Town is purring in the sense that it isn't. At all.

But for once the crappiness is not limited to AH, I've tried WA and Plugg (both IS, it seems) and they are only marginally less awful.
 
Our own testing, on a normal 4Mbps line we've setup in Cape Town, shows consistent speeds and pings.

Consistency is not the issue. My 4mbps lines, capped or uncapped, are all a very consistent < 100KBps on all protocols.
 
Brackenfell Cape Town, I doubt it is exchange problem, more a transit problem between Dslam - ESR - IPC

Agree with you. Had first hops of 2000ms not too long ago (30 mins). I'm in S.Heights and connect to the Durbanville exchange (WDBV), but it seems we have similar issue at the same times on the same days. Higher upstream than exchange in my opinion.
 
But for once the crappiness is not limited to AH, I've tried WA and Plugg (both IS, it seems) and they are only marginally less awful.

Yip, I've tested other accounts also and they all have similar low throughput in Cpt. AH IPC actually gave me the lowest latency I've ever had earlier today... incl when they were still with IS.
 
suddenly at 12.48am everything returned to normal instantly.
No more high latency, exchange instantly back to 4-5ms



Certain HOP's still seems struggling

Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 5 ms 5 ms 5 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 32 ms 31 ms 32 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 30 ms 66 ms 30 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 6 ms 6 ms 6 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 31 ms 30 ms 30 ms 196.44.31.106
7 30 ms 31 ms 31 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 8 ms 6 ms 6 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 15 ms 8 ms 7 ms tengig0-0-0-1.cpt-p-2.mweb.co.za [197.84.4.166]
10 7 ms 6 ms 7 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
11 8 ms 8 ms 7 ms 196.28.178.66
12 7 ms 7 ms 7 ms cte-core-sw2.vwol.net [196.41.144.35]
13 8 ms 7 ms 7 ms www.mweb.co.za [196.2.63.110]

Trace complete.
 
Last edited:
I'm starting to think we need to redo these threads, have a Cape Town and Everywhere else Ah thread. Ever time I see complaints saying AfriHost is ballsuped I check my account, speed etc and all is, to quote AfriMan, awesome. Then I read in depth and the complaints are usually Cape region. Very confusing to be honest.

People go on like the service provider is absolutely dead in the water when they really deliver at my, and other's ends but it's localized problems.

Otherwise we need to start posts off with "Location:" or something.
 
and this is why we stuck around

Test conducted on 01 March 2013 07:42 (International test from Cape Town)
Download Speed: 3242 kbps (405.3 KB/sec transfer rate)
Upload Speed: 502 kbps (62.8 KB/sec transfer rate)
Latency: 170 ms
 
and this is why we stuck around

Test conducted on 01 March 2013 07:42 (International test from Cape Town)
Download Speed: 3242 kbps (405.3 KB/sec transfer rate)
Upload Speed: 502 kbps (62.8 KB/sec transfer rate)
Latency: 170 ms

International still sucking here also.
 
and this is why we stuck around

Test conducted on 01 March 2013 07:42 (International test from Cape Town)
Download Speed: 3242 kbps (405.3 KB/sec transfer rate)
Upload Speed: 502 kbps (62.8 KB/sec transfer rate)
Latency: 170 ms

So at 0900 things slowed down but still alot better than prior to IPC

Test conducted on 01 March 2013 09:05 (International Test from Cape town)
Download Speed: 1329 kbps (166.1 KB/sec transfer rate) - speed has dropped but not to under 1MB as normal///
Upload Speed: 511 kbps (63.9 KB/sec transfer rate)
Latency: 171 ms
 
Afriman, the latency resolved instantly at 00:48

I just did a trace and seems the IPC is taking some strain?


Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 5 ms 4 ms 5 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 75 ms 74 ms 73 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 37 ms 29 ms 30 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 6 ms 6 ms 6 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 71 ms 71 ms 70 ms 196.44.31.106
7 73 ms 71 ms 72 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 7 ms 7 ms 7 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 12 ms 10 ms 11 ms tengig0-0-0-1.cpt-p-2.mweb.co.za [197.84.4.166]
10 8 ms 7 ms 7 ms vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
11 8 ms 7 ms 7 ms 196.28.178.66
12 7 ms 9 ms 7 ms cte-core-sw2.vwol.net [196.41.144.35]
13 7 ms 7 ms 7 ms www.mweb.co.za [196.2.63.110]

Trace complete.

Maybe there are other factors on the routes inducing latency?

Tracing route to saix.net [196.25.1.204]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 5 ms 4 ms 4 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 73 ms 70 ms 82 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 30 ms 30 ms 85 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 6 ms 6 ms 6 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 18 ms 51 ms 66 ms tb-pr-1.za--tb-cr-2.za-a.mtnns.net [196.44.18.143]
7 69 ms 66 ms 64 ms wblv-ip-se-2-gw.telkom-ipnet.co.za [196.25.165.197]
8 31 ms 31 ms 31 ms 196.43.25.205
9 33 ms 32 ms 32 ms wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [196.43.11.30]
10 * * * Request timed out.
11 * * * Request timed out.
12 wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [196.43.11.30] reports: Destination net unreachable.

Trace complete.

Tracing route to webafrica.com [196.220.58.66]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 5 ms 5 ms 5 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 6 ms 5 ms 6 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
4 30 ms 29 ms 29 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 7 ms 6 ms 6 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 6 ms 6 ms 6 ms tb-pr-1.za--tb-cr-2.za-a.mtnns.net [196.44.18.143]
7 75 ms 73 ms 74 ms wblv-ip-se-2-gw.telkom-ipnet.co.za [196.25.165.197]
8 31 ms 30 ms 30 ms 196.43.25.205
9 8 ms 7 ms 7 ms 196.43.39.78
10 9 ms 8 ms 8 ms wnls-cr1-vl-102.wa.co.za [196.220.59.229]
11 8 ms 8 ms 8 ms wnls-hr1-gi-8-13.wa.co.za [41.185.1.18]
12 9 ms 8 ms 9 ms 196.220.58.66

Trace complete.

Tracing route to afrihost.com [196.38.88.139]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 5 ms 5 ms 5 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 7 ms 6 ms 6 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
4 59 ms 30 ms 30 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 6 ms 6 ms 6 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 7 ms 7 ms 7 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
7 6 ms 6 ms 10 ms 196.44.0.74
8 33 ms 33 ms 32 ms 41-208-29-209.mtnns.net [41.208.29.209]
9 33 ms 32 ms 34 ms core1a-ctn-gi0-1.ip.isnet.net [168.209.2.5]
10 61 ms 62 ms 61 ms 168.209.100.13
11 64 ms 59 ms 56 ms core1a-pkl-te1-2.isnet.net [168.209.100.238]
12 53 ms 52 ms 52 ms csw1-b-jup-bry-gi3-2.ip.isnet.net [168.209.218.21]
13 31 ms 34 ms 30 ms 196.34.134.105
14 32 ms * * gw.aserv.co.za [196.33.227.1]
15 131 ms 132 ms 129 ms www.afrihost.com [196.38.88.139]

Trace complete.

Tracing route to bbc.com [212.58.241.131]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 5 ms 5 ms 5 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 7 ms 6 ms 19 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
4 30 ms 30 ms 30 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 6 ms 6 ms 6 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 150 ms 197 ms 177 ms am-cr-2.nl--am-cr-nl-b.mtnns.net [196.44.31.171]
7 150 ms 149 ms 158 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
8 150 ms 150 ms 150 ms bbc-linx.pr01.thdow.bbc.co.uk [195.66.224.103]
9 * * * Request timed out.
10 150 ms 150 ms 150 ms ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
11 166 ms 153 ms 150 ms 132.185.255.60
12 151 ms 150 ms 150 ms virtual-vip.thdo.bbc.co.uk [212.58.241.131]

Trace complete.
 
Last edited:
Looking good in Cape Town here as well:

2542581909.png


My only gripe is the free bandwidth "gift" to make up for bad service expired only 4 days later and the state of the service was so atrocious up until this morning that there was no way to ever use it. So not really a free anything, just another PR exercise - if Afrihost were half as good as implementing upgrades to their infrastructure as they are at PR, then it really would be a sterling ISP.

Please AH - try to keep it like this and let's wait a good while before you decide to make any more major infrastructure changes.
 
I just did a trace and seems the IPC is taking some strain?

Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 5 ms 4 ms 5 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 75 ms 74 ms 73 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 37 ms 29 ms 30 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 6 ms 6 ms 6 ms unc-cpt-1.mtnns.net [196.44.18.8]

I saw the same thing last night - same hop was slow. From Port Elizabeth.
 
I woke up this morning to find a lot of my stuff had downloaded overnight, so it looks like AH is back on track.

Speedtest got 3.5Mbps down, which is normal on a 4Mb line?

This seems to be my norm now (atleast better than 0.5Mbps it has normally been)
Test conducted on 01 March 2013 12:44
Download Speed: 1329 kbps (166.1 KB/sec transfer rate)
Upload Speed: 490 kbps (61.3 KB/sec transfer rate)
Latency: 170 ms
 
So, it seems that the Cape Town IPC is now available? Can anyone confirm this? Have you noticed an improvement in your ping to the USA if so?

I ask because if the ping to the NA WoT server is superior to the 250ms I'm getting on OpenWeb right now then I'll make the jump to afrihost :-)
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X