Afrihost Uncapped ADSL Feedback

Status
Not open for further replies.
Hi. If telkom sometime soon migrates my line to a 2mb ADSL line I would like to join Afrihost for 2mb uncapped. At what data usage can one expect to be throtteled?
 
Can you perhaps paste your traceroute to google.cinx.net.za ?

Tracing route to google.cinx.net.za [196.223.22.41]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms BillionRouter.werny.ctwug.za.net [172.18.58.108]
2 8 ms 8 ms 8 ms 105-236-4-193-esr-lo.mtnbusiness.co.za [105.236.4.193]
3 33 ms 32 ms 33 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178.77]
4 35 ms 33 ms 34 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 32 ms 31 ms 32 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 33 ms 33 ms 33 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 34 ms 34 ms 34 ms rb-cr-1.za--jh-cr-2.za-a.mtnns.net [196.44.31.94]
8 32 ms 32 ms 31 ms rb-cr-2.za--rb-dca-1.za-a.mtnns.net [196.44.31.123]
9 36 ms 31 ms 32 ms rb-dca-1.za--rb-cr-2.za-a.mtnns.net [196.44.31.122]
10 31 ms 30 ms 31 ms rb-cr-2.za--rb-dca-1.za-a.mtnns.net [196.44.31.123]
11 35 ms 31 ms 31 ms rb-dca-1.za--rb-cr-2.za-a.mtnns.net [196.44.31.122]
12 31 ms 31 ms 59 ms rb-cr-2.za--rb-dca-1.za-a.mtnns.net [196.44.31.123]
13 49 ms 30 ms 31 ms rb-dca-1.za--rb-cr-2.za-a.mtnns.net [196.44.31.122]
14 31 ms 31 ms 32 ms rb-cr-2.za--rb-dca-1.za-a.mtnns.net [196.44.31.123]
15 167 ms 31 ms 31 ms rb-dca-1.za--rb-cr-2.za-a.mtnns.net [196.44.31.122]
16 31 ms 31 ms 31 ms rb-cr-2.za--rb-dca-1.za-a.mtnns.net [196.44.31.123]
17 137 ms 46 ms 31 ms rb-dca-1.za--rb-cr-2.za-a.mtnns.net [196.44.31.122]
18 32 ms 31 ms 32 ms rb-cr-2.za--rb-dca-1.za-a.mtnns.net [196.44.31.123]
19 35 ms 73 ms 73 ms rb-dca-1.za--rb-cr-2.za-a.mtnns.net [196.44.31.122]
20 31 ms 31 ms 31 ms rb-cr-2.za--rb-dca-1.za-a.mtnns.net [196.44.31.123]
21 105 ms 183 ms * rb-dca-1.za--rb-cr-2.za-a.mtnns.net [196.44.31.122]
22 32 ms 31 ms 32 ms rb-cr-2.za--rb-dca-1.za-a.mtnns.net [196.44.31.123]
23 32 ms 34 ms 31 ms rb-dca-1.za--rb-cr-2.za-a.mtnns.net [196.44.31.122]
24 31 ms 31 ms 31 ms rb-cr-2.za--rb-dca-1.za-a.mtnns.net [196.44.31.123]
25 103 ms 31 ms 31 ms rb-dca-1.za--rb-cr-2.za-a.mtnns.net [196.44.31.122]
26 31 ms 31 ms 31 ms rb-cr-2.za--rb-dca-1.za-a.mtnns.net [196.44.31.123]
27 46 ms 79 ms 64 ms rb-dca-1.za--rb-cr-2.za-a.mtnns.net [196.44.31.122]
28 32 ms 32 ms 31 ms rb-cr-2.za--rb-dca-1.za-a.mtnns.net [196.44.31.123]
29 118 ms 124 ms 37 ms rb-dca-1.za--rb-cr-2.za-a.mtnns.net [196.44.31.122]
30 32 ms 31 ms 31 ms rb-cr-2.za--rb-dca-1.za-a.mtnns.net [196.44.31.123]

Trace complete.
 
Tracing route to google.cinx.net.za [196.223.22.41]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms BillionRouter.werny.ctwug.za.net [172.18.58.108]
2 8 ms 8 ms 8 ms 105-236-4-193-esr-lo.mtnbusiness.co.za [105.236.4.193]
3 33 ms 32 ms 33 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178.77]
4 35 ms 33 ms 34 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 32 ms 31 ms 32 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 33 ms 33 ms 33 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 34 ms 34 ms 34 ms rb-cr-1.za--jh-cr-2.za-a.mtnns.net [196.44.31.94]
8 32 ms 32 ms 31 ms rb-cr-2.za--rb-dca-1.za-a.mtnns.net [196.44.31.123]
9 36 ms 31 ms 32 ms rb-dca-1.za--rb-cr-2.za-a.mtnns.net [196.44.31.122]
10 31 ms 30 ms 31 ms rb-cr-2.za--rb-dca-1.za-a.mtnns.net [196.44.31.123]
11 35 ms 31 ms 31 ms rb-dca-1.za--rb-cr-2.za-a.mtnns.net [196.44.31.122]
12 31 ms 31 ms 59 ms rb-cr-2.za--rb-dca-1.za-a.mtnns.net [196.44.31.123]
13 49 ms 30 ms 31 ms rb-dca-1.za--rb-cr-2.za-a.mtnns.net [196.44.31.122]
14 31 ms 31 ms 32 ms rb-cr-2.za--rb-dca-1.za-a.mtnns.net [196.44.31.123]
15 167 ms 31 ms 31 ms rb-dca-1.za--rb-cr-2.za-a.mtnns.net [196.44.31.122]
16 31 ms 31 ms 31 ms rb-cr-2.za--rb-dca-1.za-a.mtnns.net [196.44.31.123]
17 137 ms 46 ms 31 ms rb-dca-1.za--rb-cr-2.za-a.mtnns.net [196.44.31.122]
18 32 ms 31 ms 32 ms rb-cr-2.za--rb-dca-1.za-a.mtnns.net [196.44.31.123]
19 35 ms 73 ms 73 ms rb-dca-1.za--rb-cr-2.za-a.mtnns.net [196.44.31.122]
20 31 ms 31 ms 31 ms rb-cr-2.za--rb-dca-1.za-a.mtnns.net [196.44.31.123]
21 105 ms 183 ms * rb-dca-1.za--rb-cr-2.za-a.mtnns.net [196.44.31.122]
22 32 ms 31 ms 32 ms rb-cr-2.za--rb-dca-1.za-a.mtnns.net [196.44.31.123]
23 32 ms 34 ms 31 ms rb-dca-1.za--rb-cr-2.za-a.mtnns.net [196.44.31.122]
24 31 ms 31 ms 31 ms rb-cr-2.za--rb-dca-1.za-a.mtnns.net [196.44.31.123]
25 103 ms 31 ms 31 ms rb-dca-1.za--rb-cr-2.za-a.mtnns.net [196.44.31.122]
26 31 ms 31 ms 31 ms rb-cr-2.za--rb-dca-1.za-a.mtnns.net [196.44.31.123]
27 46 ms 79 ms 64 ms rb-dca-1.za--rb-cr-2.za-a.mtnns.net [196.44.31.122]
28 32 ms 32 ms 31 ms rb-cr-2.za--rb-dca-1.za-a.mtnns.net [196.44.31.123]
29 118 ms 124 ms 37 ms rb-dca-1.za--rb-cr-2.za-a.mtnns.net [196.44.31.122]
30 32 ms 31 ms 31 ms rb-cr-2.za--rb-dca-1.za-a.mtnns.net [196.44.31.123]

Trace complete.

wow.. that doesnt look very good.. @Afriman - seems you need to tell your techs to sort out CPT's routing
 
wow.. that doesnt look very good.. @Afriman - seems you need to tell your techs to sort out CPT's routing

Yes, PLEASE AFRIMAN, sort out Cape Town's Routing, that is just not good by any means!
 
traceroute to a server in newlands CPT goes via JHB from CPT..

rather disappointed. speedtests are good but pings are sub-par for CPT.

WA and MWEB are a lot better when it comes to pings.. come on Afrihost, the idea is to make MWEB look bad, not good :)
 
My MTN connection just dropped to roughly 0.1Mbps and is now practically unusable (took a minute or two to log in here). Anyone else?
 
Yep, mine died.... slower than a sloth running through quicksand...
Had to back out and use another account...

It's a trial, so there's that...
Hope they sort out most of the niggles soon, as very few users are currently on and it is failing the litmus test..
 
My MTN connection just dropped to roughly 0.1Mbps and is now practically unusable (took a minute or two to log in here). Anyone else?

Yup, switched back to the capped IS account. MTN dead at the moment.
 
I see a couple of people saying their accounts died - we're not a aware of a general problem so please PM our username so we can check this out individually. We're able to authenticate normally in our testing on this side.
 
Welcome Back AfriMan!

youve been very quiet today!
I see a couple of people saying their accounts died - we're not a aware of a general problem so please PM our username so we can check this out individually. We're able to authenticate normally in our testing on this side.
 
Last edited:
Mine also died about 4pm, had to reconnect on the router and then everything worked again, but now I cant even play CoD online because it would just not connect to any game server and XFire also does not work. Everything else is working just fine.

The routing via JHB is a pain in the ASS, and if it is not fixed before the switch over, it will mean alot of people will move over to MWeb just be be able to get good pings in games.

I personally think that Afrihost is playing with fire here. IS was good enough for me, speeds were great.
 
Mine also died about 4pm, had to reconnect on the router and then everything worked again, but now I cant even play CoD online because it would just not connect to any game server and XFire also does not work. Everything else is working just fine.

The routing via JHB is a pain in the ASS, and if it is not fixed before the switch over, it will mean alot of people will move over to MWeb just be be able to get good pings in games.

I personally think that Afrihost is playing with fire here. IS was good enough for me, speeds were great.

A horse and carriage was also fast enough then Henry Ford came along. I think the MTN network is going to be great for Afrihost. They have more control over it than they did with IS. These are just teething problems.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X