Afrihost New Network Feedback

Status
Not open for further replies.
cortexenslaver said:
Funny you mention that... I noticed that my afrihost.co.za username has lower latency, and seems much more snappy than my Afrigreen username.

AH
CPT - 8ms
JHB - 24ms

AG
CPT - 12ms
JHB - 34ms

....very weird hehehe
Click to expand...

Now that's very interesting indeed.
While the usernames differ, both run off exactly the same IPC.

Are you able to paste up some traceroutes of the comparisons?
 
Zertop said:
I have a feeling that @afrigreen likes to route through JHB, regardless of location...

Could be wrong though.

Z
Click to expand...

Not sure how that would be possible, as both will run via the same IPC.
You never know though, IPCs can be magical places :p

If you do notice a difference in routing between the two though, please paste up some comparative traceroutes.
 
Jypels said:
I have been switching between the two the last month or so.

been on afrihost.co.za username for last few days. just switched to afrigreen again and now throughput looks ok. (13.5mbps down /0.5 up
Click to expand...

Looks a bit better, not sure if't up to par for a 20Mbps connection though.
Can you monitor things over the next hour or so to see if there's any degradation in throughput?
 
AfriGuy said:
Looks a bit better, not sure if't up to par for a 20Mbps connection though.
Can you monitor things over the next hour or so to see if there's any degradation in throughput?
Click to expand...
Mmmh it has allready degraded. Doesnt want to go over 7.63mbps down and 0.25 up. Only the 1st test looked good
 
Jypels said:
Mmmh it has allready degraded. Doesnt want to go over 7.63mbps down and 0.25 up. Only the 1st test looked good
Click to expand...

That's strange.
Have you tried hooking up your 1GB account to see how things are there?
 
AfriGuy said:
Now that's very interesting indeed.
While the usernames differ, both run off exactly the same IPC.

Are you able to paste up some traceroutes of the comparisons?
Click to expand...
Here you go...

AH
Code: 
C:\Windows\system32>tracert afrihost.com

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

  1    <1 ms    <1 ms    <1 ms  home.gateway.pace.net [192.168.1.254]
  2    11 ms     7 ms     7 ms  169-0-54-1.ip.afrihost.co.za [169.0.54.1]
  3     *        *        *     Request timed out.
  4     9 ms     8 ms     8 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82]
  5     8 ms     8 ms     8 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6     8 ms     8 ms     8 ms  41.164.52.40
  7     9 ms     9 ms     9 ms  172.18.32.33
  8    10 ms    10 ms     9 ms  mtnns-2.cinx.net.za [196.223.22.31]
  9    11 ms    10 ms    10 ms  rb-cr-1.za.nl-ha-2.za-a.mtnns.net [196.44.0.120]

 10    10 ms    10 ms    10 ms  tb-cr-2.za--ct-cr-1.za-a.mtnns.net [196.44.31.10
7]
 11    33 ms    32 ms    33 ms  jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]

 12    32 ms    32 ms    32 ms  jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.21
7]
 13    32 ms    32 ms    32 ms  18.185.181.41.in-addr.aserv.co.za [41.181.185.18
]

Trace complete.

C:\Windows\system32>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  home.gateway.pace.net [192.168.1.254]
  2     8 ms     7 ms     7 ms  169-0-54-1.ip.afrihost.co.za [169.0.54.1]
  3     *        *        *     Request timed out.
  4     9 ms     9 ms     9 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82]
  5     8 ms     7 ms     8 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6     9 ms     9 ms     9 ms  optinet.ct1.napafrica.net [196.10.140.145]
  7     9 ms    11 ms    11 ms  te0-0-0-1.cpt-p-2.optinet.net [197.84.7.34]
  8     9 ms     8 ms     9 ms  vl11.cpt-hscore-1.optinet.net [197.84.5.238]
  9    23 ms    25 ms    24 ms  196.28.178.66
 10     9 ms     9 ms     9 ms  cte-core-sw2.vwol.net [196.41.144.35]
 11     9 ms     9 ms     9 ms  www.mweb.co.za [196.2.63.110]

Trace complete.
http://netgauge.ookla.com/share/305892540.png
http://netgauge.ookla.com/share/305893417.png

AG
Code: 
C:\Windows\system32>tracert afrihost.com

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

  1    <1 ms    <1 ms    <1 ms  home.gateway.pace.net [192.168.1.254]
  2     7 ms     7 ms     6 ms  169-0-54-1.ip.afrihost.co.za [169.0.54.1]
  3     *        *        *     Request timed out.
  4     9 ms     9 ms     8 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82]
  5     8 ms     8 ms     8 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6     9 ms     9 ms    10 ms  41.164.52.40
  7     9 ms     9 ms     9 ms  172.18.32.33
  8    10 ms     9 ms    10 ms  mtnns-2.cinx.net.za [196.223.22.31]
  9    11 ms    11 ms    10 ms  rb-cr-1.za.nl-ha-2.za-a.mtnns.net [196.44.0.120]

 10    11 ms    10 ms    10 ms  tb-cr-2.za--ct-cr-1.za-a.mtnns.net [196.44.31.10
7]
 11    32 ms    33 ms    32 ms  jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]

 12    32 ms    32 ms    32 ms  jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.21
7]
 13    32 ms    32 ms    32 ms  18.185.181.41.in-addr.aserv.co.za [41.181.185.18
]

Trace complete.

C:\Windows\system32>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  home.gateway.pace.net [192.168.1.254]
  2     7 ms     7 ms     7 ms  169-0-54-1.ip.afrihost.co.za [169.0.54.1]
  3     *        *        *     Request timed out.
  4    10 ms     9 ms     9 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82]
  5    15 ms     7 ms     8 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6     9 ms     9 ms     9 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     9 ms     9 ms     9 ms  vl11.cpt-hscore-1.optinet.net [197.84.5.238]
  9    10 ms     9 ms     9 ms  196.28.178.66
 10     9 ms     9 ms     9 ms  cte-core-sw2.vwol.net [196.41.144.35]
 11     9 ms    10 ms     9 ms  www.mweb.co.za [196.2.63.110]

Trace complete.
http://netgauge.ookla.com/share/305890194.png
http://netgauge.ookla.com/share/305891201.png
 
AfriGuy said:
Not sure how that would be possible, as both will run via the same IPC.
You never know though, IPCs can be magical places :p

If you do notice a difference in routing between the two though, please paste up some comparative traceroutes.
Click to expand...

Haha,

I'm probably wrong then! If I do notice anything, will do ;)

Z :)

P.S. No complaints this side! Rock solid latency and maxed-out downloads!
 
AfriGuy said:
All done.
Lemme know how things go over the next 20 mins.
Click to expand...

Download speeds seem back to normal. Just under 800kbps.

The downloading and browsing Facebook, Twitter, gmail etc issue still remains.

Tracing route to star.c10r.facebook.com [31.13.90.2]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 107 ms 105 ms 117 ms jhb-up7.ip.adsl.co.za [169.1.5.6]
4 9 ms 8 ms 8 ms jhb-up8b.ip.adsl.co.za [169.1.5.56]
5 10 ms 10 ms 9 ms 41.169.57.218
6 21 ms 9 ms 10 ms if-7-0.tcore1.JSO-Johannesburg.as6453.net [41.20
6.178.29]
7 186 ms 184 ms 184 ms if-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.1
78.2]
8 187 ms 186 ms 187 ms if-5-30.tcore2.PV9-Lisbon.as6453.net [80.231.159
.85]
9 181 ms 181 ms 180 ms if-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.
5]
10 188 ms 187 ms 187 ms if-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.
158.30]
11 188 ms 187 ms 187 ms if-19-2.tcore2.L78-London.as6453.net [80.231.138
.22]
12 182 ms 183 ms 182 ms if-2-2.tcore1.L78-London.as6453.net [80.231.131.
2]
13 185 ms 184 ms 182 ms if-17-2.tcore1.LDN-London.as6453.net [80.231.130
.130]
14 181 ms 180 ms 180 ms 195.219.83.186
15 180 ms 180 ms 180 ms ae-1.r00.londen10.uk.bb.gin.ntt.net [129.250.3.3
1]
16 175 ms 175 ms 175 ms 81.25.207.98
17 187 ms 189 ms 187 ms po102.psw01b.lhr3.tfbnw.net [74.119.79.105]
18 189 ms 188 ms 189 ms msw1ar.01.lhr3.tfbnw.net [173.252.65.156]
19 266 ms 280 ms 282 ms edge-star-shv-01-lhr3.facebook.com [31.13.90.2]


Trace complete.
 
KoolDaffy said:
Download speeds seem back to normal. Just under 800kbps.

The downloading and browsing Facebook, Twitter, gmail etc issue still remains.

Tracing route to star.c10r.facebook.com [31.13.90.2]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 107 ms 105 ms 117 ms jhb-up7.ip.adsl.co.za [169.1.5.6]
4 9 ms 8 ms 8 ms jhb-up8b.ip.adsl.co.za [169.1.5.56]
5 10 ms 10 ms 9 ms 41.169.57.218
6 21 ms 9 ms 10 ms if-7-0.tcore1.JSO-Johannesburg.as6453.net [41.20
6.178.29]
7 186 ms 184 ms 184 ms if-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.1
78.2]
8 187 ms 186 ms 187 ms if-5-30.tcore2.PV9-Lisbon.as6453.net [80.231.159
.85]
9 181 ms 181 ms 180 ms if-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.
5]
10 188 ms 187 ms 187 ms if-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.
158.30]
11 188 ms 187 ms 187 ms if-19-2.tcore2.L78-London.as6453.net [80.231.138
.22]
12 182 ms 183 ms 182 ms if-2-2.tcore1.L78-London.as6453.net [80.231.131.
2]
13 185 ms 184 ms 182 ms if-17-2.tcore1.LDN-London.as6453.net [80.231.130
.130]
14 181 ms 180 ms 180 ms 195.219.83.186
15 180 ms 180 ms 180 ms ae-1.r00.londen10.uk.bb.gin.ntt.net [129.250.3.3
1]
16 175 ms 175 ms 175 ms 81.25.207.98
17 187 ms 189 ms 187 ms po102.psw01b.lhr3.tfbnw.net [74.119.79.105]
18 189 ms 188 ms 189 ms msw1ar.01.lhr3.tfbnw.net [173.252.65.156]
19 266 ms 280 ms 282 ms edge-star-shv-01-lhr3.facebook.com [31.13.90.2]


Trace complete.
Click to expand...

Please run my second tool in my desc, just for interests sake :)

Z
 
cortexenslaver said:
Here you go...

AH
Code: 
C:\Windows\system32>tracert afrihost.com

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

  1    <1 ms    <1 ms    <1 ms  home.gateway.pace.net [192.168.1.254]
  2    11 ms     7 ms     7 ms  169-0-54-1.ip.afrihost.co.za [169.0.54.1]
  3     *        *        *     Request timed out.
  4     9 ms     8 ms     8 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82]
  5     8 ms     8 ms     8 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6     8 ms     8 ms     8 ms  41.164.52.40
  7     9 ms     9 ms     9 ms  172.18.32.33
  8    10 ms    10 ms     9 ms  mtnns-2.cinx.net.za [196.223.22.31]
  9    11 ms    10 ms    10 ms  rb-cr-1.za.nl-ha-2.za-a.mtnns.net [196.44.0.120]

 10    10 ms    10 ms    10 ms  tb-cr-2.za--ct-cr-1.za-a.mtnns.net [196.44.31.10
7]
 11    33 ms    32 ms    33 ms  jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]

 12    32 ms    32 ms    32 ms  jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.21
7]
 13    32 ms    32 ms    32 ms  18.185.181.41.in-addr.aserv.co.za [41.181.185.18
]

Trace complete.

C:\Windows\system32>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  home.gateway.pace.net [192.168.1.254]
  2     8 ms     7 ms     7 ms  169-0-54-1.ip.afrihost.co.za [169.0.54.1]
  3     *        *        *     Request timed out.
  4     9 ms     9 ms     9 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82]
  5     8 ms     7 ms     8 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6     9 ms     9 ms     9 ms  optinet.ct1.napafrica.net [196.10.140.145]
  7     9 ms    11 ms    11 ms  te0-0-0-1.cpt-p-2.optinet.net [197.84.7.34]
  8     9 ms     8 ms     9 ms  vl11.cpt-hscore-1.optinet.net [197.84.5.238]
  9    23 ms    25 ms    24 ms  196.28.178.66
 10     9 ms     9 ms     9 ms  cte-core-sw2.vwol.net [196.41.144.35]
 11     9 ms     9 ms     9 ms  www.mweb.co.za [196.2.63.110]

Trace complete.
http://netgauge.ookla.com/share/305892540.png
http://netgauge.ookla.com/share/305893417.png

AG
Code: 
C:\Windows\system32>tracert afrihost.com

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

  1    <1 ms    <1 ms    <1 ms  home.gateway.pace.net [192.168.1.254]
  2     7 ms     7 ms     6 ms  169-0-54-1.ip.afrihost.co.za [169.0.54.1]
  3     *        *        *     Request timed out.
  4     9 ms     9 ms     8 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82]
  5     8 ms     8 ms     8 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6     9 ms     9 ms    10 ms  41.164.52.40
  7     9 ms     9 ms     9 ms  172.18.32.33
  8    10 ms     9 ms    10 ms  mtnns-2.cinx.net.za [196.223.22.31]
  9    11 ms    11 ms    10 ms  rb-cr-1.za.nl-ha-2.za-a.mtnns.net [196.44.0.120]

 10    11 ms    10 ms    10 ms  tb-cr-2.za--ct-cr-1.za-a.mtnns.net [196.44.31.10
7]
 11    32 ms    33 ms    32 ms  jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]

 12    32 ms    32 ms    32 ms  jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.21
7]
 13    32 ms    32 ms    32 ms  18.185.181.41.in-addr.aserv.co.za [41.181.185.18
]

Trace complete.

C:\Windows\system32>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  home.gateway.pace.net [192.168.1.254]
  2     7 ms     7 ms     7 ms  169-0-54-1.ip.afrihost.co.za [169.0.54.1]
  3     *        *        *     Request timed out.
  4    10 ms     9 ms     9 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82]
  5    15 ms     7 ms     8 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6     9 ms     9 ms     9 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     9 ms     9 ms     9 ms  vl11.cpt-hscore-1.optinet.net [197.84.5.238]
  9    10 ms     9 ms     9 ms  196.28.178.66
 10     9 ms     9 ms     9 ms  cte-core-sw2.vwol.net [196.41.144.35]
 11     9 ms    10 ms     9 ms  www.mweb.co.za [196.2.63.110]

Trace complete.
http://netgauge.ookla.com/share/305890194.png
http://netgauge.ookla.com/share/305891201.png
Click to expand...

These results look identical to me.
Unless I'm being a noob?
 
KoolDaffy said:
Download speeds seem back to normal. Just under 800kbps.

The downloading and browsing Facebook, Twitter, gmail etc issue still remains.

Tracing route to star.c10r.facebook.com [31.13.90.2]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 107 ms 105 ms 117 ms jhb-up7.ip.adsl.co.za [169.1.5.6]
4 9 ms 8 ms 8 ms jhb-up8b.ip.adsl.co.za [169.1.5.56]
5 10 ms 10 ms 9 ms 41.169.57.218
6 21 ms 9 ms 10 ms if-7-0.tcore1.JSO-Johannesburg.as6453.net [41.20
6.178.29]
7 186 ms 184 ms 184 ms if-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.1
78.2]
8 187 ms 186 ms 187 ms if-5-30.tcore2.PV9-Lisbon.as6453.net [80.231.159
.85]
9 181 ms 181 ms 180 ms if-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.
5]
10 188 ms 187 ms 187 ms if-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.
158.30]
11 188 ms 187 ms 187 ms if-19-2.tcore2.L78-London.as6453.net [80.231.138
.22]
12 182 ms 183 ms 182 ms if-2-2.tcore1.L78-London.as6453.net [80.231.131.
2]
13 185 ms 184 ms 182 ms if-17-2.tcore1.LDN-London.as6453.net [80.231.130
.130]
14 181 ms 180 ms 180 ms 195.219.83.186
15 180 ms 180 ms 180 ms ae-1.r00.londen10.uk.bb.gin.ntt.net [129.250.3.3
1]
16 175 ms 175 ms 175 ms 81.25.207.98
17 187 ms 189 ms 187 ms po102.psw01b.lhr3.tfbnw.net [74.119.79.105]
18 189 ms 188 ms 189 ms msw1ar.01.lhr3.tfbnw.net [173.252.65.156]
19 266 ms 280 ms 282 ms edge-star-shv-01-lhr3.facebook.com [31.13.90.2]


Trace complete.
Click to expand...

Hard to tell from this test, but looks like latency is spiking up at the exchange.
Can you run a ping to bras.afrihost.com please?
 
Johnatan56 said:
http://bit.ly/1lqvJpd
Click to expand...

aah okay here/s the results of that

Zertop's "Is it my Line" Results
Date/Time: Mon Oct 26 17:28:25 CAT 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 8ms.
Your maximum ping was 10ms.

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:

Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms 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 = 7ms, Maximum = 10ms, Average = 8ms
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X