Afrihost POC Network - Afrigreen Feedback

standerr · Sep 16, 2015

standerr said:
Don't know if it's just me, but seems like something went boom.
Latency has suddenly spiked significantly since 16h00

City: Cape Town

Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.1.0.254
2 1301 ms 1241 ms 1436 ms 169-0-54-1-access.afrihost.co.za [169.0.54.1]
3 1103 ms 193 ms 29 ms 41.170.79.230
4 585 ms 689 ms 552 ms 41.170.79.236
5 901 ms 865 ms 892 ms mweb.jb1.napafrica.net [196.46.25.145]
6 977 ms 1056 ms 1039 ms te0-0-0-3.vic-p-2.optinet.net [197.80.7.34]
7 1133 ms 1095 ms 1131 ms te0-0-0-0.cpt-p-1.optinet.net [197.84.4.34]
8 1356 ms 1207 ms 1283 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
9 1433 ms 1406 ms 1623 ms 196.28.178.66
10 1639 ms 1415 ms 1569 ms cte-core-sw2.vwol.net [196.41.144.35]
11 1515 ms 1474 ms 1549 ms www.mweb.co.za [196.2.63.110]

Trace complete.

http://netgauge.ookla.com/share/273180451.png

And before everybody jumps on the Exchange wagon. I know I know second hop, bla bla.

AfriGuy · Sep 16, 2015

standerr said:
Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.1.0.254
2 1301 ms 1241 ms 1436 ms 169-0-54-1-access.afrihost.co.za [169.0.54.1]
3 1103 ms 193 ms 29 ms 41.170.79.230
4 585 ms 689 ms 552 ms 41.170.79.236
5 901 ms 865 ms 892 ms mweb.jb1.napafrica.net [196.46.25.145]
6 977 ms 1056 ms 1039 ms te0-0-0-3.vic-p-2.optinet.net [197.80.7.34]
7 1133 ms 1095 ms 1131 ms te0-0-0-0.cpt-p-1.optinet.net [197.84.4.34]
8 1356 ms 1207 ms 1283 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
9 1433 ms 1406 ms 1623 ms 196.28.178.66
10 1639 ms 1415 ms 1569 ms cte-core-sw2.vwol.net [196.41.144.35]
11 1515 ms 1474 ms 1549 ms www.mweb.co.za [196.2.63.110]

Trace complete.

http://netgauge.ookla.com/share/273180451.png

And before everybody jumps on the Exchange wagon. I know I know second hop, bla bla.

Woah, this looks like a severe case of exchange congestion

Not seeing anywhere near this amount of latency on my tests or monitoring.
Could you test with your regular Afrihost to confirm?

caroper · Sep 16, 2015

Also try and Ping 155.239.255.250, it will test the local latency in the exchange.

LaraC · Sep 16, 2015

Zertop's "Is it my Line" Results
Date/Time: Wed Sep 16 16:53:28 CAT 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 6ms.
Your maximum ping was 7ms.

Looking at your average ping, your line seems to be running perfectly.
It seems that your maximum ping is also good. If there are any issues, they most probably lie with your ISP

Detailed Report:

Code:

Pinging 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
Reply from 155.239.255.250: bytes=32 time=7ms 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
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=7ms 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
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
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
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms 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
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 = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 6ms, Maximum = 7ms, Average = 6ms

LaraC · Sep 16, 2015

No problems with my connectivity.

DonaldMickey · Sep 16, 2015

LaraC said:

Zertop's "Is it my Line" Results
Date/Time: Wed Sep 16 16:53:28 CAT 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 6ms.
Your maximum ping was 7ms.

Looking at your average ping, your line seems to be running perfectly.
It seems that your maximum ping is also good. If there are any issues, they most probably lie with your ISP

Detailed Report:

Code:

Pinging 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
Reply from 155.239.255.250: bytes=32 time=7ms 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
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=7ms 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
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
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
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms 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
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 = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 6ms, Maximum = 7ms, Average = 6ms

LaraC said:
No problems with my connectivity.

View attachment 297472

Brag brag brag......

AfriGuy · Sep 16, 2015

LaraC said:
No problems with my connectivity.

View attachment 297472

Looking good

standerr · Sep 16, 2015

AfriGuy said:
Woah, this looks like a severe case of exchange congestion Not seeing anywhere near this amount of latency on my tests or monitoring.
Could you test with your regular Afrihost to confirm?

Like I said my exchange has been very stable for a while now. I've written some software to track this over time.

Current averages for the day on Afrigreen & MTN

Running fine on MTN now

LaraC · Sep 16, 2015

DonaldMickey said:
Brag brag brag......

If you've got it flaunt it...

Dan C · Sep 16, 2015

standerr said:
Like I said my exchange has been very stable for a while now. I've written some software to track this over time.

Current averages for the day on Afrigreen & MTN
View attachment 297474

Running fine on MTN now

Definately a problem, my exchange is about 30% used.

Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 416 ms 376 ms 390 ms 169-0-29-1-access.afrihost.co.za [169.0.29.1]
3 444 ms 408 ms 340 ms 41.170.79.230
4 460 ms 466 ms 453 ms 41.170.79.236
5 365 ms 441 ms 376 ms mweb.jb1.napafrica.net [196.46.25.145]
6 305 ms 332 ms 410 ms te0-0-0-3.vic-p-2.optinet.net [197.80.7.34]
7 477 ms 457 ms 376 ms te0-0-0-0.cpt-p-1.optinet.net [197.84.4.34]
8 446 ms 468 ms 485 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
9 326 ms 344 ms 348 ms 196.28.178.66
10 402 ms 382 ms 408 ms cte-core-sw2.vwol.net [196.41.144.35]
11 487 ms 466 ms 431 ms www.mweb.co.za [196.2.63.110]

Trace complete.

EDIT : My telkom account

Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 8 ms 8 ms eel-ip-bb-1.south.dsl.telkomsa.net [105.224.120.1]
3 46 ms 45 ms 49 ms ipc-3-up.south.dsl.telkomsa.net [105.226.0.246]

4 78 ms 78 ms 80 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13]

5 31 ms 29 ms 30 ms blv-pr-02-be200-vl1.net.telkomsa.net [105.226.0.54]
6 93 ms 91 ms 93 ms ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
7 96 ms 96 ms 99 ms 196.10.140.15
8 77 ms 75 ms 70 ms bu-ether1.cpt-p-1.optinet.net [197.84.7.33]
9 31 ms 31 ms 30 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
10 * 43 ms 40 ms 196.28.178.66
11 31 ms 30 ms 31 ms cte-core-sw2.vwol.net [196.41.144.35]
12 38 ms 38 ms 38 ms www.mweb.co.za [196.2.63.110]

Trace complete.

LaraC · Sep 16, 2015

Dan C said:
Definately a problem, my exchange is about 30% used.

Did the same test. Mine routes differently than yours.

Code:

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

C:\Users\Lara>tracert mweb.co.za

Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    41 ms    40 ms    40 ms  ipc-tx-a-access.afrihost.co.za [169.1.1.249]
  4    45 ms    44 ms    45 ms  ipc-rx-a-access.afrihost.co.za [169.1.1.250]
  5    40 ms    40 ms    39 ms  41.170.79.236
  6    42 ms    41 ms    41 ms  mweb.jb1.napafrica.net [196.46.25.145]
  7    64 ms    65 ms    63 ms  te0-7-0-3.vic-p-2.optinet.net [197.80.7.98]
  8    60 ms    64 ms    60 ms  te0-0-0-0.cpt-p-1.optinet.net [197.84.4.34]
  9    61 ms    61 ms    61 ms  vl11.cpt-hscore-1.optinet.net [197.84.5.238]
 10    65 ms    65 ms    65 ms  196.28.178.66
 11    65 ms    64 ms    65 ms  cte-core-sw2.vwol.net [196.41.144.35]
 12    63 ms    60 ms    61 ms  www.mweb.co.za [196.2.63.110]

Trace complete.

Luke7777 · Sep 16, 2015

My route looks similar to yours Dan
Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway.home.gateway [192.168.1.254]
2 8 ms 8 ms 8 ms 169-0-53-1-access.afrihost.co.za [169.0.53.1]
3 11 ms 11 ms 11 ms ipc-rx-b-access.afrihost.co.za [169.1.1.238]
4 11 ms 10 ms 11 ms 41.170.79.236
5 13 ms 13 ms 16 ms mweb.jb1.napafrica.net [196.46.25.145]
6 33 ms 32 ms 31 ms te0-7-0-3.vic-p-1.optinet.net [197.80.7.1]
7 30 ms 32 ms 31 ms te0-0-0-0.cpt-p-2.optinet.net [197.84.4.46]
8 30 ms 30 ms 30 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
9 29 ms 29 ms 29 ms 196.28.178.66
10 29 ms 28 ms 29 ms cte-core-sw2.vwol.net [196.41.144.35]
11 29 ms 30 ms 29 ms www.mweb.co.za [196.2.63.110]

However , this looks a bit worse :

Zertop's "Is it my Line" Results
Date/Time: Wed Sep 16 17:55:33 CAT 2015

Basic Report:

Your packet loss was 20%.
Your average ping was 848ms.
Your maximum ping was 3078ms.

You seem to have some packet loss. This indicates an issue on the line.

Detailed Report:

Code:

Pinging 169.0.53.1 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 169.0.53.1: bytes=32 time=1615ms TTL=254
Reply from 169.0.53.1: bytes=32 time=153ms TTL=254
Reply from 169.0.53.1: bytes=32 time=1297ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 169.0.53.1: bytes=32 time=11ms TTL=254
Reply from 169.0.53.1: bytes=32 time=11ms TTL=254
Reply from 169.0.53.1: bytes=32 time=1434ms TTL=254
Reply from 169.0.53.1: bytes=32 time=1863ms TTL=254
Reply from 169.0.53.1: bytes=32 time=1292ms TTL=254
Reply from 169.0.53.1: bytes=32 time=931ms TTL=254
Reply from 169.0.53.1: bytes=32 time=224ms TTL=254
Reply from 169.0.53.1: bytes=32 time=10ms TTL=254
Reply from 169.0.53.1: bytes=32 time=3078ms TTL=254
Reply from 169.0.53.1: bytes=32 time=196ms TTL=254
Reply from 169.0.53.1: bytes=32 time=10ms TTL=254
Reply from 169.0.53.1: bytes=32 time=1990ms TTL=254
Reply from 169.0.53.1: bytes=32 time=244ms TTL=254
Reply from 169.0.53.1: bytes=32 time=493ms TTL=254
Reply from 169.0.53.1: bytes=32 time=1503ms TTL=254
Reply from 169.0.53.1: bytes=32 time=260ms TTL=254
Reply from 169.0.53.1: bytes=32 time=10ms TTL=254
Reply from 169.0.53.1: bytes=32 time=11ms TTL=254
Reply from 169.0.53.1: bytes=32 time=887ms TTL=254
Reply from 169.0.53.1: bytes=32 time=60ms TTL=254
Reply from 169.0.53.1: bytes=32 time=2776ms TTL=254

Ping statistics for 169.0.53.1:
    Packets: Sent = 30, Received = 24, Lost = 6 (20% loss),
Approximate round trip times in milli-seconds:
    Minimum = 10ms, Maximum = 3078ms, Average = 848ms

AfriGuy · Sep 16, 2015

standerr said:
Like I said my exchange has been very stable for a while now. I've written some software to track this over time.

Current averages for the day on Afrigreen & MTN
View attachment 297474

Running fine on MTN now

If your exchange is reporting that amount of latency that's where the issues will come in. Even on the MTN IPC the latency is still way too high.

Dan C · Sep 16, 2015

AfriGuy said:
If your exchange is reporting that amount of latency that's where the issues will come in. Even on the MTN IPC the latency is still way too high.

Why is mine so high on the 2nd hop ?

standerr · Sep 16, 2015

AfriGuy said:
If your exchange is reporting that amount of latency that's where the issues will come in. Even on the MTN IPC the latency is still way too high.

Don't confuse the max with the averages though. If you look at the average for the day it's sitting at 19 & 62ms respectively for Green vs MTN.

AfriFella · Sep 16, 2015

Dan C said:
Why is mine so high on the 2nd hop ?

Higher latency on the 2nd hop usually indicates exchange congestion...

Dan C · Sep 16, 2015

AfriFella said:
Higher latency on the 2nd hop usually indicates exchange congestion...

Check my Telkom ISP traceroute.. it was 8ms

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 8 ms 8 ms eel-ip-bb-1.south.dsl.telkomsa.net [105.224.120.1]
3 46 ms 45 ms 49 ms ipc-3-up.south.dsl.telkomsa.net [105.226.0.246]

AfriFella · Sep 16, 2015

Dan C said:
Check my Telkom ISP traceroute.. it was 8ms

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 8 ms 8 ms eel-ip-bb-1.south.dsl.telkomsa.net [105.224.120.1]
3 46 ms 45 ms 49 ms ipc-3-up.south.dsl.telkomsa.net [105.226.0.246]

Hmm sorry I didn't notice that. We'll definitely have to troubleshoot this a little more and we'll need some more info. Please send me a PM with your account details and our team will contact you so we can run some more tests.

Dan C · Sep 16, 2015

AfriFella said:
Hmm sorry I didn't notice that. We'll definitely have to troubleshoot this a little more and we'll need some more info. Please send me a PM with your account details and our team will contact you so we can run some more tests.

Seems fine now.. maybe it was something on my network :twisted: Will let you know when it happens again.

AfriFella · Sep 16, 2015

Dan C said:
Seems fine now.. maybe it was something on my network :twisted: Will let you know when it happens again.

Very weird... Glad to hear it's looking better! Feel free to send me a PM at any time.

Join the MyBroadband community

Get started

Afrihost POC Network - Afrigreen Feedback

Well-Known Member

Afrihost

Executive Member

Honorary Master

Honorary Master

Well-Known Member

Afrihost

Well-Known Member

Honorary Master

Honorary Master

Honorary Master

Executive Member

Afrihost

Honorary Master

Well-Known Member

Afrihost

Honorary Master

Afrihost

Honorary Master

Afrihost