Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
Code: 
Pinging vienna.at [194.183.128.94] with 32 bytes of data:
Reply from 194.183.128.94: bytes=32 time=334ms TTL=44
Reply from 194.183.128.94: bytes=32 time=332ms TTL=44
Reply from 194.183.128.94: bytes=32 time=308ms TTL=44
Reply from 194.183.128.94: bytes=32 time=319ms TTL=44
Reply from 194.183.128.94: bytes=32 time=331ms TTL=44
Reply from 194.183.128.94: bytes=32 time=338ms TTL=44
Reply from 194.183.128.94: bytes=32 time=301ms TTL=44
Reply from 194.183.128.94: bytes=32 time=334ms TTL=44
Reply from 194.183.128.94: bytes=32 time=339ms TTL=44
Request timed out.
Reply from 194.183.128.94: bytes=32 time=297ms TTL=44
Reply from 194.183.128.94: bytes=32 time=337ms TTL=44
Reply from 194.183.128.94: bytes=32 time=313ms TTL=44
Reply from 194.183.128.94: bytes=32 time=339ms TTL=44
Reply from 194.183.128.94: bytes=32 time=304ms TTL=44
Reply from 194.183.128.94: bytes=32 time=330ms TTL=44
Reply from 194.183.128.94: bytes=32 time=327ms TTL=44
Reply from 194.183.128.94: bytes=32 time=322ms TTL=44
Reply from 194.183.128.94: bytes=32 time=319ms TTL=44
Reply from 194.183.128.94: bytes=32 time=329ms TTL=44
Reply from 194.183.128.94: bytes=32 time=321ms TTL=44
Reply from 194.183.128.94: bytes=32 time=325ms TTL=44
Reply from 194.183.128.94: bytes=32 time=338ms TTL=44
Reply from 194.183.128.94: bytes=32 time=338ms TTL=44
Reply from 194.183.128.94: bytes=32 time=335ms TTL=44
Reply from 194.183.128.94: bytes=32 time=334ms TTL=44
Reply from 194.183.128.94: bytes=32 time=336ms TTL=44

Ping statistics for 194.183.128.94:
    Packets: Sent = 27, Received = 26, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
    Minimum = 297ms, Maximum = 339ms, Average = 326ms



---------------------------------------------------------------------------------------------------------------------------------------


Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=22ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=24ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=22ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=22ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=22ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=22ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=22ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=20ms TTL=62
Reply from 155.239.255.250: bytes=32 time=20ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=26ms TTL=62
Reply from 155.239.255.250: bytes=32 time=24ms TTL=62
Reply from 155.239.255.250: bytes=32 time=24ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=24ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=22ms TTL=62
Reply from 155.239.255.250: bytes=32 time=22ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=22ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=22ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=22ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=20ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=22ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=20ms TTL=62
Reply from 155.239.255.250: bytes=32 time=22ms TTL=62
Reply from 155.239.255.250: bytes=32 time=22ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=22ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=22ms TTL=62

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


---------------------------------------------------------------------------------------------------------------------------------------

Tracing route to vienna.at [194.183.128.94]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  ARCHER_D5 [192.168.0.1]
  2    <1 ms    <1 ms    <1 ms  home.gateway.pace.net [192.168.1.1]
  3     *        *        *     Request timed out.
  4    23 ms    28 ms    22 ms  cpt-up1.ip.adsl.co.za [169.1.5.105]
  5   100 ms   101 ms   102 ms  cpt-up2.ip.adsl.co.za [169.1.5.106]
  6   108 ms     *      113 ms  169-1-5-132.ip.afrihost.co.za [169.1.5.132]
  7    96 ms    99 ms   100 ms  41.164.52.42
  8   150 ms   145 ms   141 ms  ix-ae-7-0.tcore2.KLT-Cape-Town.as6453.net [41.206.165.25]
  9   306 ms   298 ms   286 ms  if-ae-2-2.tcore1.KLT-Cape-Town.as6453.net [41.206.164.253]
 10   310 ms   304 ms   347 ms  if-ae-5-90.tcore2.PV9-Lisbon.as6453.net [80.231.159.109]
 11   302 ms     *      344 ms  if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
 12   294 ms   264 ms   295 ms  if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
 13   296 ms     *        *     if-ae-19-2.tcore2.L78-London.as6453.net [80.231.138.22]
 14   294 ms   309 ms   320 ms  if-ae-15-2.tcore2.LDN-London.as6453.net [80.231.131.118]
 15   311 ms   328 ms   350 ms  ldn-b5-link.telia.net [62.115.9.173]
 16   344 ms   294 ms   339 ms  ldn-bb2-link.telia.net [213.155.136.76]
 17   307 ms   296 ms   304 ms  prs-bb2-link.telia.net [80.91.246.177]
 18   309 ms   312 ms   314 ms  zch-b2-link.telia.net [62.115.135.127]
 19   325 ms   312 ms     *     russmedia-ic-317231-zch-b2.c.telia.net [62.115.146.227]
 20   324 ms   326 ms   329 ms  194-208-001-038.tele.net [194.208.1.38]
 21     *      308 ms   295 ms  gi0-2-74-cr6-swz1.net.tele.net [194.183.142.135]
 22   302 ms   327 ms   322 ms  service.tele.net [194.183.128.94]

Trace complete.

5 100 ms 101 ms 102 ms cpt-up2.ip.adsl.co.za [169.1.5.106]

100ms for a local hop. WTF afrihost.

Hi guys, I have sent all your test results over to our NOC Team and they are currently looking into - and monitoring traffic in the South. We're not seeing any obvious causes for high latency at the moment, but our Team are busy investigating. I'll reach out to you individually via PM if we need any further tests and update the thread with any general announcements once I hear back from the NOC Team. Thanks for testing.
Click to expand...

Glad to see that you guys are working on it. /sarcasm

Just slightly annoyed atm. Only slightly.
 
Last edited:
And afrihost status no problem
cd7d1952ea6ea5d30dd8ed2a402ea0a3.png
 
Vio said:
There's something wrong with Afrihost's IPC. Probably congested again etc. as per normal...

Afrihost:
tracert www.afrihost.com

Tracing route to www.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 31 ms 31 ms 32 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
4 40 ms 39 ms 39 ms 169-1-5-132.ip.afrihost.co.za [169.1.5.132]
5 34 ms 33 ms 35 ms 41.164.52.42
6 66 ms 64 ms 65 ms 172.18.1.162
7 69 ms 69 ms 65 ms cloudflare.ixp.joburg [196.46.25.198]
8 63 ms 61 ms 60 ms 104.20.31.244

Web Africa comparison:
tracert www.afrihost.com

Tracing route to www.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 13 ms 13 ms 12 ms cdsl1-ctn-vl2376-ipc.ip.isnet.net [196.38.72.206]
4 12 ms 12 ms 13 ms cdsl1-ctn-vl2376.ip.isnet.net [196.38.72.205]
5 11 ms 12 ms 12 ms 196.35.115.128
6 13 ms 12 ms 12 ms mi-za-cpt-p7-te0-7-0-0.ip.isnet.net [168.209.2.12]
7 64 ms 63 ms 60 ms 168.209.0.177
8 60 ms 67 ms 65 ms 196.26.0.130
9 36 ms 37 ms 37 ms cloudflare.ixp.joburg [196.46.25.198]
10 36 ms 36 ms 36 ms 104.20.31.244

Trace complete.
Click to expand...

And this is what it looks like when Afrihost works correctly:
>tracert www.afrihost.com

Tracing route to www.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 13 ms 13 ms 11 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
4 11 ms 12 ms 14 ms 169-1-5-132.ip.afrihost.co.za [169.1.5.132]
5 12 ms 12 ms 13 ms 41.164.52.42
6 33 ms 33 ms 33 ms 172.18.1.162
7 34 ms 33 ms 33 ms cloudflare.ixp.joburg [196.46.25.198]
8 34 ms 34 ms 34 ms 104.20.31.244

Trace complete.
 
Last edited:
Vio said:
And this is what it looks like when Afrihost works correctly:
>tracert www.afrihost.com

Tracing route to www.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 13 ms 13 ms 11 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
4 11 ms 12 ms 14 ms 169-1-5-132.ip.afrihost.co.za [169.1.5.132]
5 12 ms 12 ms 13 ms 41.164.52.42
6 33 ms 33 ms 33 ms 172.18.1.162
7 34 ms 33 ms 33 ms cloudflare.ixp.joburg [196.46.25.198]
8 34 ms 34 ms 34 ms 104.20.31.244

Trace complete.
Click to expand...

Thanks for posting the two traceroutes! It helps a lot to have those for the Team.
 
AfriGenie said:
We're definitely not shaping our Capped accounts. Which services or sites have been problematic for you?
Click to expand...

So before the promo started, NNTP traffic ran at 90-100% my line speed. Since the promo, if its not in the "night time data" the traffic grinds nearly to a halt at 2-4kb/s. Explain that one then.
 
Zenthrax said:
So before the promo started, NNTP traffic ran at 90-100% my line speed. Since the promo, if its not in the "night time data" the traffic grinds nearly to a halt at 2-4kb/s. Explain that one then.
Click to expand...

If you are experiencing that, we'll need to look into this. If it happens again, would you be able to run a speedtest, and post a screenshot of your NNTP Client's current download speed?
 
LBXAC20 said:
vox was pinging 160 last night the same time afri was at 300+...
Click to expand...
But again, if you look at other users who use Vox, they were having latency issues. Its a tough one for any isp, when only a select few are having issues, because then you cannot change the status to there being a problem. Isolated issues need to be individually addressed.

Maybe Afrihost should remove the status bit on their site, because its confusing people it seems. As an example, if lets say every user in the cape is affected, then its easy to change from green to red. However, if only a few are having an issue, then to change the status from green to red, will just set off a case where people question that status..
 
Icemanbrfc said:
But again, if you look at other users who use Vox, they were having latency issues.
Click to expand...

I can only speak about my own experience. Last night and the night before that afri was at 300ms+ while vox was around 160.
 
LBXAC20 said:
I can only speak about my own experience. Last night and the night before that afri was at 300ms+ while vox was around 160.
Click to expand...
100% no issues with that. I was just pointing out, that it seems like a trend in all the isp threads, which makes it difficult for an isp to pinpoint an issue. The only way is to individually address it. Thus, people continue to point to Afrihost status page showing green. You cant change it to red, if an entire region are not affected, or at least a significant number, or its a serious break somewhere. :)
 
AfriGenie said:
Ideally you shouldn't be having any latency issues. :(

To which site or service were you seeing that latency?
Click to expand...
Look at my Post last night and the night befor then you see the Problem
International trace was going up to 300 ms normaly 190
Local to youtube was 100 ms normaly 60 ms or lower
 
Last edited:
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X