Afrihost POC Network - Afrigreen Feedback

Status
Not open for further replies.
Looking good thus far...

4763196291.png


/pats AfriTeam on the backs!

Awesome sauce :D
 
Morning AfriGuy

According to that Network IP check page both my AfriGreen and old/normal accounts are running on the new network. When doing a tracert I do see a difference between how they route. Is this expected? Specifically look at hop 4

AfriGreen:
Code:
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     6 ms     6 ms     6 ms  169-0-54-1.ip.afrihost.co.za [169.0.54.1] 
  3     *        *        *     Request timed out.
  4     9 ms     7 ms     8 ms  cpt-rx1.net.afrihost.co.za [169.1.5.94] 
  5    10 ms     7 ms     7 ms  cpt-net1.net.afrihost.co.za [169.1.5.128] 
  6     8 ms     8 ms     8 ms  optinet.ct1.napafrica.net [196.10.140.145] 
  7    12 ms    11 ms    12 ms  te0-0-0-1.cpt-p-1.optinet.net [197.84.7.1] 
  8     7 ms     8 ms     7 ms  vl12.cpt-hscore-2.optinet.net [197.84.5.254] 
  9    14 ms    13 ms    11 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70] 
 10     9 ms     9 ms     8 ms  www.mweb.co.za [196.2.63.110] 

Trace complete.

Old Account:
Code:
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     6 ms     6 ms     6 ms  169-0-54-1.ip.afrihost.co.za [169.0.54.1] 
  3     *        *        *     Request timed out.
  4     8 ms     7 ms     7 ms  cpt-rx2.net.afrihost.co.za [169.1.5.82] 
  5     7 ms     7 ms     7 ms  cpt-net1.net.afrihost.co.za [169.1.5.128] 
  6     9 ms     8 ms     8 ms  optinet.ct1.napafrica.net [196.10.140.145] 
  7     8 ms    11 ms    13 ms  te0-0-0-1.cpt-p-1.optinet.net [197.84.7.1] 
  8     9 ms    12 ms     8 ms  vl12.cpt-hscore-2.optinet.net [197.84.5.254] 
  9     9 ms     8 ms     8 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70] 
 10     8 ms     9 ms     9 ms  www.mweb.co.za [196.2.63.110] 

Trace complete.

The change may just be a finalisation in routing - the IPC in the South, East and North are all live now.
That latency looks fantastic btw!
 
I didn't think it was possible, but the network is running even better now that it's gone 'live' to everybody.

1517993675.png


Please give your team a big high five on my behalf!

Z
 
I didn't think it was possible, but the network is running even better now that it's gone 'live' to everybody.

1517993675.png


Please give your team a big high five on my behalf!

Z

That's looking strong :D
Thanks for posting! Keep us posted on how things go.
 
4763230808.png

Testing out the new network this morning on a prepaid capped account that still has some data active. Very impressed guys, props.

Too many ISPs offering far better value for money on capped accounts now to consider switching back though - especially when it comes to after hours / zero rated windows, but glad to see the much vaunted new network is actually solid.
 
View attachment 308402

Testing out the new network this morning on a prepaid capped account that still has some data active. Very impressed guys, props.

Too many ISPs offering far better value for money on capped accounts now to consider switching back though - especially when it comes to after hours / zero rated windows, but glad to see the much vaunted new network is actually solid.

Woohoo, awesome results here! And glad that you're happy :D
Watch this space around pricing too, just need to see the dust settle on the migration.
 
Hope this is just a temporary glitch, but seeing some latency creeping in now

Code:
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    20 ms     6 ms     6 ms  169-0-54-1.ip.afrihost.co.za [169.0.54.1] 
  3     *        *        *     Request timed out.
  4     8 ms     8 ms     8 ms  cpt-rx2.net.afrihost.co.za [169.1.5.82] 
  5   513 ms   563 ms    90 ms  cpt-net1.net.afrihost.co.za [169.1.5.128] 
  6   233 ms   227 ms   145 ms  optinet.ct1.napafrica.net [196.10.140.145] 
  7    11 ms    11 ms    11 ms  te0-0-0-1.cpt-p-1.optinet.net [197.84.7.1] 
  8   270 ms   386 ms   279 ms  vl12.cpt-hscore-2.optinet.net [197.84.5.254] 
  9     9 ms    10 ms     9 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70] 
 10     9 ms     8 ms     8 ms  www.mweb.co.za [196.2.63.110] 

Trace complete.
 
Hope this is just a temporary glitch, but seeing some latency creeping in now

Code:
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    20 ms     6 ms     6 ms  169-0-54-1.ip.afrihost.co.za [169.0.54.1] 
  3     *        *        *     Request timed out.
  4     8 ms     8 ms     8 ms  cpt-rx2.net.afrihost.co.za [169.1.5.82] 
  5   513 ms   563 ms    90 ms  cpt-net1.net.afrihost.co.za [169.1.5.128] 
  6   233 ms   227 ms   145 ms  optinet.ct1.napafrica.net [196.10.140.145] 
  7    11 ms    11 ms    11 ms  te0-0-0-1.cpt-p-1.optinet.net [197.84.7.1] 
  8   270 ms   386 ms   279 ms  vl12.cpt-hscore-2.optinet.net [197.84.5.254] 
  9     9 ms    10 ms     9 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70] 
 10     9 ms     8 ms     8 ms  www.mweb.co.za [196.2.63.110] 

Trace complete.

Hhhmm, odd results here.
What happens if you ping 169.1.5.12?
 
Hhhmm, odd results here.
What happens if you ping 169.1.5.12?

Code:
Pinging 169.1.5.12 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
 
Code:
Pinging 169.1.5.12 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Tracing to Mweb may be the problem - seems like they have some downtime right now. Can you try using a different site, like afrihost.com?
 
Tracing to Mweb may be the problem - seems like they have some downtime right now. Can you try using a different site, like afrihost.com?

Same thing it seems

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

  1    <1 ms    <1 ms    <1 ms  wall.exa [10.0.0.254]
  2    29 ms     7 ms     7 ms  169-0-54-1.ip.afrihost.co.za [169.0.54.1]
  3     *        *        *     Request timed out.
  4   503 ms   316 ms   224 ms  cpt-rx1.net.afrihost.co.za [169.1.5.94]
  5   585 ms   331 ms    96 ms  cpt-net1.net.afrihost.co.za [169.1.5.128]
  6   429 ms   248 ms    51 ms  41.164.52.40
  7   440 ms   460 ms   483 ms  172.18.32.33
  8   462 ms   229 ms    14 ms  mtnns-2.cinx.net.za [196.223.22.31]
  9   102 ms   108 ms   161 ms  rb-cr-1.za.nl-ha-2.za-a.mtnns.net [196.44.0.120]
 10    34 ms    22 ms    20 ms  tb-cr-2.za--ct-cr-1.za-a.mtnns.net [196.44.31.107]
 11   294 ms   363 ms   409 ms  jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
 12   104 ms   142 ms   127 ms  jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
 13   444 ms   463 ms   494 ms  18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.
 
Same thing it seems

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

  1    <1 ms    <1 ms    <1 ms  wall.exa [10.0.0.254]
  2    29 ms     7 ms     7 ms  169-0-54-1.ip.afrihost.co.za [169.0.54.1]
  3     *        *        *     Request timed out.
  4   503 ms   316 ms   224 ms  cpt-rx1.net.afrihost.co.za [169.1.5.94]
  5   585 ms   331 ms    96 ms  cpt-net1.net.afrihost.co.za [169.1.5.128]
  6   429 ms   248 ms    51 ms  41.164.52.40
  7   440 ms   460 ms   483 ms  172.18.32.33
  8   462 ms   229 ms    14 ms  mtnns-2.cinx.net.za [196.223.22.31]
  9   102 ms   108 ms   161 ms  rb-cr-1.za.nl-ha-2.za-a.mtnns.net [196.44.0.120]
 10    34 ms    22 ms    20 ms  tb-cr-2.za--ct-cr-1.za-a.mtnns.net [196.44.31.107]
 11   294 ms   363 ms   409 ms  jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
 12   104 ms   142 ms   127 ms  jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
 13   444 ms   463 ms   494 ms  18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.

Definitely looking worrying there. Will kick this up to the network team :(
 
Same thing it seems

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

  1    <1 ms    <1 ms    <1 ms  wall.exa [10.0.0.254]
  2    29 ms     7 ms     7 ms  169-0-54-1.ip.afrihost.co.za [169.0.54.1]
  3     *        *        *     Request timed out.
  4   503 ms   316 ms   224 ms  cpt-rx1.net.afrihost.co.za [169.1.5.94]
  5   585 ms   331 ms    96 ms  cpt-net1.net.afrihost.co.za [169.1.5.128]
  6   429 ms   248 ms    51 ms  41.164.52.40
  7   440 ms   460 ms   483 ms  172.18.32.33
  8   462 ms   229 ms    14 ms  mtnns-2.cinx.net.za [196.223.22.31]
  9   102 ms   108 ms   161 ms  rb-cr-1.za.nl-ha-2.za-a.mtnns.net [196.44.0.120]
 10    34 ms    22 ms    20 ms  tb-cr-2.za--ct-cr-1.za-a.mtnns.net [196.44.31.107]
 11   294 ms   363 ms   409 ms  jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
 12   104 ms   142 ms   127 ms  jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
 13   444 ms   463 ms   494 ms  18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.

Can I please get your username via PM?
 
Definitely looking worrying there. Will kick this up to the network team :(

FYI I did a modem power cycle and it looks better now. Hoping it was "confused" with the switch ;)

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

  1    <1 ms    <1 ms    <1 ms  wall.exa [10.0.0.254]
  2    13 ms     7 ms     8 ms  169-0-54-1.ip.afrihost.co.za [169.0.54.1]
  3     *        *        *     Request timed out.
  4    12 ms    12 ms    30 ms  cpt-rx1.net.afrihost.co.za [169.1.5.94]
  5    52 ms    35 ms    35 ms  cpt-net1.net.afrihost.co.za [169.1.5.128]
  6    34 ms    32 ms    19 ms  41.164.52.40
  7    23 ms    21 ms    11 ms  172.18.32.33
  8    34 ms    32 ms    29 ms  mtnns-2.cinx.net.za [196.223.22.31]
  9    11 ms    12 ms    18 ms  rb-cr-1.za.nl-ha-2.za-a.mtnns.net [196.44.0.120]
 10    38 ms    36 ms    28 ms  tb-cr-2.za--ct-cr-1.za-a.mtnns.net [196.44.31.107]
 11    53 ms    62 ms    42 ms  jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
 12    49 ms    84 ms    41 ms  jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
 13    54 ms    44 ms    43 ms  18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.
 
FYI I did a modem power cycle and it looks better now. Hoping it was "confused" with the switch ;)

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

  1    <1 ms    <1 ms    <1 ms  wall.exa [10.0.0.254]
  2    13 ms     7 ms     8 ms  169-0-54-1.ip.afrihost.co.za [169.0.54.1]
  3     *        *        *     Request timed out.
  4    12 ms    12 ms    30 ms  cpt-rx1.net.afrihost.co.za [169.1.5.94]
  5    52 ms    35 ms    35 ms  cpt-net1.net.afrihost.co.za [169.1.5.128]
  6    34 ms    32 ms    19 ms  41.164.52.40
  7    23 ms    21 ms    11 ms  172.18.32.33
  8    34 ms    32 ms    29 ms  mtnns-2.cinx.net.za [196.223.22.31]
  9    11 ms    12 ms    18 ms  rb-cr-1.za.nl-ha-2.za-a.mtnns.net [196.44.0.120]
 10    38 ms    36 ms    28 ms  tb-cr-2.za--ct-cr-1.za-a.mtnns.net [196.44.31.107]
 11    53 ms    62 ms    42 ms  jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
 12    49 ms    84 ms    41 ms  jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
 13    54 ms    44 ms    43 ms  18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.

Definitely better here but worried about those intermittent spikes. Have you only seen this today?
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X