Afrihost Business Uncapped Feedback

Status
Not open for further replies.
Heheheheheh ...

Anyhow, I think I have had it with uncapped.
I think my next move will be a plain old 100GB-160GB capped account.
Screw uncapped. Not worth all the tracerts and schizophrenics.
Shaped or unshaped, down south here uncapped sucks lately.

/meh meh and another meh just for the hell of it

WebAfrica - 240GB total Data for R559 per month

or

/sigh

OpenWeb 100Gb Capped Unshaped R399

oh fuddit

/meh

Just get a proper account. It's been proven long ago that AH has ipc issues. You the only one that's been wasting your time.
 
Cybersmart Business uncapped still performing for me. By far the best account I've had...

92L1eJH.png
 
tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms 10.0.0.2
2 47 ms 34 ms 52 ms 105-236-9-65-esr-lo.mtnbusiness.co.za [105.236.9
.65]
3 50 ms 39 ms 42 ms 41.181.221.254
4 56 ms 39 ms 39 ms 66.8.75.13
5 101 ms 79 ms 79 ms tb-dca-2.za-qux-e.za.mtnbusiness.net [41.181.202
.0]
6 1040 ms 339 ms 289 ms compj-cpt-1.mtnns.net [196.44.18.2]
7 267 ms 289 ms 379 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]

8 328 ms 309 ms 279 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]

9 248 ms 269 ms 269 ms 41.181.139.109
10 250 ms 269 ms 240 ms 72.14.194.74
11 420 ms 469 ms 509 ms 66.249.95.8
12 415 ms 449 ms 460 ms 209.85.244.240
13 210 ms 212 ms 206 ms 72.14.242.166
14 481 ms 379 ms 429 ms 72.14.238.43
15 * * * Request timed out.
16 846 ms 409 ms 429 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.



Ouchies. International is hardly moving

That's a line issue, you'll have to report a fault :(
 
I just don't understand how it's not every single one of the people complaining about these issues?? There must be a common link. For example, if everyone is situated in Kirstenbosch, then there could be a fault with the KB Central MTN Exchange (which would be around hop 3/4 on the tracerts). This would therefore mean that only MTN accounts would have issues.

Could everyone having issues please post a tracert. Doesn't matter where to - I just want to see the paths being taken :)

Z
 
Hi Zertop

Do you want a tracert now (when it is behaving) or when it starts to flap and flip and gets all schizo ?


I just don't understand how it's not every single one of the people complaining about these issues?? There must be a common link. For example, if everyone is situated in Kirstenbosch, then there could be a fault with the KB Central MTN Exchange (which would be around hop 3/4 on the tracerts). This would therefore mean that only MTN accounts would have issues.

Could everyone having issues please post a tracert. Doesn't matter where to - I just want to see the paths being taken :)

Z

EDIT:

Ps. I am connected to the WYNBERG (WWG+) exchange.
 
Last edited:
Hi Zertop

Do you want a tracert now (when it is behaving) or when it starts to flap and flip and gets all schizo ?

Uhmm, now should be good :) then another when it starts to "flip and flap and gets all schizo" :D it's just to see the route taken :P
 
Uhmm, now should be good :) then another when it starts to "flip and flap and gets all schizo" :D it's just to see the route taken :P

Cool beans

Afrihost tool

Code:
Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=59 time=44 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=59 time=41 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=59 time=42 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=59 time=54 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=59 time=48 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=45 time=190 ms
Request timeout for icmp_seq 2
64 bytes from 8.8.8.8: icmp_req=3 ttl=45 time=182 ms
Request timeout for icmp_seq 4
64 bytes from 8.8.8.8: icmp_req=5 ttl=45 time=193 ms


Trace Test:

traceroute -n 197.242.144.102

  1	192.168.0.1       	6 ms      	8 ms      	
  2	41.181.221.2      	27 ms     	27 ms     	
  3	41.181.198.1      	20 ms     	28 ms     	
  4	196.44.18.2       	25 ms     	57 ms     	
  5	196.44.31.1       	31 ms     	17 ms     	
  6	196.44.31.6       	52 ms     	
   	196.44.31.9       	40 ms     	
  7	196.30.1.5        	59 ms     	40 ms     	
  8	196.31.220.2      	50 ms     	43 ms     	
  9	196.31.63.2       	52 ms     	42 ms     	
 10	196.30.42.1       	51 ms     	41 ms     	
 11	197.242.144.1     	37 ms     	38 ms     	


traceroute -n 8.8.8.8

  1	192.168.0.1       	1 ms      	
  2	41.181.51.1       	13 ms     	
  3	41.181.198.1      	22 ms     	
  4	196.44.18.2       	27 ms     	
  5	196.44.31.1       	22 ms     	
  6	41.181.139.1      	33 ms     	
  7	72.14.194.7       	37 ms     	
  8	Request timed out 	*         	


DNS Test:

nslookup www.afrihost.com

Name:	www.afrihost.com
Address: 197.242.144.102


nslookup www.google.com

Name:	www.google.com
Address: 173.194.34.148
Name:	www.google.com
Address: 173.194.34.144
Name:	www.google.com
Address: 173.194.34.146
Name:	www.google.com
Address: 173.194.34.147
Name:	www.google.com
Address: 173.194.34.145


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN

MyBroadband Local Speedtest:

Last Result:
Download Speed: 1706 kbps (213.3 KB/sec transfer rate)
Upload Speed: 413 kbps (51.6 KB/sec transfer rate)
Latency: 33 ms
24 March 2014 08:35:04 AM

MyBroadband International speedtest:
Last Result:
Download Speed: 1682 kbps (210.3 KB/sec transfer rate)
Upload Speed: 394 kbps (49.3 KB/sec transfer rate)
Latency: 186 ms
24 March 2014 08:36:19 AM


Zertop Tool

Code:
Local Tracert 

Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:

  1     5 ms     3 ms     9 ms  H0M3nE11 [192.168.0.1] 
  2    23 ms    19 ms    19 ms  ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150] 
  3    12 ms    22 ms    16 ms  tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188] 
  4    27 ms    23 ms    29 ms  unc-cpt-1.mtnns.net [196.44.18.8] 
  5    29 ms    27 ms    22 ms  196.44.31.106 
  6    21 ms    19 ms    29 ms  nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121] 
  7    19 ms    29 ms    29 ms  196-28-178-141.adsl.mweb.co.za [196.28.178.141] 
  8    18 ms    29 ms    24 ms  197-84-7-1.cpt.mweb.co.za [197.84.7.1] 
  9    27 ms    29 ms    24 ms  197-84-5-238.cpt.mweb.co.za [197.84.5.238] 
 10    15 ms    26 ms    15 ms  196.28.178.66 
 11    24 ms    22 ms    29 ms  gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234] 
 12    16 ms    29 ms    25 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 13    24 ms    13 ms    13 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 14    22 ms    19 ms    20 ms  41-86-110-143.mweb.co.za [41.86.110.143] 

Trace complete.
  
International Tracert 

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

  1     7 ms     8 ms     5 ms  H0M3nE11 [192.168.0.1] 
  2    21 ms    22 ms    26 ms  41.181.51.182 
  3    23 ms    19 ms    19 ms  tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28] 
  4    21 ms    29 ms    25 ms  unc-cpt-1.mtnns.net [196.44.18.8] 
  5    30 ms    21 ms    20 ms  196.44.31.106 
  6   156 ms   174 ms   169 ms  am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.221] 
  7   170 ms   169 ms   159 ms  ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83] 
  8   168 ms   169 ms   159 ms  linx-gw1.thn.ncuk.net [195.66.224.240] 
  9   162 ms   162 ms   169 ms  gi1-24-10-star1.core-rs2.thdo.ncuk.net [80.249.97.9] 
 10   164 ms   159 ms   169 ms  www.thinkbroadband.com [80.249.99.130] 

Trace complete.
  
International Speedtest 
Downloaded 5120.0 kilobytes in 32 seconds. (159.15 KB/s)
  
Local Speedtest 
Downloaded 4000.0 kilobytes in 22 seconds. (180.42 KB/s)
  
  
  
  
Test End Timestamp 
2014/03/24  8:38:42.93
 
Last edited:
I just don't understand how it's not every single one of the people complaining about these issues?? There must be a common link. For example, if everyone is situated in Kirstenbosch, then there could be a fault with the KB Central MTN Exchange (which would be around hop 3/4 on the tracerts). This would therefore mean that only MTN accounts would have issues.

Could everyone having issues please post a tracert. Doesn't matter where to - I just want to see the paths being taken :)

Z

Here is your common link:

105-236-9-65-esr-lo.mtnbusiness.co.za
41.181.221.254

Both are on the MTN Network, and both cannot maintain a consistent, or respectable latency. This is true no matter where in Cape Town you are. If you do repeated trace routes, one after the other, you will see how the rates fluctuate. This should NOT happen...

If this were a car that had intermittent "flat spots" during acceleration, would you blame the car dealership, or would you have a mechanic look at the engine, accelerator, etc. It's quite funny how AH keeps claiming that it's congestion at the exchange, but the ESR at the exchange belongs to MTN. This is the main link between Telkom and AH... strange how NO other ISP's equipment
seems to suffer from erratic behaviour. Now, I admit that Telkom has it's own issues, but I think it's a "cop-out" to dump everything on their doorstep and refuse to look in AH's own back yard.
 
This is my opinion on the situation for what it's worth :-) Im not defending Afrihost, just presenting the facts.

1) Users demand cheap uncapped internet and daily they demand even cheaper products.
2) Telkom's IP Connect (IPC) products are super expensive per Mbps, the biggest cost of supplying ADSL for ISP's
3) The result of this is that ISP's CANNOT afford to have extra capacity laying around at the price point they selling at
4) Afrihost hits there IPC capacity limits, as it could just be a temporary trend they don't act on this immediately.
5) Afrihost then realizes they need extra IPC capacity
6) To obtain extra IPC from Telkom is a massive process, feasibility studies, contracts etc.
7) Telkom approves the capacity upgrade, the upgrades will take no less than 3-4 weeks
8) In the meantime Afrihost made their problems worse by offering free products....stupid
9) Before the upgrade happens Afrihost has to keep the network operational, this is done by shaping, throttling or if that is not the case then simply higher contention ratio on certain pools, you can't make bandwidth out of fresh air :-)

What is worrying:

1) No communication from Afrihost, network status is green :wtf:
2) Why are the support staff not informed about this, people are on the phone for hrs, running tests all for nothing...
3) What happened to Afriman, etc. They are usually active on the forums giving reassurance and updates on the situation

In my experience if you just upfront about the problem to your clients they are usually very understanding...the problem here is everyone is in the dark...so for them it's simple...if you can't get support or feedback just switch ISP's

In Afrihost's defence:

Telkom are the ones charging a premium on IPC, resulting in the ISP not being able to have extra capacity idle
Telkom are the ones who take ages to do IPC upgrades.

So who is really the ones to blame here...Afrihost or Telkom or both :-)
 
Just some added info.

When I signed up for this Business account, my ping to Cape Town servers was 7ms, and to JHB it was 12ms.
Now these are 12ms and 38ms, at any time of the day. There are occasions that these figures go to 30ms and 63ms.... and the longest hops are ALL MTN IP addresses.
 
Ok, if Afrihost has the IPC issues, then why give capped users extra free bandwidth? This really makes no sense at all, the system is under strain and then you increase the strain.
 
Just some added info.

When I signed up for this Business account, my ping to Cape Town servers was 7ms, and to JHB it was 12ms.
Now these are 12ms and 38ms, at any time of the day. There are occasions that these figures go to 30ms and 63ms.... and the longest hops are ALL MTN IP addresses.

Hmmmm....

Mine were in the 15's in CT and 30's to JHB in the 1st month I signed up... now sometimes, my ping to JHB is lower than my CT pings, and these are in the 60's... 2 months into this account and the average CT pings are in the 30's, JHB in the 60's and INT around 180's - 200's.
 
Here is your common link:

105-236-9-65-esr-lo.mtnbusiness.co.za
41.181.221.254

Both are on the MTN Network, and both cannot maintain a consistent, or respectable latency. This is true no matter where in Cape Town you are. If you do repeated trace routes, one after the other, you will see how the rates fluctuate. This should NOT happen...

If this were a car that had intermittent "flat spots" during acceleration, would you blame the car dealership, or would you have a mechanic look at the engine, accelerator, etc. It's quite funny how AH keeps claiming that it's congestion at the exchange, but the ESR at the exchange belongs to MTN. This is the main link between Telkom and AH... strange how NO other ISP's equipment
seems to suffer from erratic behaviour. Now, I admit that Telkom has it's own issues, but I think it's a "cop-out" to dump everything on their doorstep and refuse to look in AH's own back yard.

Okay cool - I will see what I can find! It really helps to know where the issue is. To use your car analogy - its like if the brakes in an old car fail, we are trying to figure out whether its the pedal, the hydraulics or the brake pads :P
 
Okay cool - I will see what I can find! It really helps to know where the issue is. To use your car analogy - its like if the brakes in an old car fail, we are trying to figure out whether its the pedal, the hydraulics or the brake pads :P

ITS THE IPC WHICH IS SATURATED ! PERIOD
 
This is my opinion on the situation for what it's worth :-) Im not defending Afrihost, just presenting the facts.

1) Users demand cheap uncapped internet and daily they demand even cheaper products.
2) Telkom's IP Connect (IPC) products are super expensive per Mbps, the biggest cost of supplying ADSL for ISP's
3) The result of this is that ISP's CANNOT afford to have extra capacity laying around at the price point they selling at
4) Afrihost hits there IPC capacity limits, as it could just be a temporary trend they don't act on this immediately.
5) Afrihost then realizes they need extra IPC capacity
6) To obtain extra IPC from Telkom is a massive process, feasibility studies, contracts etc.
7) Telkom approves the capacity upgrade, the upgrades will take no less than 3-4 weeks
8) In the meantime Afrihost made their problems worse by offering free products....stupid
9) Before the upgrade happens Afrihost has to keep the network operational, this is done by shaping, throttling or if that is not the case then simply higher contention ratio on certain pools, you can't make bandwidth out of fresh air :-)

What is worrying:

1) No communication from Afrihost, network status is green :wtf:
2) Why are the support staff not informed about this, people are on the phone for hrs, running tests all for nothing...
3) What happened to Afriman, etc. They are usually active on the forums giving reassurance and updates on the situation

In my experience if you just upfront about the problem to your clients they are usually very understanding...the problem here is everyone is in the dark...so for them it's simple...if you can't get support or feedback just switch ISP's

In Afrihost's defence:

Telkom are the ones charging a premium on IPC, resulting in the ISP not being able to have extra capacity idle
Telkom are the ones who take ages to do IPC upgrades.

So who is really the ones to blame here...Afrihost or Telkom or both :-)

I agree with you fully - however the Reps should be here today :) They like their weekends off :P

Anyway - I believe that the capacity AH has ordered has caused a bit of an issue? I dont actually know whats happened to it haha - it seems to be just taking its time?

If they were to change their network status - users get a bit worried. Anyway, they are just implementing shaping which is stated in the AUP :/

Their support is definitely getting better! :)

Z
 
ITS THE IPC WHICH IS SATURATED ! PERIOD

Yes. But I dont have issues on any of my accounts? Business is profiled exactly as capped, so it should be performing exactly the same! So then why, if its an IPC issue (which affect all Afrihost accounts), do some accounts work just fine?

Thats why I believe its a business routing issue in Cape Town, causing issues with the accounts?

Z
 
Ok, if Afrihost has the IPC issues, then why give capped users extra free bandwidth? This really makes no sense at all, the system is under strain and then you increase the strain.

This I agree with. Shouldn't have happened - but I guess there was a reason :) Remember, us users were begging for upgrades! They couldn't just give JHB users the deals :P So when they applied it network-wide, it took the South with it :(

Z
 
Hmmmm....

Mine were in the 15's in CT and 30's to JHB in the 1st month I signed up... now sometimes, my ping to JHB is lower than my CT pings, and these are in the 60's... 2 months into this account and the average CT pings are in the 30's, JHB in the 60's and INT around 180's - 200's.

CPT ~ 8ms
JHB ~ 25ms
INT ~ 175ms (to uk)

Strange how its different? Then again, these are tests from Home Uncapped and Capped - I dont really have a business account anymore :erm:
 
I agree with you fully - however the Reps should be here today :) They like their weekends off :P

Anyway - I believe that the capacity AH has ordered has caused a bit of an issue? I dont actually know whats happened to it haha - it seems to be just taking its time?

If they were to change their network status - users get a bit worried. Anyway, they are just implementing shaping which is stated in the AUP :/

Their support is definitely getting better! :)

Z

I think at the price we pay, and the confirmed Support staff issues, there should be reps or someone from Afrihost online 24/7, sorry this is unacceptable
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X