Afrihost Capped DSL Feedback

Igor III said:
After struggling to stay connected to PWE's Forsaken World, I performed speed tests on the following 3 ISP's

Afrihost

View attachment 441814

WebAfrika

View attachment 441816

ISPAfrika

View attachment 441818

The only noticeable difference between the three is the amount of jitter I have (this is on a 10 mb/s fiber line) and of course the in game ping levels (AH is more than double that of ISPA - not sure if it is due to shaping or something else)
Click to expand...

You should be seeing similar latencies with us, I'm going to ask our Critical Care Team to look into this. Can you please PM me your details and I'll get them on this. The Critical Care Team will definitely be able to figure out what's going on and get to the bottom of it!
 
Dstv streaming really struggling currently.

Seems I really need to rethink my full time Afrihost return.
Code: 
 Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2    <1 ms    <1 ms    <1 ms  10.100.0.1 
  3     *        *        *     Request timed out.
  4    20 ms    19 ms    18 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  5   128 ms   125 ms   120 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  6    38 ms    40 ms    46 ms  optinet.ixp.capetown [196.10.140.15] 
  7   155 ms   160 ms   160 ms  te0-0-0-1.cpt-p-2.optinet.net [197.84.7.34] 
  8    19 ms    19 ms    19 ms  vl11.cpt-hscore-1.optinet.net [197.84.5.238] 
  9   120 ms   117 ms   117 ms  196.28.178.66 
 10    68 ms    69 ms    78 ms  gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234] 
 11   153 ms   141 ms   140 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 12   123 ms   120 ms   122 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 13   129 ms     *      117 ms  41-86-110-200.mweb.co.za [41.86.110.200] 

Trace complete.

This is on an unshaped account.
 
standerr said:
Is anybody willing to stick their necks out regarding the Afrihost network lately? Especially in the South and later afternoon/evening? Thinking of switching back, but need to know if the latency issues we had a few months ago has been sorted?
Click to expand...

No issues from my side for awhile now, and I am on shaped account. I don't torrent though. Real time works perfectly for me.
 
AfriGenie said:
Is the streaming not running as well as it should? Are you seeing buffering? What do your speedtests look like?
Click to expand...

Lots of buffering, streaming on YT and Twitch is bad. Speedtest is fine, once again it's throughput.

This is a Twitch stream
2a9aff64ae.png
 
obviously they are shaping everything else so the people that are streaming and watching youtube wont complain and they have enough ipc Really!!!
 
AfriGenie said:
You should be seeing similar latencies with us, I'm going to ask our Critical Care Team to look into this. Can you please PM me your details and I'll get them on this. The Critical Care Team will definitely be able to figure out what's going on and get to the bottom of it!
Click to expand...

Hi AfriGenie,

I am not sure if your Critical Care Team will be able to assist, for the following two reasons:

According to AfriFella, it is very possible that the game in question is affected by AH's shaping policies:

AfriFella said:
I think it's worth checking what protocols the game in question is using. If their not unique and something our shaping software identifies as a non-realtime service, you might definitely be affected by shaping. Out of interest, have you compared your experience with an Unshaped Caped account?
Click to expand...

And the fact that there is a difference between the response times of AH and ISPA on the game server (albeit only ~10ms)

Afrihost:

C:\Users\Igor III>ping fweu1.en.perfectworld.eu

Pinging fweu1.en.perfectworld.eu [95.172.91.23] with 32 bytes of data:
Reply from 95.172.91.23: bytes=32 time=181ms TTL=45
Reply from 95.172.91.23: bytes=32 time=181ms TTL=45
Reply from 95.172.91.23: bytes=32 time=181ms TTL=45
Reply from 95.172.91.23: bytes=32 time=181ms TTL=45

Ping statistics for 95.172.91.23:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 181ms, Maximum = 181ms, Average = 181ms

ISPAfrika:

C:\Users\Igor III>ping fweu1.en.perfectworld.eu

Pinging fweu1.en.perfectworld.eu [95.172.91.23] with 32 bytes of data:
Reply from 95.172.91.23: bytes=32 time=170ms TTL=51
Reply from 95.172.91.23: bytes=32 time=170ms TTL=51
Reply from 95.172.91.23: bytes=32 time=170ms TTL=51
Reply from 95.172.91.23: bytes=32 time=171ms TTL=51

Ping statistics for 95.172.91.23:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 170ms, Maximum = 171ms, Average = 170ms

To quote AH's on the shaping of capped accounts, the following statement is made on your website:

Shaping on Capped DSL
To put things in perspective, Capped Data is the last broadband product in the queue for potential shaping.

~snip~

Thus, the likelihood of Capped Data being shaped is extremely low.

Yet, based on what the recent comments on this thread show is that shaping of capped accounts seems to be the opposite of what is stated.

For pure inquisitiveness, would it be possible to share with us the available stats that AH have on (a) the frequency (e.g. % on a daily/weekly/monthly basis) that capped accounts are shaped and (b) the severity of the shaping (e.g. - 10%/ - 20%/ - 30% etc.)
 
So was trying to watch twitch tonight. Was unable to make use of Afrihost and had to swap to ISPAfrika where the stream was perfect.

I have seen problems with your tcore routes before while gaming. I pretty much need two accounts at this time. Afrihost for general use and another for gaming/when tcore decides to screw with EU routes.

ISPAfrika:
W6eRdng.png


Afrihost:
gUCOW9ag.png
 
standerr said:
Dstv streaming really struggling currently.

Seems I really need to rethink my full time Afrihost return.
Code: 
 Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2    <1 ms    <1 ms    <1 ms  10.100.0.1 
  3     *        *        *     Request timed out.
  4    20 ms    19 ms    18 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  5   128 ms   125 ms   120 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  6    38 ms    40 ms    46 ms  optinet.ixp.capetown [196.10.140.15] 
  7   155 ms   160 ms   160 ms  te0-0-0-1.cpt-p-2.optinet.net [197.84.7.34] 
  8    19 ms    19 ms    19 ms  vl11.cpt-hscore-1.optinet.net [197.84.5.238] 
  9   120 ms   117 ms   117 ms  196.28.178.66 
 10    68 ms    69 ms    78 ms  gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234] 
 11   153 ms   141 ms   140 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 12   123 ms   120 ms   122 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 13   129 ms     *      117 ms  41-86-110-200.mweb.co.za [41.86.110.200] 

Trace complete.

This is on an unshaped account.
Click to expand...

Mind dropping me a PM with your account details?
 
roadcat said:
No issues from my side for awhile now, and I am on shaped account. I don't torrent though. Real time works perfectly for me.
Click to expand...

Really great feedback! Glad your connection is on point, roadcat! :D
 
electrofreeze said:
obviously they are shaping everything else so the people that are streaming and watching youtube wont complain and they have enough ipc Really!!!
Click to expand...

Not sure what point you're making here, electrofreeze? Perhaps switching over to an Unshaped Capped package will solve the issues you have with our shaping policy?
 
Igor III said:
Hi AfriGenie,

I am not sure if your Critical Care Team will be able to assist, for the following two reasons:

According to AfriFella, it is very possible that the game in question is affected by AH's shaping policies:



And the fact that there is a difference between the response times of AH and ISPA on the game server (albeit only ~10ms)

Afrihost:

C:\Users\Igor III>ping fweu1.en.perfectworld.eu

Pinging fweu1.en.perfectworld.eu [95.172.91.23] with 32 bytes of data:
Reply from 95.172.91.23: bytes=32 time=181ms TTL=45
Reply from 95.172.91.23: bytes=32 time=181ms TTL=45
Reply from 95.172.91.23: bytes=32 time=181ms TTL=45
Reply from 95.172.91.23: bytes=32 time=181ms TTL=45

Ping statistics for 95.172.91.23:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 181ms, Maximum = 181ms, Average = 181ms

ISPAfrika:

C:\Users\Igor III>ping fweu1.en.perfectworld.eu

Pinging fweu1.en.perfectworld.eu [95.172.91.23] with 32 bytes of data:
Reply from 95.172.91.23: bytes=32 time=170ms TTL=51
Reply from 95.172.91.23: bytes=32 time=170ms TTL=51
Reply from 95.172.91.23: bytes=32 time=170ms TTL=51
Reply from 95.172.91.23: bytes=32 time=171ms TTL=51

Ping statistics for 95.172.91.23:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 170ms, Maximum = 171ms, Average = 170ms

To quote AH's on the shaping of capped accounts, the following statement is made on your website:

Shaping on Capped DSL
To put things in perspective, Capped Data is the last broadband product in the queue for potential shaping.

~snip~

Thus, the likelihood of Capped Data being shaped is extremely low.

Yet, based on what the recent comments on this thread show is that shaping of capped accounts seems to be the opposite of what is stated.

For pure inquisitiveness, would it be possible to share with us the available stats that AH have on (a) the frequency (e.g. % on a daily/weekly/monthly basis) that capped accounts are shaped and (b) the severity of the shaping (e.g. - 10%/ - 20%/ - 30% etc.)
Click to expand...

I think it's important to put things in perspective here. The reply you've quoted from me is a reply based on the fact that you were querying performance of one specific game where I was uncertain which protocols were being used. I don't think it's fair to translate that across - and into your entire internet experience. Your tests also indicate similar results on all ISP accounts you mentioned, but for jitter.

I would suggest that you give our CC Team a chance to contact you and work with you to troubleshoot the cause of this, as Genie suggested. I'll follow up with them from my side too.
 
Karel Kat said:
So was trying to watch twitch tonight. Was unable to make use of Afrihost and had to swap to ISPAfrika where the stream was perfect.

I have seen problems with your tcore routes before while gaming. I pretty much need two accounts at this time. Afrihost for general use and another for gaming/when tcore decides to screw with EU routes.

ISPAfrika:
W6eRdng.png


Afrihost:
gUCOW9ag.png
Click to expand...

Not seeing a huge difference between these two traces, to be honest. What DNS settings are you using?
 
Some random testing…4mb line…router stats 5120kps down 512kbps up.

Shaped capped account


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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 29 ms 27 ms 26 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 30 ms 27 ms 27 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 27 ms 26 ms 26 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 29 ms 29 ms 26 ms 196-10-140-198.ixp.capetown [196.10.140.198]
7 27 ms 28 ms 27 ms 104.20.31.244

Trace complete.

C:\Windows\system32>ping bras.afrihost.com

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=27ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 27ms, Average = 25ms




MyBB Speedtest Johannesburg
Ping: 47ms
Download: 3.84Mbps
Upload: 0.25Mbps


MyBB Speedtest Cape Town
Ping: 26ms
Download: 4.07Mbps
Upload: 0.25Mbps
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X