Afrihost Business Uncapped Feedback

Status
Not open for further replies.
So for the past week I have been watching TV shows on Hulu and streaming using netflix, I always select the highest quality available for a stream. I have not seen any buffering on my tablet, pc or xbox. I use a 10meg business uncapped account. So I can safely say I do not think the streaming issues that people are complaining about are directly related to Afrihosts network.

Maybe I am just one of the lucky ones?

Thank for this post, really helps to put things in perspective. I also believe that there isn't a general issue. But I just also want to be clear that I in no way deny that some clients are having a poor experience, ad we'll continue to test and troubleshoot with them to figure out why their experience differs from the norm.
 
With my 10mb Business account I too have zero problems streaming Netflix & Hulu in HD on my Xbox, PC, and Android devices. On my WDTV Live media box, however, Hulu sometimes has weird freezing/buffering problems (been behaving recently though). I've come to realize that performance can vary on different devices.

There is definitely no general Netflix or Hulu streaming issue on Afrihost's network (using a 10mb unshaped account, at least). Twitch isn't so hot though...

Thanks for posting this as well. Glad to hear that a few clients here on MyBB as also having a good experience :)
 
Why is rapidgator causing problems again? When I load the rapidgator home page through my Afrihost account, it displays "error 500 Redis server went away". When I load the same page by using vodacom's network on my cell phone, I don't get the error message. When I switch to wi-fi on my cell phone, I again get the error message

Is afrihost deliberately disabling rapidgator access?
 
Why is rapidgator causing problems again? When I load the rapidgator home page through my Afrihost account, it displays "error 500 Redis server went away". When I load the same page by using vodacom's network on my cell phone, I don't get the error message. When I switch to wi-fi on my cell phone, I again get the error message

Is afrihost deliberately disabling rapidgator access?

Nevermind, after resetting my modem, the problem seems to have been resolved.
 
I'm getting horrible latency - and I'm posting here as I can't even get to the afrihost homepage.
 
Ping Test:

ping 197.242.144.102

Request timeout for icmp_seq 1
64 bytes from 197.242.144.102: icmp_req=2 ttl=58 time=304 ms
Request timeout for icmp_seq 3
64 bytes from 197.242.144.102: icmp_req=4 ttl=58 time=480 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=58 time=428 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=45 time=433 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=45 time=325 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=45 time=392 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=45 time=296 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=45 time=426 ms


Trace Test:

traceroute -n 197.242.144.102

1 192.168.0.1 1 ms 1 ms 1 ms
2 196.44.31.6 225 ms
41.181.198.1 163 ms
3 196.30.42.1 149 ms
196.30.1.3 97 ms


traceroute -n 8.8.8.8

1 192.168.0.1 1 ms
2 Request timed out *
3 Request timed out *
4 Request timed out *


DNS Test:

nslookup www.afrihost.com

Name: www.afrihost.com
Address: 41.76.227.137


nslookup www.google.com

Name: www.google.com
Address: 74.125.224.145
Name: www.google.com
Address: 74.125.224.147
Name: www.google.com
Address: 74.125.224.148
Name: www.google.com
Address: 74.125.224.144
Name: www.google.com
Address: 74.125.224.146


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN
 
Issues.... international speeds have been terrible all day, and are now even worse - E I S H :(

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  home.gateway.pace.net [192.168.1.254] 
  2     7 ms     7 ms     7 ms  105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129] 
  3     9 ms     7 ms     8 ms  ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86] 
  4    26 ms    21 ms     8 ms  tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188] 
  5    10 ms     8 ms    59 ms  unc-cpt-1.mtnns.net [196.44.18.8] 
  6     9 ms     9 ms     9 ms  196.44.31.106 
  7     8 ms     8 ms     8 ms  nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121] 
  8    10 ms     9 ms     9 ms  196-28-178-141.adsl.mweb.co.za [196.28.178.141] 
  9    12 ms    11 ms    11 ms  tengig-0-0-0-1-cpt-p-1.mweb.co.za [197.84.7.1] 
 10    10 ms     9 ms    10 ms  vl-12-cpt-hscore-2.mweb.co.za [197.84.5.254] 
 11    11 ms    10 ms    10 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70] 
 12    11 ms     9 ms    10 ms  gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166] 
 13    10 ms    10 ms     9 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 14    10 ms    11 ms    10 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  home.gateway.pace.net [192.168.1.254] 
  2     7 ms     7 ms     7 ms  105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129] 
  3     8 ms     7 ms     7 ms  41.181.221.254 
  4     9 ms     9 ms     9 ms  tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28] 
  5     8 ms     8 ms     8 ms  unc-cpt-1.mtnns.net [196.44.18.8] 
  6     9 ms     9 ms     9 ms  196.44.31.106 
  7   151 ms   152 ms   151 ms  am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.221] 
  8   152 ms   151 ms   152 ms  ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83] 
  9   152 ms   151 ms   152 ms  linx-gw1.thn.ncuk.net [195.66.224.240] 
 10   152 ms   151 ms   151 ms  te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17] 
 11   153 ms   152 ms   156 ms  te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85] 
 12   152 ms   151 ms   152 ms  [url]www.thinkbroadband.com[/url] [80.249.99.130] 

Trace complete.
  
International Speedtest 
Downloaded 20.0 megabytes in 50 seconds. (406.00 KB/s)
  
Local Speedtest 
Downloaded 15.6 megabytes in 23 seconds. (680.73 KB/s)
  
  
  
  
Test End Timestamp 
2014/08/18 20:21:36.44

Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 105.236.13.129 with 32 bytes of data:
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=10ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=10ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=7ms TTL=254
Reply from 105.236.13.129: bytes=32 time=12ms TTL=254
Reply from 105.236.13.129: bytes=32 time=9ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=7ms TTL=254
Reply from 105.236.13.129: bytes=32 time=9ms TTL=254
Reply from 105.236.13.129: bytes=32 time=10ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=7ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=9ms TTL=254
Reply from 105.236.13.129: bytes=32 time=7ms TTL=254
Reply from 105.236.13.129: bytes=32 time=10ms TTL=254
Reply from 105.236.13.129: bytes=32 time=10ms TTL=254
Reply from 105.236.13.129: bytes=32 time=10ms TTL=254
Reply from 105.236.13.129: bytes=32 time=7ms TTL=254

Ping statistics for 105.236.13.129:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 7ms, Maximum = 12ms, Average = 8ms
 
2014/08/18 20:22:23.34

This hop seems to always be the issue in Cape Town:

unc-cpt-1.mtnns.net [196.44.18.8]

Erratic, unstable, and well, SLOW :p
 
Last edited:
Same in pe


Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=58 time=41 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=58 time=49 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=58 time=40 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=58 time=42 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=58 time=42 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=45 time=176 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=45 time=176 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=45 time=177 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=45 time=177 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=45 time=176 ms


Trace Test:

traceroute -n 197.242.144.102

1 192.168.178.1 * * *
2 105.236.10.65 9.049 ms 8.08 ms 7.949 ms
3 41.181.221.254 23.823 ms 18.13 ms 18.351 ms
4 41.181.198.188 18.808 ms 43.58 ms 19.129 ms
5 196.44.18.2 26.825 ms 27.86 ms 26.397 ms
6 196.44.31.134 20.661 ms 20.018 ms 19.596 ms
7 196.44.31.69 49.151 ms 48.944 ms 49.065 ms
8 196.44.31.97 47.83 ms
196.44.0.221 47.299 ms 47.249 ms
9 196.31.220.10 48.277 ms
196.31.220.12 41.9 ms
196.30.1.53 48.604 ms
10 196.31.220.21 48.736 ms 49.061 ms
196.31.220.25 121.967 ms
11 196.31.63.202 40.999 ms 41.263 ms
196.31.63.206 48.933 ms
12 196.30.42.133 41.193 ms 41.104 ms 41.314 ms
13 197.242.144.102 49.022 ms 47.75 ms 48.351 ms


traceroute -n 8.8.8.8

1 192.168.178.1 * * *
2 105.236.10.65 8.509 ms 7.855 ms 7.287 ms
3 41.181.54.86 25.699 ms 34.715 ms 25.528 ms
4 41.181.184.28 25.872 ms 27.421 ms 26.502 ms
5 196.44.18.8 33.138 ms 33.361 ms 33.167 ms
6 196.44.31.106 30.338 ms 26.591 ms 29.535 ms
7 196.44.31.221 178.643 ms 177.298 ms 176.616 ms
8 209.212.111.203 177.161 ms 177.697 ms 176.941 ms
9 209.212.99.13 177.464 ms 176.199 ms 176.692 ms
10 Request timed out * *
209.85.255.76 189.798 ms
11 209.85.253.196 170.961 ms
209.85.253.94 171.511 ms
209.85.245.2 177.766 ms
12 66.249.95.173 183.407 ms
72.14.232.134 206.05 ms 182.841 ms
13 8.8.8.8 175.586 ms 175.66 ms
216.239.47.83 177.765 ms
14 8.8.8.8 176.211 ms


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.41.83
Name: www.google.com
Address: 173.194.41.82
Name: www.google.com
Address: 173.194.41.84
Name: www.google.com
Address: 173.194.41.80
Name: www.google.com
Address: 173.194.41.81


nslookup thishouldfail.afrihost.com

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

This weekend i must admit, my speed wasn't half bad. Not sure if i was perhaps using other ppl's speeds this weekend (or maybe there were less people at home this week in CPT). My speeds was definitely a little better than usual.

Afriguy ? Maybe it was just my imagination? or maybe Something was altered on my account?
 
Last edited:
Hi Guys

This weekend my speed wasn't half bad. Not sure if i was using other ppl's speeds this weekend (or maybe there were less people at home this week in CPT). My speeds was definitely a little better than usual.

Afriguy ? Maybe it was just my imagination? or maybe Something was altered on my account?

Hello

No changes on our side but Sunday looked like a slow day in Cape Town. ;)
 
Damn, that must have been me causing the slowness then {Sorry , My bad guys}

My internet felt nice and fast, but then again. Maybe something went wrong causing other users in CPT to be affected to cause a slow day for them {opening up the pipes for me}

As i wasn't affected {well i was, but in a good way}
 
480p should be streaming fine on a 1mbit (it's technically 1mbit, so thats 1024K. To get bits to bytes , devide by 8)

1024 / 8 = 128kb per second {though you will never see full speed on any given telkom line, so you can gather 80% from that)

Say you get 95kb +- per second on average. (which should give a rough 5.7megs per minute)

a 4minute clip would then use about 22.8 megs {Most youtube clips downloaded is about 16-18megs for 4minute clips)
 
Shouldn't be too bad, but it could change depending on the source of the stream.

In Youtube under "stats for nerds" i get a peak stream rate of 450kbps opposed to the maximum of 1024kbps.

But im sure you have heard this many times before.
 
In Youtube under "stats for nerds" i get a peak stream rate of 450kbps opposed to the maximum of 1024kbps.

But im sure you have heard this many times before.

Have you run any comparison checks on this yet?
Any buffering?
 
Have you run any comparison checks on this yet?
Any buffering?

Any buffering? Do you mean any video playback?

It stutters like crazy.

And for comparison, I was watching a video about a phone review (which is about 59Min long) and that vid was buffering every 30 seconds, but another review on the same YT channel zero buffering, now have a look at this network gadget.

d8f1c4f73c.png


On the first video it wouldnt go above 35KB/s.
 
Any buffering? Do you mean any video playback?

It stutters like crazy.

And for comparison, I was watching a video about a phone review (which is about 59Min long) and that vid was buffering every 30 seconds, but another review on the same YT channel zero buffering, now have a look at this network gadget.

d8f1c4f73c.png


On the first video it wouldnt go above 35KB/s.

That's very weird :(
Are you using our DNS servers?
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X