Afrihost Capped DSL Feedback

I personally find that it is due to horrible quality international bandwidth with Afrihost. Can stream an 8k YouTube video with out an issue (Don't need or can't use 8k but just used for testing) thanks to Google having local servers but try to watch from an international server and everything falls apart.

Exactly this ^

nail.jpg
 
My line has been giving ups and downs as well. It's ok for one week then suddenly I can't stream any low quality vids from Youtube or FB. Buffers most of the time.

Youtube was buffering 3s, playing 3s, buffering 3s, playing 3s, around 7:15 this morning. Don't know how long it lasted, I gave up.
 
Hmmmm, that does seem like something more than a coincidence... And with the current name servers the Twitch stream has been stable the whole time?

It did maintain stability, but I started fiddling today again and it went belly up. Will continue testing...
 
It did maintain stability, but I started fiddling today again and it went belly up. Will continue testing...

Thanks! If it does look like there are some problematic DNS Servers, we need to get to the bottom of this!
 
This probably mean they are business ADSL lines, which means they have a different contention ratio to consumer ADSL lines, not so?

The connections are setup to use the exact same IPC, contention ratios and infrastructure as a regular DSL Line.
 
contention ratio usually means how many users share the same bandwidth like 10 to 1

Thanks... I did know what contention ratio means... I'm just not sure of the contention ratio on our network so I can't give specific numbers. :)
 
Anyone else having problems?

This is my ping on world of tanks EU:

Pinging ed-sl-b62.fe.core.pw [92.223.21.62] with 32 bytes of data:
Reply from 92.223.21.62: bytes=32 time=306ms TTL=46
Reply from 92.223.21.62: bytes=32 time=275ms TTL=46
Reply from 92.223.21.62: bytes=32 time=304ms TTL=46
Reply from 92.223.21.62: bytes=32 time=316ms TTL=46
Reply from 92.223.21.62: bytes=32 time=321ms TTL=46
Reply from 92.223.21.62: bytes=32 time=321ms TTL=46
Reply from 92.223.21.62: bytes=32 time=281ms TTL=46
Reply from 92.223.21.62: bytes=32 time=299ms TTL=46
Reply from 92.223.21.62: bytes=32 time=315ms TTL=46
Reply from 92.223.21.62: bytes=32 time=302ms TTL=46
Reply from 92.223.21.62: bytes=32 time=293ms TTL=46
Reply from 92.223.21.62: bytes=32 time=305ms TTL=46

And

Tracing route to ed-sl-b62.fe.core.pw [92.223.21.62]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 24 ms 20 ms 20 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
4 20 ms 20 ms 20 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 123 ms 113 ms 109 ms 41.164.52.40
6 146 ms 138 ms 150 ms ix-ae-7-0.tcore1.KLT-Cape-Town.as6453.net [41.206.164.53]
7 163 ms 164 ms 163 ms if-ae-5-2.tcore2.PV9-Lisbon.as6453.net [80.231.159.109]
8 272 ms 276 ms 295 ms if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
9 169 ms 169 ms 169 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
10 167 ms 166 ms 166 ms if-ae-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
11 163 ms 163 ms 163 ms if-ae-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
12 168 ms 168 ms 167 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
13 169 ms 169 ms 169 ms be3040.ccr21.lon01.atlas.cogentco.com [130.117.15.177]
14 273 ms 242 ms 217 ms be2871.ccr42.lon13.atlas.cogentco.com [154.54.58.185]
15 170 ms 170 ms 169 ms be12488.ccr42.ams03.atlas.cogentco.com [130.117.51.42]
16 169 ms 170 ms 169 ms be2413.rcr21.b038092-0.ams03.atlas.cogentco.com [154.54.37.242]
17 171 ms 170 ms 170 ms 149.11.65.26
18 283 ms 355 ms 297 ms ed-n5596up-fe-1-vl241.fe.core.pw [92.223.112.163]
19 301 ms 270 ms 276 ms ed-sl-b62.fe.core.pw [92.223.21.62]
 
Code:
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms 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 = 6ms, Maximum = 6ms, Average = 6ms
Code:
Tracing route to ed-sl-b62.fe.core.pw [92.223.21.62]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  ARCHER_D5 [192.168.0.1]
  2     *        *        *     Request timed out.
  3   120 ms   123 ms   123 ms  cpt-up1.ip.adsl.co.za [169.1.5.105]
  4   135 ms   138 ms   136 ms  cpt-up2.ip.adsl.co.za [169.1.5.106]
  5    10 ms     7 ms     7 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6     9 ms     8 ms     9 ms  41.164.52.40
  7     8 ms     9 ms     8 ms  ix-ae-7-0.tcore1.KLT-Cape-Town.as6453.net [41.206.164.53]
  8   157 ms   160 ms   157 ms  if-ae-5-2.tcore2.PV9-Lisbon.as6453.net [80.231.159.93]
  9   158 ms   157 ms   157 ms  if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
 10   152 ms   152 ms   156 ms  if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
 11   269 ms   276 ms   283 ms  if-ae-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
 12     *      157 ms   157 ms  if-ae-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
 13   263 ms   257 ms   263 ms  if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
 14   247 ms   244 ms   251 ms  be3040.ccr21.lon01.atlas.cogentco.com [130.117.15.177]
 15   158 ms   158 ms   160 ms  be2868.ccr41.lon13.atlas.cogentco.com [154.54.57.153]
 16   158 ms   158 ms   205 ms  be12194.ccr41.ams03.atlas.cogentco.com [154.54.56.94]
 17   288 ms   283 ms   345 ms  be2412.rcr21.b038092-0.ams03.atlas.cogentco.com [154.54.37.98]
 18   262 ms   272 ms   277 ms  149.11.65.26
 19   172 ms   185 ms   182 ms  ed-n5596up-fe-1-vl241.fe.core.pw [92.223.112.163]
 20   178 ms   172 ms   170 ms  ed-sl-b62.fe.core.pw [92.223.21.62]

Trace complete.

C:\WINDOWS\system32>

EDIT: 9:36pm
Discord is connected to your voice server on eu-west285 with an average ping of 925ms
 
Last edited:
From our side both accounts would route via the same PoP in the South, where our management services live for that region. So the only differentiating factor would be the exchange.

It's definitely something to look into. How many users having a poor experience are also in Durbanville? We know it's an area which has battled with congestion - at one point the exchange was upgrade 4 or 5 times in one year, to my knowledge.

Can't tell you why. I'm only conveying my test results. The fact that we both had different results might just shed some light on the varying results you get in the south.
Exchange is fine as usual. For the last week I've had 0 issues while running on Crystalweb. Also pinging bras is always 18ms.
 
Last edited:
So your friend in Brackenfell performed the same traceroutes as you during peak hours and had no latency issues on Afrihost?

I'm located in Panorama, Northern Suburbs and with my rudimentary knowledge of my PSTN routing - it's CPE -> remote ISAM -> Exchange in Voortrekker Road, Parow -> Central Office in Bellville - and I also suffer with the higher than normal latency during peak hours.

But the issue is not present on other ISP accounts, so i wouldn't seem to think anything of exchange related issues.. :confused:

Exactly my experience. I've got tons of Afrihost test data showing the issue, with bras always fine. Running on another ISP also fine.
 
Last edited:
Lol. So terrible, had to use my lte to sign up another isp account and finally my brother gave notice to afrihost.
Two more weeks =)
 
Everything about Afrihost is poor at the moment. Even the support on these forums is just terrible. Afrihost is but a mere shadow of what they used to be. Sad really. time to move on
 
the internet and browsing experience is not good this weekend looks like we are shaped to death or they simply ran out of ipc
 
Top
Sign up to the MyBroadband newsletter
X