Afrihost New Network Feedback

Bryn · Jan 2, 2016

Found the issue I had with the free capped account yesterday. It just so happened that I used Afrihost's DNS settings with it (used Google's with the WA account and left them in place), and I see now that the DNS addresses have changed since I last used Afrihost.

Icemanbrfc · Jan 2, 2016

Bryn said:
The new Afrihost network is just amazing, and I'm loving having the country's best customer portal back again. Streaming is 100% (tested Netflix 1080p, Twitch source quality, Youtube 1080p and BBC iPlayer HD), no issues with the few games I've tried and browsing is snappy in general.

The 200+200GB was indeed reflected in the Clientzone when I checked it last night.

Nice pal, glad you all good. I'm also having no issues, and streaming happily right now.

Vio · Jan 2, 2016

Afrihost network currently has a latency problem on this hop tracing to afrihost.co.za:
4 22 ms 20 ms 18 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 78 ms 85 ms 91 ms 41.164.52.40
6 104 ms 106 ms 113 ms mtnns-2.cinx.net.za [196.223.22.31]

This is @ 10pm on the 2nd.

Oh yes I forgot this is from CT.

ghostR · Jan 2, 2016

Vio said:
Afrihost network currently has a latency problem on this hop tracing to afrihost.co.za:
4 22 ms 20 ms 18 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 78 ms 85 ms 91 ms 41.164.52.40
6 104 ms 106 ms 113 ms mtnns-2.cinx.net.za [196.223.22.31]

This is @ 10pm on the 2nd.

That's an issue with the interconnect point connecting to MTN's network. So it's not a problem on Afrihost's side.

Vio · Jan 2, 2016

ghostR said:
That's an issue with the interconnect point connecting to MTN's network. So it's not a problem on Afrihost's side.

I'm seeing latency on their 3rd to 4th hop now:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 13 ms 12 ms 12 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
4 75 ms 74 ms 78 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
Third to fourth hop one thats been bottlenecking in peak hours since before christmas on and off.

Btw through all this bras.afrihost.com latency has been 11-12ms never increasing.

NewBiks · Jan 3, 2016

Hi everyone hope you all had a great festive season.

For the past 3 days my streaming quality has been sub par on both Twitch and Vessel.

Speedtest remained the same but throughput was bad, didn't record any tests but I could actively see the lack in performance.

Bryn · Jan 3, 2016

NewBiks said:
Hi everyone hope you all had a great festive season.

For the past 3 days my streaming quality has been sub par on both Twitch and Vessel.

Speedtest remained the same but throughput was bad, didn't record any tests but I could actively see the lack in performance.

Are you using Afrihost's DNS settings? I found performance increased across the board with them.

Slaught3r · Jan 3, 2016

Anyone else struggling with latency issues?

Vio · Jan 3, 2016

Slaught3r said:
Anyone else struggling with latency issues?

Yes I am seeing intermittent periods of 100ms+ latency on the hops coming off their 3rd and 4th hop, while at the same time seeing low latency to bras.afrihost.com (which I think is the first hop)

ghostR · Jan 3, 2016

Vio said:
Yes I am seeing intermittent periods of 100ms+ latency on the hops coming off their 3rd and 4th hop, while at the same time seeing low latency to bras.afrihost.com (which I think is the first hop)

What region are you in? If it was an afrihost issue I'm sure there would be a lot more complaints here.

DonaldMickey · Jan 3, 2016

Any issues with AH tonight? When I ping www.google.co.za the latency ranges from 12ms to 150+ms.
Download speed seems to be unaffected.

DonaldMickey · Jan 3, 2016

DonaldMickey said:
Any issues with AH tonight? When I ping www.google.co.za the latency ranges from 12ms to 150+ms.
Download speed seems to be unaffected.

Started about an hour ago.

Vio · Jan 3, 2016

ghostR said:
What region are you in? If it was an afrihost issue I'm sure there would be a lot more complaints here.

I'm in CT. And it most certainly is Afrihost, my other accounts do not manifest the issue.

Vio · Jan 3, 2016

DonaldMickey said:
Started about an hour ago.

Here is what I am seeing from my side to google.co.za:
Tracing route to www.google.co.za [173.194.45.55]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 12 ms 13 ms 12 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
4 87 ms 96 ms 95 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 282 ms 289 ms 334 ms 41.164.52.40
6 374 ms 295 ms 281 ms 172.18.1.162
7 364 ms 196 ms 200 ms 72.14.194.206
8 437 ms 397 ms 341 ms 216.239.54.57
9 428 ms 395 ms 443 ms 209.85.143.219
10 484 ms 502 ms 424 ms 209.85.248.20
11 472 ms 511 ms 530 ms 66.249.94.79
12 267 ms 267 ms 287 ms par03s12-in-f23.1e100.net [173.194.45.55]

Trace complete.

To Afrihost.com:
Tracing route to www.afrihost.com [41.181.185.18]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 37 ms 37 ms 37 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
4 133 ms 124 ms 123 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 120 ms 109 ms 106 ms 41.164.52.40
6 115 ms 112 ms 104 ms mtnns-2.cinx.net.za [196.223.22.31]
7 14 ms 14 ms 14 ms 196.44.0.75
8 36 ms 36 ms 43 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]
9 122 ms 96 ms 94 ms jh-cr-2.za--rb-cr-1.za-b.mtnns.net [196.44.31.171]
10 35 ms 35 ms 35 ms jh-dca-1.za--jh-cr-2.za-a.mtnns.net [41.181.180.8]
11 229 ms 103 ms 59 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]
to bras.afrihost.com:
Tracing route to bras.afrihost.com [155.239.255.250]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 10 ms 11 ms 10 ms 155.239.255.250

Trace complete.

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=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms 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 = 12ms, Average = 11ms

I would venture to say their link between cpt-rx2.ip.adsl.co.za and cpt-net1.ip.adsl.co.za is over capacity or broken; connecting to 41.164.52.40 is also suspect. Notice everything prior to cpt-rx2.ip.adsl.co.za is sunshine and roses.

I pointed this out to them on the 20th~23rd of December, but its the same **** every few days: in peak times those links bottleneck and latency shoots up.

Johnatan56 · Jan 3, 2016

Vio said:

Here is what I am seeing from my side to google.co.za:

Code:

Tracing route to [url]www.google.co.za[/url] [173.194.45.55]
over a maximum of 30 hops:

[COLOR="#00FF00"]  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3    12 ms    13 ms    12 ms[/COLOR]  [COLOR="#FF0000"]cpt-rx2.ip.adsl.co.za [169.1.5.82]
  4    87 ms    96 ms    95 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  5   282 ms   289 ms   334 ms  41.164.52.40[/COLOR]
  6   374 ms   295 ms   281 ms  172.18.1.162
  7   364 ms   196 ms   200 ms  72.14.194.206
  8   437 ms   397 ms   341 ms  216.239.54.57
  9   428 ms   395 ms   443 ms  209.85.143.219
 10   484 ms   502 ms   424 ms  209.85.248.20
 11   472 ms   511 ms   530 ms  66.249.94.79
 12   267 ms   267 ms   287 ms  par03s12-in-f23.1e100.net [173.194.45.55]

Trace complete.

To Afrihost.com:
Tracing route to [url]www.afrihost.com[/url] [41.181.185.18]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3    37 ms    37 ms    37 ms  [COLOR="#FF0000"]cpt-rx2.ip.adsl.co.za [169.1.5.82]
  4   133 ms   124 ms   123 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  5   120 ms   109 ms   106 ms  41.164.52.40[/COLOR]
  6   115 ms   112 ms   104 ms  mtnns-2.cinx.net.za [196.223.22.31]
  7    14 ms    14 ms    14 ms  196.44.0.75
  8    36 ms    36 ms    43 ms  rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]
  9   122 ms    96 ms    94 ms  jh-cr-2.za--rb-cr-1.za-b.mtnns.net [196.44.31.171]
 10    35 ms    35 ms    35 ms  jh-dca-1.za--jh-cr-2.za-a.mtnns.net [41.181.180.8]
 11   229 ms   103 ms    59 ms  18.185.181.41.in-addr.aserv.co.za [41.181.185.18]
to bras.afrihost.com:
Tracing route to bras.afrihost.com [155.239.255.250]
over a maximum of 30 hops:

[COLOR="#00FF00"]  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    10 ms    11 ms    10 ms  155.239.255.250[/COLOR]

Trace complete.

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=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms 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 = 12ms, Average = 11ms

I would venture to say their link between cpt-rx2.ip.adsl.co.za and cpt-net1.ip.adsl.co.za is over capacity or broken; connecting to 41.164.52.40 is also suspect. Notice everything prior to cpt-rx2.ip.adsl.co.za is sunshine and roses.

I pointed this out to them on the 20th~23rd of December, but its the same **** every few days: in peak times those links bottleneck and latency shoots up.

Code:

Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\WINDOWS\System32>tracert 173.194.45.55

Tracing route to par03s12-in-f23.1e100.net [173.194.45.55]
over a maximum of 30 hops:

  1     2 ms     1 ms     2 ms  home.gateway.pace.net [192.168.1.1]
  2     *        *        *     Request timed out.
  3    26 ms    24 ms    26 ms  cpt-up1.ip.adsl.co.za [169.1.5.105]
  4    62 ms    62 ms    59 ms  cpt-up2.ip.adsl.co.za [169.1.5.106]
  5    27 ms    25 ms    26 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6    26 ms    25 ms    25 ms  41.164.52.40
  7    83 ms    83 ms    74 ms  172.18.1.162
  8    48 ms    47 ms    48 ms  72.14.194.206
  9   208 ms   206 ms   208 ms  216.239.54.57
 10   238 ms   217 ms   218 ms  209.85.143.219
 11   221 ms   217 ms   220 ms  209.85.245.71
 12   217 ms   226 ms   218 ms  66.249.94.79
 13   471 ms   323 ms   312 ms  par03s12-in-f23.1e100.net [173.194.45.55]

Trace complete.

C:\WINDOWS\System32>tracert afrihost.com

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

  1     1 ms     2 ms     8 ms  home.gateway.pace.net [192.168.1.1]
  2     *        *        *     Request timed out.
  3    25 ms    26 ms    24 ms  cpt-up1.ip.adsl.co.za [169.1.5.105]
  4    66 ms    69 ms    60 ms  cpt-up2.ip.adsl.co.za [169.1.5.106]
  5    26 ms    26 ms    27 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6    25 ms    25 ms    28 ms  41.164.52.40
  7    28 ms    26 ms    26 ms  mtnns-2.cinx.net.za [196.223.22.31]
  8    28 ms    27 ms    27 ms  rb-cr-1.za.nl-ha-2.za-a.mtnns.net [196.44.0.120]
  9    27 ms    30 ms    29 ms  tb-cr-2.za--ct-cr-1.za-a.mtnns.net [196.44.31.107]
 10    56 ms    68 ms    52 ms  jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66] 
 11    50 ms    53 ms    48 ms  jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
 12    73 ms    71 ms    56 ms  18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

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=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms 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

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 = 23ms

I am copying over the network, downloading a torrent and playing an MMORPG, so all my tracerts are higher as you can see by the first hop, so all good my side.

(also could you in future use [ code] [/ code] (remove the spaces) for tracerts/pings as it saves a lot of space on a page and makes it easier to look at (überischt zu behalten, my english is currently failing me, lol))

NewBiks · Jan 4, 2016

Bryn said:
Are you using Afrihost's DNS settings? I found performance increased across the board with them.

I have been using their DNS settings, not sure if anything has changed on their end.
Here are the settings

Primary DNS: 169.1.1.1
Secondary DNS: 169.1.1.2

Slaught3r · Jan 4, 2016

I was playing some COD last night and was spiking badly. I was checking out everyone elses pings and they were erratic at best. Between 30 - 300. When asked who there was using Afrihost - everyone with an erratic ping answered in the affirmative. There was an issue, for sure. I didn't check this morning - had to get to work early, so not sure if it is persisting.

Dianysis · Jan 4, 2016

Slaught3r said:
I was playing some COD last night and was spiking badly. I was checking out everyone elses pings and they were erratic at best. Between 30 - 300. When asked who there was using Afrihost - everyone with an erratic ping answered in the affirmative. There was an issue, for sure. I didn't check this morning - had to get to work early, so not sure if it is persisting.

This. That was what was happening with my ping. Spiking left right and centre.

Slaught3r · Jan 4, 2016

No Afripeeps around?

Icemanbrfc · Jan 4, 2016

My line is dead. My internet light on my modem is not on. So not an Afrihost issue, possibly Telkom again. Urgh

Join the MyBroadband community

Get started

Afrihost New Network Feedback

Doubleplusgood

Honorary Master

Expert Member

Executive Member

Expert Member

Well-Known Member

Doubleplusgood

Expert Member

Expert Member

Executive Member

Well-Known Member

Well-Known Member

Expert Member

Expert Member

Honorary Master

Well-Known Member

Expert Member

Expert Member

Expert Member

Honorary Master