Afrihost Capped DSL Feedback

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.

Hi AF,

I fully agree that one must always put things in perspective, that is why I usually try and relate my experiences between different ISP's on exactly the same points. I am truly sorry that you appear to take some offence to my comments, but fact is - in all my recent fault logs I always refer to the exact same game (feel free to check my posts) .... it is always a PWE's Forsaken World.

With reference to post # 2222, where you claim the only difference is jitter - please have a look at the screen shots of in game latency: Afrihost = 550 ms and ISPAfrika = 205 ms. For the record (again, please feel free to check my log), when I noticed the high in game latency on my AH account I logged out from AH, logged in on ISPAfika took a screen shot (15:30) and logged out on ISPAfrika and logged back in on AH and then took the AH screen shot (15:54) of in game latency. I honestly do not understand why you feel that I am being possibly biased in my test results and are taking up this defensive stance. All I am trying to do is to point out that there are possibly some issues at hand. Again, please accept my apologies if you feel that my posts are perceived to be anything else.

I have been with AH for many years (with the odd break in between, when I got fed up with the lack of transparency) and I do honestly believe that my comments/observations were kept to be factual to the best of my abilities without making accusations/threats etc.

I am sure you are also aware (or should be) that when the unshaped/shaped capped options were introduced, I was initially on a unshaped capped.

The bottom line for me based on my observations is this (specifically to the PWE game Forsaken World) - ISPAfrika seems to have lower in game latency as opposed to AH and the round trip results to this games server in Europe is 10 ms faster on ISPAfrika than what it is on AH.

Based on these facts and the comment you made specifically on this game (refer to post # 2133) that it is possibly affected by AH's shaping policy, that I made my request regarding AH's shaping policy details (which I note remains unanswered).
 
Last edited:
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

Looks pretty consistent with a 4Mbps line. :)
 
Hi AF,

I fully agree that one must always put things in perspective, that is why I usually try and relate my experiences between different ISP's on exactly the same points. I am truly sorry that you appear to take some offence to my comments, but fact is - in all my recent fault logs I always refer to the exact same game (feel free to check my posts) .... it is always a PWE's Forsaken World.

With reference to post # 2222, where you claim the only difference is jitter - please have a look at the screen shots of in game latency: Afrihost = 550 ms and ISPAfrika = 205 ms. For the record (again, please feel free to check my log), when I noticed the high in game latency on my AH account I logged out from AH, logged in on ISPAfika took a screen shot (15:30) and logged out on ISPAfrika and logged back in on AH and then took the AH screen shot (15:54) of in game latency. I honestly do not understand why you feel that I am being possibly biased in my test results and are taking up this defensive stance. All I am trying to do is to point out that there are possibly some issues at hand. Again, please accept my apologies if you feel that my posts are perceived to be anything else.

I have been with AH for many years (with the odd break in between, when I got fed up with the lack of transparency) and I do honestly believe that my comments/observations were kept to be factual to the best of my abilities without making accusations/threats etc.

I am sure you are also aware (or should be) that when the unshaped/shaped capped options were introduced, I was initially on a unshaped capped.

The bottom line for me based on my observations is this (specifically to the PWE game Forsaken World) - ISPAfrika seems to have lower in game latency as opposed to AH and the round trip results to this games server in Europe is 10 ms faster on ISPAfrika than what it is on AH.

Based on these facts and the comment you made specifically on this game (refer to post # 2133) that it is possibly affected by AH's shaping policy, that I made my request regarding AH's shaping policy details (which I note remains unanswered).

Thanks for clarifying. :) Please don't think I took any offense. We're here to discuss experience as well as facilitate support between yourselves and the relevant technicians that can assist with your queries. :)

I'm sorry for having missed the latency spike between your Afrihost test and ISPAfrica.

Regarding our Shaping policy, I think it has been discussed in this forum at length before, with the basic gist being that non-realtime protocols dynamically get shaped, and Shaped Capped get's shaped on different levels than Uncapped, based on network activity. More info here.

As I mentioned, I'm unfamiliar with the game in question and don't know what protocols it uses to connect online. What I mentioned was that it's possible this game uses non-realtime protocols, but it was just a suggestion.

Please allow our Critical Care Team to contact you and address your query in more detail. :)
 
Thanks for clarifying. :) Please don't think I took any offense. We're here to discuss experience as well as facilitate support between yourselves and the relevant technicians that can assist with your queries. :)

I'm sorry for having missed the latency spike between your Afrihost test and ISPAfrica.

Regarding our Shaping policy, I think it has been discussed in this forum at length before, with the basic gist being that non-realtime protocols dynamically get shaped, and Shaped Capped get's shaped on different levels than Uncapped, based on network activity. More info here.

As I mentioned, I'm unfamiliar with the game in question and don't know what protocols it uses to connect online. What I mentioned was that it's possible this game uses non-realtime protocols, but it was just a suggestion.

Please allow our Critical Care Team to contact you and address your query in more detail. :)

Critical Care did get involved quite some time ago ( I have been actively been playing FW for the past ~6 years) - sadly no conclusion was reached (hints of exchange congestion etc was passed from time to time), hence my reluctance to get involved in this exercise. This time I know for sure that it is not exchange congestion related.

I was considering a last option and that was to switch back to an unshaped capped account, but I am currently not sure if this is the way to go for me - as a last resort I suppose I have two options available, either accept the current situation and refrain from adding comments to this forum, or move on.

Thanks for the support on this subject thus far.
 
Critical Care did get involved quite some time ago ( I have been actively been playing FW for the past ~6 years) - sadly no conclusion was reached (hints of exchange congestion etc was passed from time to time), hence my reluctance to get involved in this exercise. This time I know for sure that it is not exchange congestion related.

I was considering a last option and that was to switch back to an unshaped capped account, but I am currently not sure if this is the way to go for me - as a last resort I suppose I have two options available, either accept the current situation and refrain from adding comments to this forum, or move on.

Thanks for the support on this subject thus far.

I think it's definitely worth revisiting your complaint as we're not seeing any general issues on our network at the moment. Please let me know the oucome of your troubleshooting with CC. :)
 
I'm really sick and tired of terrible international latency on Afrihost in games. Some days it's fine, tonight clearly not.

Trying my best to be rude, but please, understand my frustrations as this has been ongoing for a very long time with no resolution.

Heroes of the Storm EU trace

kMiIE7c.png


Ping to bras

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms 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 = 11ms, Maximum = 11ms, Average = 11ms

In-game latency

iDu3BEf.png


Same trace from Vox

EZckdws.png


Just look at the difference.
 
I'm really sick and tired of terrible international latency on Afrihost in games. Some days it's fine, tonight clearly not.

Trying my best to be rude, but please, understand my frustrations as this has been ongoing for a very long time with no resolution.

Heroes of the Storm EU trace

kMiIE7c.png


Ping to bras

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms 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 = 11ms, Maximum = 11ms, Average = 11ms

In-game latency

iDu3BEf.png


Same trace from Vox

EZckdws.png


Just look at the difference.

That's not great at all! :( Which DNS servers are you using with us at the moment?
 
Really slow tonight. Can't even watch a YouTube video on lowest quality
 
Having the same issues on world of warcraft.
Code:
tracert 80.239.149.77

Tracing route to 80-239-149-77.customer.teliacarrier.com [80.239.149.77]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.0.0.2
  2     *        *        *     Request timed out.
  3    34 ms    33 ms    33 ms  cpt-tx2.ip.adsl.co.za [169.1.5.81]
  4    42 ms    40 ms    40 ms  169-1-21-54.ip.afrihost.co.za [169.1.21.54]
  5   168 ms     *      172 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6   134 ms   125 ms   121 ms  41.164.52.40
  7    39 ms    35 ms    34 ms  ix-ae-7-0.tcore1.KLT-Cape-Town.as6453.net [41.206.164.53]
  8   203 ms   200 ms   186 ms  if-ae-5-2.tcore2.PV9-Lisbon.as6453.net [80.231.159.61]
  9   191 ms   183 ms   184 ms  if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
 10   190 ms   191 ms   190 ms  if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
 11   305 ms   302 ms     *     if-ae-19-2.tcore2.L78-London.as6453.net [80.231.138.22]
 12   232 ms   263 ms   200 ms  if-ae-15-2.tcore2.LDN-London.as6453.net [80.231.131.118]
 13   206 ms   203 ms   202 ms  ldn-b5-link.telia.net [62.115.9.173]
 14   233 ms   238 ms   244 ms  ldn-bb2-link.telia.net [80.91.246.146]
 15   219 ms   213 ms   217 ms  hbg-bb4-link.telia.net [80.91.247.198]
 16   355 ms   381 ms   421 ms  war-b2-link.telia.net [80.91.247.135]
 17   313 ms   326 ms   341 ms  80-239-149-77.customer.teliacarrier.com [80.239.149.77]

Trace complete.

Code:
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=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms 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 = 22ms, Maximum = 24ms, Average = 22ms
 
Top
Sign up to the MyBroadband newsletter
X