Afrihost New Network Feedback

Status
Not open for further replies.
Back on PC. Lets see if I can finish this post (attempt 3).

Its up and down. Works for a bit (sluggishly) then goes dead. When it's dead I can't ping DNS names i.e. afrihost.co.za, and can't ping IP address directly.

Throughput is at 15%, although latency seems fine, i.e. I am still getting 20ms, but with vastly reduced throughput.
 
I find the issues on tracert not 100% reproducable

Code:
Tracing route to e10088.dspb.akamaiedge.net [95.100.163.11]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     9 ms     6 ms     6 ms  169-0-54-1.ip.afrihost.co.za [169.0.54.1] 
  3  1653 ms  1913 ms  2917 ms  cpt-tx2.ip.adsl.co.za [169.1.5.81] 
  4     8 ms     7 ms     7 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  5     7 ms     7 ms     6 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  6     8 ms     7 ms     7 ms  41.164.52.40 
  7     8 ms    10 ms     7 ms  if-7-0.tcore1.KLT-Cape-Town.as6453.net [41.206.164.53] 
  8   130 ms   130 ms   131 ms  Pos-channel6.core2.PV9-Lisbon.as6453.net [41.206.164.6] 
  9   163 ms   163 ms   166 ms  if-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net [80.231.158.1] 
 10   168 ms   174 ms   177 ms  if-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30] 
 11   165 ms   165 ms   166 ms  if-19-2.tcore2.L78-London.as6453.net [80.231.138.22] 
 12   174 ms   175 ms   176 ms  if-8-2.tcore2.AV2-Amsterdam.as6453.net [80.231.131.6] 
 13   158 ms   159 ms   158 ms  if-2-2.tcore1.AV2-Amsterdam.as6453.net [195.219.194.5] 
 14   181 ms   180 ms   178 ms  195.219.194.106 
 15   171 ms   168 ms   169 ms  a95-100-163-11.deploy.akamaitechnologies.com [95.100.163.11] 

Trace complete.

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

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     8 ms     5 ms     6 ms  169-0-54-1.ip.afrihost.co.za [169.0.54.1] 
  3   401 ms   997 ms  1197 ms  cpt-tx2.ip.adsl.co.za [169.1.5.81] 
  4     7 ms     7 ms    11 ms  cpt-rx1.ip.adsl.co.za [169.1.5.94] 
  5     8 ms     8 ms     7 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  6     7 ms     8 ms     8 ms  41.164.52.40 
  7     8 ms     7 ms     8 ms  172.18.32.33 
  8     8 ms     8 ms     9 ms  mtnns-2.cinx.net.za [196.223.22.31] 
  9     9 ms    10 ms     9 ms  rb-cr-1.za.nl-ha-2.za-a.mtnns.net [196.44.0.120] 
 10    10 ms     9 ms     9 ms  tb-cr-2.za--ct-cr-1.za-a.mtnns.net [196.44.31.107] 
 11    32 ms    31 ms    31 ms  pe-cr-2.za--el-mse-1.za.mtnns.net [196.44.31.66] 
 12    73 ms    71 ms    31 ms  jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217] 
 13    31 ms    31 ms    31 ms  18.185.181.41.in-addr.aserv.co.za [41.181.185.18] 

Trace complete.
 
Not the case here. Some teething issues are to be expected, we're still running through some improvements.
We're working on sorting this out.

This is only affecting the South btw.

Always the South its about time users in the South get some compensation for these continual issues
 
Back on PC. Lets see if I can finish this post (attempt 3).

Its up and down. Works for a bit (sluggishly) then goes dead. When it's dead I can't ping DNS names i.e. afrihost.co.za, and can't ping IP address directly.

Throughput is at 15%, although latency seems fine, i.e. I am still getting 20ms, but with vastly reduced throughput.

Sorry about this :(
We're working on a fix for this now.
 
I find the issues on tracert not 100% reproducable

Code:
Tracing route to e10088.dspb.akamaiedge.net [95.100.163.11]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     9 ms     6 ms     6 ms  169-0-54-1.ip.afrihost.co.za [169.0.54.1] 
  3  1653 ms  1913 ms  2917 ms  cpt-tx2.ip.adsl.co.za [169.1.5.81] 
  4     8 ms     7 ms     7 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  5     7 ms     7 ms     6 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  6     8 ms     7 ms     7 ms  41.164.52.40 
  7     8 ms    10 ms     7 ms  if-7-0.tcore1.KLT-Cape-Town.as6453.net [41.206.164.53] 
  8   130 ms   130 ms   131 ms  Pos-channel6.core2.PV9-Lisbon.as6453.net [41.206.164.6] 
  9   163 ms   163 ms   166 ms  if-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net [80.231.158.1] 
 10   168 ms   174 ms   177 ms  if-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30] 
 11   165 ms   165 ms   166 ms  if-19-2.tcore2.L78-London.as6453.net [80.231.138.22] 
 12   174 ms   175 ms   176 ms  if-8-2.tcore2.AV2-Amsterdam.as6453.net [80.231.131.6] 
 13   158 ms   159 ms   158 ms  if-2-2.tcore1.AV2-Amsterdam.as6453.net [195.219.194.5] 
 14   181 ms   180 ms   178 ms  195.219.194.106 
 15   171 ms   168 ms   169 ms  a95-100-163-11.deploy.akamaitechnologies.com [95.100.163.11] 

Trace complete.

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

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     8 ms     5 ms     6 ms  169-0-54-1.ip.afrihost.co.za [169.0.54.1] 
  3   401 ms   997 ms  1197 ms  cpt-tx2.ip.adsl.co.za [169.1.5.81] 
  4     7 ms     7 ms    11 ms  cpt-rx1.ip.adsl.co.za [169.1.5.94] 
  5     8 ms     8 ms     7 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  6     7 ms     8 ms     8 ms  41.164.52.40 
  7     8 ms     7 ms     8 ms  172.18.32.33 
  8     8 ms     8 ms     9 ms  mtnns-2.cinx.net.za [196.223.22.31] 
  9     9 ms    10 ms     9 ms  rb-cr-1.za.nl-ha-2.za-a.mtnns.net [196.44.0.120] 
 10    10 ms     9 ms     9 ms  tb-cr-2.za--ct-cr-1.za-a.mtnns.net [196.44.31.107] 
 11    32 ms    31 ms    31 ms  pe-cr-2.za--el-mse-1.za.mtnns.net [196.44.31.66] 
 12    73 ms    71 ms    31 ms  jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217] 
 13    31 ms    31 ms    31 ms  18.185.181.41.in-addr.aserv.co.za [41.181.185.18] 

Trace complete.

Very interesting results here.
What do you see when you ping 169.1.5.81?
 
hi there i see that the afrihost network seem to be blocking apple updates.

We don't block any services/ protocols from our end.
There do seem to be a few niggles this evening though, starting to see some good results from testing now though.

Mind trying again in 5 mins?
 
Very interesting results here.
What do you see when you ping 169.1.5.81?

Code:
C:\Users\RiaanS>ping 169.1.5.81 -t

Pinging 169.1.5.81 with 32 bytes of data:
Reply from 169.1.5.81: bytes=32 time=7ms TTL=58
Reply from 169.1.5.81: bytes=32 time=8ms TTL=58
Reply from 169.1.5.81: bytes=32 time=7ms TTL=58
Reply from 169.1.5.81: bytes=32 time=8ms TTL=58
Reply from 169.1.5.81: bytes=32 time=7ms TTL=58
Reply from 169.1.5.81: bytes=32 time=7ms TTL=58
Reply from 169.1.5.81: bytes=32 time=8ms TTL=58
Reply from 169.1.5.81: bytes=32 time=7ms TTL=58

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

As I said though it's not all the time. My tracerts are automated and not every one shows the latency I posted before.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X