Afrihost Business Uncapped Feedback

Status
Not open for further replies.
Here ... WebAfrica

View attachment 113112

View attachment 113114

View attachment 113116


Code:
Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=55 time=35 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=55 time=51 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=55 time=37 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=55 time=36 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=55 time=39 ms


ping 8.8.8.8

Request timeout for icmp_seq 1
64 bytes from 8.8.8.8: icmp_req=2 ttl=45 time=183 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=45 time=188 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=45 time=185 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=45 time=185 ms


Trace Test:

traceroute -n 197.242.144.102

  1	192.168.0.1       	1 ms      	1 ms      	1 ms      	
  2	196.38.72.1       	13 ms     	18 ms     	18 ms     	
  3	196.35.115.1      	17 ms     	16 ms     	15 ms     	
  4	168.209.2.1       	18 ms     	
   	168.209.6.1       	16 ms     	16 ms     	
  5	41.208.29.2       	17 ms     	
   	168.209.2.1       	16 ms     	17 ms     	
  6	196.44.0.7        	35 ms     	
   	41.208.29.2       	18 ms     	16 ms     	
  7	196.44.31.6       	37 ms     	37 ms     	
   	196.44.0.7        	16 ms     	
  8	196.44.31.9       	35 ms     	
   	196.44.0.2        	38 ms     	35 ms     	
  9	196.30.1.3        	38 ms     	37 ms     	36 ms     	
 10	196.31.220.2      	35 ms     	39 ms     	36 ms     	
 11	196.30.42.1       	36 ms     	
   	196.31.63.2       	37 ms     	34 ms     	
 12	197.242.144.1     	36 ms     	39 ms     	
   	196.30.42.1       	36 ms     	
 13	197.242.144.1     	33 ms     	


traceroute -n 8.8.8.8

  1	192.168.0.1       	1 ms      	1 ms      	
  2	196.38.72.1       	12 ms     	15 ms     	
  3	196.35.115.1      	21 ms     	19 ms     	
  4	168.209.2.1       	16 ms     	18 ms     	
  5	168.209.2.1       	17 ms     	16 ms     	
  6	168.209.100.1     	37 ms     	36 ms     	
  7	196.26.0.1        	35 ms     	36 ms     	
  8	74.125.49.6       	39 ms     	
   	Request timed out 	*         	
  9	66.249.95.8       	189 ms    	
 10	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: 74.125.233.82
Name:	www.google.com
Address: 74.125.233.81
Name:	www.google.com
Address: 74.125.233.83
Name:	www.google.com
Address: 74.125.233.80
Name:	www.google.com
Address: 74.125.233.84


nslookup thishouldfail.afrihost.com

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

ROCKS! :D
 
And Incredible Connection

View attachment 113118

View attachment 113120

View attachment 113122


Code:
Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=54 time=33 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=54 time=34 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=54 time=35 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=54 time=43 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=54 time=39 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=46 time=191 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=46 time=181 ms
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
64 bytes from 8.8.8.8: icmp_req=5 ttl=46 time=184 ms


Trace Test:

traceroute -n 197.242.144.102

  1	192.168.0.1       	1 ms      	1 ms      	1 ms      	
  2	196.38.72.1       	13 ms     	13 ms     	19 ms     	
  3	196.35.115.1      	15 ms     	16 ms     	16 ms     	
  4	168.209.2.1       	14 ms     	16 ms     	16 ms     	
  5	168.209.2.1       	14 ms     	11 ms     	16 ms     	
  6	41.208.29.2       	14 ms     	16 ms     	
   	196.44.0.7        	21 ms     	
  7	196.44.0.7        	12 ms     	13 ms     	
   	196.44.31.6       	36 ms     	
  8	196.44.31.6       	46 ms     	
   	196.44.0.2        	35 ms     	41 ms     	
  9	196.44.0.2        	32 ms     	
   	196.31.220.1      	37 ms     	37 ms     	
 10	196.31.220.1      	37 ms     	
   	196.31.220.2      	33 ms     	33 ms     	
 11	196.31.63.2       	32 ms     	37 ms     	36 ms     	
 12	196.30.42.1       	36 ms     	32 ms     	
   	197.242.144.1     	31 ms     	
 13	197.242.144.1     	40 ms     	37 ms     	


traceroute -n 8.8.8.8

  1	192.168.0.1       	1 ms      	2 ms      	
  2	196.38.72.1       	16 ms     	12 ms     	
  3	196.35.115.1      	14 ms     	17 ms     	
  4	168.209.6.1       	17 ms     	17 ms     	
  5	168.209.2.1       	17 ms     	16 ms     	
  6	168.209.100.1     	36 ms     	37 ms     	
  7	168.209.1.1       	31 ms     	31 ms     	
  8	74.125.49.6       	35 ms     	47 ms     	
  9	66.249.95.8       	181 ms    	180 ms    	
 10	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.176
Name:	www.google.com
Address: 173.194.34.180
Name:	www.google.com
Address: 173.194.34.177
Name:	www.google.com
Address: 173.194.34.178
Name:	www.google.com
Address: 173.194.34.179


nslookup thishouldfail.afrihost.com

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

ROCKS! :D
 
bleh ... other ISPs are fine. Zero issues and have been since February when I began to rely on them rather than this AH Business account.

I have done endless ISP comparisons...
I will do the last few here again...
but I am NOT going to run over to the router and do it via cable, and I am also NOT going to go the whole Telkom line / exchange fault logging route again or the futile hoop-jumping tracert PM shebang.

I've had a few clients and partners run tests for me in CT, so far seeing great results. I've seen the results you posted so far, definitely something not kosher - not sure what line speed you are syncing on (guessing 2Mbps).

Does anyone else have some results they can post here?
 
I've had a few clients and partners run tests for me in CT, so far seeing great results. I've seen the results you posted so far, definitely something not kosher - not sure what line speed you are syncing on (guessing 2Mbps).

Does anyone else have some results they can post here?

On Server back Home (Somerset West, Cape Town)

Code:
Local Tracert 

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

  1     1 ms    <1 ms    <1 ms  10.0.0.1 
  2     8 ms     8 ms     8 ms  105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193] 
  3     9 ms     9 ms    12 ms  ipc-send-tb-3a.mtnbusiness.net [41.181.53.214] 
  4     9 ms    15 ms     9 ms  tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188] 
  5    10 ms    10 ms     9 ms  unc-cpt-1.mtnns.net [196.44.18.8] 
  6    11 ms    10 ms    10 ms  196.44.31.106 
  7    10 ms     9 ms     9 ms  nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121] 
  8    11 ms    10 ms    10 ms  196-28-178-141.adsl.mweb.co.za [196.28.178.141] 
  9    15 ms    13 ms    13 ms  197-84-7-1.cpt.mweb.co.za [197.84.7.1] 
 10    11 ms    10 ms    10 ms  197-84-5-254.cpt.mweb.co.za [197.84.5.254] 
 11    11 ms    10 ms    11 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70] 
 12    11 ms    11 ms    10 ms  gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166] 
 13    12 ms    11 ms    11 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 14    11 ms    11 ms    11 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 15    11 ms    11 ms    11 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    <1 ms    <1 ms    <1 ms  10.0.0.1 
  2    10 ms     7 ms     7 ms  105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193] 
  3     9 ms     9 ms     9 ms  ipc-send-tb-3a.mtnbusiness.net [41.181.53.214] 
  4     9 ms     9 ms     9 ms  tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28] 
  5    10 ms     9 ms     9 ms  unc-cpt-1.mtnns.net [196.44.18.8] 
  6    11 ms    10 ms     9 ms  196.44.31.106 
  7   153 ms   153 ms   153 ms  am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.221] 
  8   153 ms   152 ms   152 ms  ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83] 
  9   153 ms   153 ms   153 ms  linx-gw1.thn.ncuk.net [195.66.224.240] 
 10   154 ms   153 ms   155 ms  gi1-24-10-star1.core-rs2.thdo.ncuk.net [80.249.97.9] 
 11   153 ms   154 ms   153 ms  www.thinkbroadband.com [80.249.99.130] 

Trace complete.


International Speedtest
Downloaded 20.0 megabytes in 20 seconds. (996.01 KB/s)

Local Speedtest
Downloaded 15.6 megabytes in 19 seconds. (823.85 KB/s)

Test End Timestamp
2014/04/18 12:28:42.79
 
I do see Telkom has listed some outages for the CPT area - might be causing some confusion:

TableView, Stikland, Wynberg, Milnerton, Waverly Business Park, Ladismith, Montague - could be more according to another ISP's notice board.

Some areas in KZN also down:

Riverhorse Valley, Alton, Gateway, Southgate

Just in case people in those areas are wondering if the upgrades haven't taken properly.
 
On Server back Home (Somerset West, Cape Town)

Code:
Local Tracert 

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

  1     1 ms    <1 ms    <1 ms  10.0.0.1 
  2     8 ms     8 ms     8 ms  105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193] 
  3     9 ms     9 ms    12 ms  ipc-send-tb-3a.mtnbusiness.net [41.181.53.214] 
  4     9 ms    15 ms     9 ms  tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188] 
  5    10 ms    10 ms     9 ms  unc-cpt-1.mtnns.net [196.44.18.8] 
  6    11 ms    10 ms    10 ms  196.44.31.106 
  7    10 ms     9 ms     9 ms  nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121] 
  8    11 ms    10 ms    10 ms  196-28-178-141.adsl.mweb.co.za [196.28.178.141] 
  9    15 ms    13 ms    13 ms  197-84-7-1.cpt.mweb.co.za [197.84.7.1] 
 10    11 ms    10 ms    10 ms  197-84-5-254.cpt.mweb.co.za [197.84.5.254] 
 11    11 ms    10 ms    11 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70] 
 12    11 ms    11 ms    10 ms  gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166] 
 13    12 ms    11 ms    11 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 14    11 ms    11 ms    11 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 15    11 ms    11 ms    11 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    <1 ms    <1 ms    <1 ms  10.0.0.1 
  2    10 ms     7 ms     7 ms  105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193] 
  3     9 ms     9 ms     9 ms  ipc-send-tb-3a.mtnbusiness.net [41.181.53.214] 
  4     9 ms     9 ms     9 ms  tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28] 
  5    10 ms     9 ms     9 ms  unc-cpt-1.mtnns.net [196.44.18.8] 
  6    11 ms    10 ms     9 ms  196.44.31.106 
  7   153 ms   153 ms   153 ms  am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.221] 
  8   153 ms   152 ms   152 ms  ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83] 
  9   153 ms   153 ms   153 ms  linx-gw1.thn.ncuk.net [195.66.224.240] 
 10   154 ms   153 ms   155 ms  gi1-24-10-star1.core-rs2.thdo.ncuk.net [80.249.97.9] 
 11   153 ms   154 ms   153 ms  www.thinkbroadband.com [80.249.99.130] 

Trace complete.


International Speedtest
Downloaded 20.0 megabytes in 20 seconds. (996.01 KB/s)

Local Speedtest
Downloaded 15.6 megabytes in 19 seconds. (823.85 KB/s)

Test End Timestamp
2014/04/18 12:28:42.79

Looking pretty healthy there :)
 
I do see Telkom has listed some outages for the CPT area - might be causing some confusion:

TableView, Stikland, Wynberg, Milnerton, Waverly Business Park, Ladismith, Montague - could be more according to another ISP's notice board.

Some areas in KZN also down:

Riverhorse Valley, Alton, Gateway, Southgate

Just in case people in those areas are wondering if the upgrades haven't taken properly.

Thanks for the input... why would a Telkom reported outage in Wynberg only affect the Afrihost Business account?

Surely ALL accounts in this area would be affected?
 
Thanks for the input... why would a Telkom reported outage in Wynberg only affect the Afrihost Business account?

Surely ALL accounts in this area would be affected?

Yes. Do the other accounts work fine when you leave them on for a prolonged period? Otherwise something is wrong somewhere with regards to MTN routing :/ (I would say the account is at fault, but this seems to have been fixed for most users now)

Does Axxess work well?

Z
 
Thanks for the input... why would a Telkom reported outage in Wynberg only affect the Afrihost Business account?

Surely ALL accounts in this area would be affected?

If the exchange is not performing correctly, it could affect any account at random. Depends on how Telkom routes from the exchange and where the issue actually lies leading to it being reported as problematic/down. At best it does mean that test results are skewed in some way and could be misleading.
 
Yes. Do the other accounts work fine when you leave them on for a prolonged period? Otherwise something is wrong somewhere with regards to MTN routing :/ (I would say the account is at fault, but this seems to have been fixed for most users now)

Does Axxess work well?

Z

The other accounts work perfectly for as long as I am connected... days / weeks.

Axxess I will try again, but thought it would be pointless because they are Afrihost / MTN anyway.
 
My new ISP's account works awesome and I am in Cape Town

If one account works and another doesn't, I've learnt a long time ago to just choose the one that works, and not to go down the "troubleshooting with support" route, as that will just give you grey hairs and no solution, because you just go round and round in circles.
 
If one account works and another doesn't, I've learnt a long time ago to just choose the one that works, and not to go down the "troubleshooting with support" route, as that will just give you grey hairs and no solution, because you just go round and round in circles.

I can see how one might feel that way - but in my experience there is a way to find a solution 99.99% of the time - even to some genuinely strange things that no-one can initially explain. And if you can't, it's best to work with your service provider to find a mutually beneficial solution. At the end of it all, we're all here for mutual benefit - and that can only happen when we work together.

But it's each individual's choice, I guess :)
 
Definite improvement for me since Wednesday. Downloaded 755MB file from international site in 12 minutes. Average bit rate using FDM was about 1063KB/s on 10Mb line. On Wednesday the average bit rate was about half that.

Kewl!
 
Going to try a 925.3MB file just for fun...

Back in a bit.

<edit>

15 minutes for 925MB file, average line speed about 1055KB/s. A bit slower, but perfectly good.
 
Last edited:
I can see how one might feel that way - but in my experience there is a way to find a solution 99.99% of the time - even to some genuinely strange things that no-one can initially explain. And if you can't, it's best to work with your service provider to find a mutually beneficial solution. At the end of it all, we're all here for mutual benefit - and that can only happen when we work together.

But it's each individual's choice, I guess :)

Because the "other ISP" already works out the box, that is my solution already.

Out of interest, could you give me a hypothetical example (paint a picture) of what you would do in such a case?
 
Its funny, when I started in this (IT) business many moons ago we talked in baud. The first modem I ever worked with was 2.6kb (some here will probably be more venerable). We took information from a power-plant, ran it through an 'artificial intelligence' interface and suggested requirements for further maintenance or better maintenance schedules. I think I was around 21 at the time, it was all very exciting and a very long time ago.

At the time ZA had a surplus of electricity, in fact we almost had the cheapest electricity in the world. We even had a single power station dedicated to training technicians that was off the grid and people came from all over the globe to train there.

This has obviously all changed and gone away. We now have a deficit of electricity, and there is no longer a place to train new technicians, and the average consumer probably has to pay more than any other consumer in an equal economy worldwide.

Further, many large firms who are energy intensive have actually suffered worse power restrictions in the last two years than the average consumer (votes required for someone?).

Sorry for the rant, if you get your pirated movie at 50% speed, tough. If your business suffers as a result of speed loss, fine, complain.

But, remember some business did very well at 2.6kb, and would probably doing just fine now if it weren't for politics.

Phaedrus
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X