Afrihost New Network Feedback - Part 2

fishfly · Jul 27, 2016

AfriGuy said:
Ah nice one dude, lucky!!
If you don't need DSL anymore you can cancel everything via ClientZone, the line and data will stay active until the end of August - you'll have to specifically that specifically for your line though

Just a heads up that our DSL data does work on fibre, we just need to finalise our line provider offerings.

Yeah with Telkom - as mentioned I refuse to deal with Telkom any longer than I need to...

AfriGuy · Jul 27, 2016

fishfly said:
Yeah with Telkom - as mentioned I refuse to deal with Telkom any longer than I need to...

Alrighty

Hopefully we can hook you up when our fibre deals launch!

Quad! · Jul 27, 2016

Where in the Client Zone can you Upload your ID??

I am only Using the client zone for Mobile section not ADSL.. do you still need my ID??

AfriFella · Jul 27, 2016

Quad! said:
Where in the Client Zone can you Upload your ID??

I am only Using the client zone for Mobile section not ADSL.. do you still need my ID??

All ClientZone accounts have to be verified with an ID document.

If CZ hasn't prompted you to upload, please send a copy of your ID through to [email protected] and our team will sort you out.

Hummercellc · Jul 27, 2016

Mweb network inaccessible again, cry...
11th night in a row...

Masik3R · Jul 27, 2016

AfriGuy said:
That's a bit of a PITA though.
I've logged some testing for myself later this evening, I'll report back tomorrow morning. Any specific host/ IP I can test?

Please also try and grab some results this evening.

Here you go

C:\Users\Ryan>tracert www.mweb.co.za

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

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 28 ms 27 ms 27 ms cpt-tx2.ip.adsl.co.za [169.1.5.81]
4 81 ms 87 ms 89 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
5 81 ms 87 ms 99 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 34 ms 34 ms 34 ms optinet.ixp.capetown [196.10.140.145]
7 29 ms 30 ms 31 ms te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2]
8 106 ms 90 ms 85 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
9 28 ms 28 ms 27 ms 196.28.178.66
10 41 ms 41 ms 38 ms cte-core-sw2.vwol.net [196.41.144.35]
11 684 ms 115 ms 113 ms www.mweb.co.za [196.2.63.110]

And a test on VOX to compare;

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

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 34 ms 29 ms 30 ms telkom-upload-vlan-tygerberg-ipc.vox.co.za [41.193.121.37]
4 30 ms 40 ms 37 ms vox-upload-teraco-cpt-tygerberg-ipc.vox.co.za [41.193.121.38]
5 29 ms 28 ms 26 ms vox-b2b-pts-tygerberg-ipc-int.vox.co.za [196.41.29.233]
6 29 ms 30 ms 29 ms mweb.cinx.net.za [196.223.22.32]
7 36 ms 43 ms 33 ms te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2]
8 40 ms 36 ms 28 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
9 39 ms 45 ms 48 ms 196.28.178.66
10 26 ms 26 ms 29 ms cte-core-sw2.vwol.net [196.41.144.35]
11 29 ms 28 ms 28 ms www.mweb.co.za [196.2.63.110]

AfriGuy · Jul 27, 2016

Masik3R said:
Here you go

C:\Users\Ryan>tracert www.mweb.co.za

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

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 28 ms 27 ms 27 ms cpt-tx2.ip.adsl.co.za [169.1.5.81]
4 81 ms 87 ms 89 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
5 81 ms 87 ms 99 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 34 ms 34 ms 34 ms optinet.ixp.capetown [196.10.140.145]
7 29 ms 30 ms 31 ms te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2]
8 106 ms 90 ms 85 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
9 28 ms 28 ms 27 ms 196.28.178.66
10 41 ms 41 ms 38 ms cte-core-sw2.vwol.net [196.41.144.35]
11 684 ms 115 ms 113 ms www.mweb.co.za [196.2.63.110]

And a test on VOX to compare;

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

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 34 ms 29 ms 30 ms telkom-upload-vlan-tygerberg-ipc.vox.co.za [41.193.121.37]
4 30 ms 40 ms 37 ms vox-upload-teraco-cpt-tygerberg-ipc.vox.co.za [41.193.121.38]
5 29 ms 28 ms 26 ms vox-b2b-pts-tygerberg-ipc-int.vox.co.za [196.41.29.233]
6 29 ms 30 ms 29 ms mweb.cinx.net.za [196.223.22.32]
7 36 ms 43 ms 33 ms te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2]
8 40 ms 36 ms 28 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
9 39 ms 45 ms 48 ms 196.28.178.66
10 26 ms 26 ms 29 ms cte-core-sw2.vwol.net [196.41.144.35]
11 29 ms 28 ms 28 ms www.mweb.co.za [196.2.63.110]

Just ran the same test, looks like latency is coming in at 169.1.5.82 for you, but seeing as you're in PE you physically have a bit of a longer distance to run, so I wonder if this is a backhaul issue of sorts. My latency over that destination reports as 14ms.

Code:

traceroute to mweb.co.za (196.2.63.110), 64 hops max, 52 byte packets
 1  router.asus.com (192.168.1.1)  0.813 ms  0.540 ms  0.469 ms
 2  * * *
 3  cpt-up1.ip.adsl.co.za (169.1.5.105)  13.874 ms  12.373 ms  12.259 ms
 4  cpt-up2.ip.adsl.co.za (169.1.5.106)  13.803 ms  12.706 ms  12.299 ms
 5  cpt-net1.ip.adsl.co.za (169.1.5.128)  12.797 ms  14.357 ms  13.489 ms
 6  optinet.ixp.capetown (196.10.140.145)  14.661 ms  13.315 ms  13.450 ms
 7  te0-0-0-1.cpt-p-1.optinet.net (197.84.7.1)  27.224 ms  23.710 ms
    te0-0-0-1.cpt-p-2.optinet.net (197.84.7.34)  17.265 ms
 8  vl11.cpt-hscore-1.optinet.net (197.84.5.238)  21.673 ms  28.424 ms  30.047 ms
 9  196.28.178.66 (196.28.178.66)  25.527 ms  32.897 ms  23.745 ms
10  cte-core-sw2.vwol.net (196.41.144.35)  33.235 ms  31.559 ms  33.681 ms

Masik3R · Jul 27, 2016

AfriGuy said:
Just ran the same test, looks like latency is coming in at 169.1.5.82 for you, but seeing as you're in PE you physically have a bit of a longer distance to run, so I wonder if this is a backhaul issue of sorts. My latency over that destination reports as 14ms.

That is very weird

standerr · Jul 27, 2016

Struggling with latency again

Code:

Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3    85 ms    85 ms    92 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    23 ms    20 ms    21 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5   115 ms   113 ms   114 ms  optinet.ixp.capetown [196.10.140.145] 
  6   107 ms   100 ms    93 ms  te0-0-0-1.cpt-p-1.optinet.net [197.84.7.1] 
  7    21 ms    24 ms    25 ms  vl12.cpt-hscore-2.optinet.net [197.84.5.254] 
  8   109 ms   112 ms   117 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70] 
  9    22 ms    22 ms    23 ms  gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166] 
 10    96 ms    71 ms    48 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 11    23 ms    23 ms    25 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 12   125 ms   122 ms   116 ms  41-86-110-200.mweb.co.za [41.86.110.200] 

Trace complete.

Ping to 196.10.140.145

Code:

Pinging 196.10.140.145 with 32 bytes of data:
Reply from 196.10.140.145: bytes=32 time=103ms TTL=251
Reply from 196.10.140.145: bytes=32 time=103ms TTL=251
Reply from 196.10.140.145: bytes=32 time=121ms TTL=251
Reply from 196.10.140.145: bytes=32 time=123ms TTL=251
Reply from 196.10.140.145: bytes=32 time=125ms TTL=251
Reply from 196.10.140.145: bytes=32 time=51ms TTL=251
Reply from 196.10.140.145: bytes=32 time=81ms TTL=251
Reply from 196.10.140.145: bytes=32 time=101ms TTL=251
Reply from 196.10.140.145: bytes=32 time=127ms TTL=251
Reply from 196.10.140.145: bytes=32 time=53ms TTL=251

Ping to 169.1.5.82

Code:

Pinging 169.1.5.82 with 32 bytes of data:
Reply from 169.1.5.82: bytes=32 time=72ms TTL=60
Reply from 169.1.5.82: bytes=32 time=48ms TTL=60
Reply from 169.1.5.82: bytes=32 time=25ms TTL=60
Reply from 169.1.5.82: bytes=32 time=40ms TTL=60
Reply from 169.1.5.82: bytes=32 time=44ms TTL=60
Reply from 169.1.5.82: bytes=32 time=66ms TTL=60
Reply from 169.1.5.82: bytes=32 time=99ms TTL=60
Reply from 169.1.5.82: bytes=32 time=22ms TTL=60
Reply from 169.1.5.82: bytes=32 time=92ms TTL=60
Reply from 169.1.5.82: bytes=32 time=60ms TTL=60
Reply from 169.1.5.82: bytes=32 time=97ms TTL=60
Reply from 169.1.5.82: bytes=32 time=61ms TTL=60
Reply from 169.1.5.82: bytes=32 time=82ms TTL=60
Reply from 169.1.5.82: bytes=32 time=85ms TTL=60
Reply from 169.1.5.82: bytes=32 time=43ms TTL=60
Reply from 169.1.5.82: bytes=32 time=218ms TTL=60
Reply from 169.1.5.82: bytes=32 time=85ms TTL=60
Reply from 169.1.5.82: bytes=32 time=79ms TTL=60
Reply from 169.1.5.82: bytes=32 time=102ms TTL=60
Reply from 169.1.5.82: bytes=32 time=112ms TTL=60

standerr · Jul 27, 2016

Definitely something not lekker going on. Just switched over to Telkom and things are much better. Could not even upload files to OneDrive on Afrihost, but all works fine on Telkom.

News24 Telkom

Code:

Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3    21 ms    21 ms    21 ms  ipc-1-up.south.dsl.telkomsa.net [105.226.0.6] 
  4    21 ms    20 ms    24 ms  ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13] 
  5    23 ms    22 ms    21 ms  blv-pr-02-be200-vl1.net.telkomsa.net [105.226.0.54] 
  6    21 ms    21 ms    21 ms  ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138] 
  7    22 ms    31 ms    22 ms  optinet.ixp.capetown [196.10.140.15] 
  8    26 ms    27 ms    23 ms  te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2] 
  9    22 ms    21 ms    21 ms  vl12.cpt-hscore-2.optinet.net [197.84.5.254] 
 10    22 ms    22 ms    22 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70] 
 11    22 ms    22 ms    23 ms  gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166] 
 12    24 ms    23 ms    23 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 13    22 ms    22 ms    22 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 14    22 ms    31 ms    23 ms  41-86-110-200.mweb.co.za [41.86.110.200] 

Trace complete.

News24 Afrihost

Code:

Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3    69 ms    65 ms    64 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    21 ms    21 ms    22 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5    70 ms    69 ms    72 ms  optinet.ixp.capetown [196.10.140.145] 
  6    95 ms    97 ms   100 ms  te0-0-0-1.cpt-p-1.optinet.net [197.84.7.1] 
  7    58 ms    57 ms    67 ms  vl12.cpt-hscore-2.optinet.net [197.84.5.254] 
  8   114 ms    99 ms    86 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70] 
  9    22 ms    22 ms    22 ms  gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166] 
 10    81 ms    85 ms    94 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 11    23 ms    23 ms    21 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 12    91 ms    99 ms    98 ms  41-86-110-200.mweb.co.za [41.86.110.200] 

Trace complete.

Stackoverflow Telkom

Code:

Tracing route to stackoverflow.com [151.101.1.69]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3    22 ms    20 ms    21 ms  ipc-1-up.south.dsl.telkomsa.net [105.226.0.6] 
  4    25 ms    21 ms    21 ms  ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13] 
  5    21 ms    24 ms    22 ms  wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39.45] 
  6   189 ms   190 ms   190 ms  fra-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.43.9.110] 
  7   216 ms   221 ms   222 ms  te0-7-0-11.agr21.fra06.atlas.cogentco.com [149.11.20.65] 
  8     *        *        *     Request timed out.
  9   221 ms   209 ms   199 ms  151.101.1.69 

Trace complete.

Stackoverflow Afrihost

Code:

Tracing route to stackoverflow.com [151.101.193.69]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3    75 ms    76 ms    79 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    20 ms    21 ms    21 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5    22 ms    22 ms    21 ms  41.164.52.40 
  6   146 ms   148 ms   146 ms  172.18.1.162 
  7   453 ms   465 ms   475 ms  ix-xe-0-0-0-231.thar2.1MH-Sydney.as6453.net [180.87.29.121] 
  8   451 ms   590 ms   404 ms  220.101.73.73 
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13   472 ms   482 ms   503 ms  59.154.57.222 
 14   533 ms   494 ms   641 ms  Bundle-Ether11.lon-edge901.melbourne.telstra.net [139.130.105.1] 
 15   420 ms   418 ms   419 ms  bundle-ether2.win-edge901.melbourne.telstra.net [203.50.11.114] 
 16     *        *        *     Request timed out.
 17   446 ms   455 ms   468 ms  151.101.193.69 

Trace complete.

OneDrive Telkom

Code:

Tracing route to a-0014.a-msedge.net [204.79.197.217]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3    22 ms    20 ms    20 ms  ipc-1-up.south.dsl.telkomsa.net [105.226.0.6] 
  4    21 ms    20 ms    21 ms  ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13] 
  5    21 ms    21 ms    21 ms  blv-pr-02-be200-vl1.net.telkomsa.net [105.226.0.54] 
  6    21 ms    21 ms    21 ms  ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138] 
  7    21 ms    25 ms    21 ms  microsoft.ixp.capetown [196.10.140.47] 
  8    22 ms    25 ms    22 ms  ae0-0.cpt02-96cbe-1b.ntwk.msn.net [104.44.228.15] 
  9    91 ms    87 ms    84 ms  ae1-0.jnb02-96cbe-1b.ntwk.msn.net [104.44.228.16] 
 10    88 ms    97 ms    89 ms  tor1.jnb02.msedge.net [131.253.6.215] 
 11     *        *        *     Request timed out.
 12    91 ms    90 ms    88 ms  204.79.197.217 

Trace complete.

OneDrive Afrihost

Code:

Tracing route to a-0014.a-msedge.net [204.79.197.217]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3   111 ms   111 ms   115 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    21 ms    22 ms    22 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5    22 ms    21 ms    22 ms  41.164.52.40 
  6   385 ms   190 ms   182 ms  microsoft.ixp.capetown [196.10.140.47] 
  7   189 ms   201 ms   185 ms  ae0-0.cpt02-96cbe-1b.ntwk.msn.net [104.44.228.15] 
  8   186 ms   186 ms   186 ms  ae1-0.jnb02-96cbe-1b.ntwk.msn.net [104.44.228.16] 
  9   184 ms   182 ms   188 ms  tor1.jnb02.msedge.net [131.253.6.215] 
 10     *        *        *     Request timed out.
 11   209 ms   218 ms   220 ms  204.79.197.217 

Trace complete.

Afrihost you need to get a handle on this.

Masik3R · Jul 27, 2016

And now everything back to normal;

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

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 28 ms 27 ms 27 ms cpt-tx2.ip.adsl.co.za [169.1.5.81]
4 35 ms 34 ms 34 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
5 29 ms 27 ms 26 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 40 ms 35 ms 35 ms optinet.ixp.capetown [196.10.140.145]
7 27 ms 30 ms 30 ms te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2]
8 35 ms 34 ms 34 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
9 28 ms 47 ms 37 ms 196.28.178.66
10 35 ms 34 ms 34 ms cte-core-sw2.vwol.net [196.41.144.35]
11 35 ms 35 ms 34 ms www.mweb.co.za [196.2.63.110]

Hummercellc · Jul 28, 2016

Masik3R said:
And now everything back to normal;

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

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 28 ms 27 ms 27 ms cpt-tx2.ip.adsl.co.za [169.1.5.81]
4 35 ms 34 ms 34 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
5 29 ms 27 ms 26 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 40 ms 35 ms 35 ms optinet.ixp.capetown [196.10.140.145]
7 27 ms 30 ms 30 ms te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2]
8 35 ms 34 ms 34 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
9 28 ms 47 ms 37 ms 196.28.178.66
10 35 ms 34 ms 34 ms cte-core-sw2.vwol.net [196.41.144.35]
11 35 ms 35 ms 34 ms www.mweb.co.za [196.2.63.110]

Latency on Afrihost's network is very inconsistent, in the 100 one second then mid teens the next. If I switch to another ISP latency is constant. So I am seeing the same results as you.

AfriGenie · Jul 28, 2016

standerr said:

Struggling with latency again

Code:

Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3    85 ms    85 ms    92 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    23 ms    20 ms    21 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5   115 ms   113 ms   114 ms  optinet.ixp.capetown [196.10.140.145] 
  6   107 ms   100 ms    93 ms  te0-0-0-1.cpt-p-1.optinet.net [197.84.7.1] 
  7    21 ms    24 ms    25 ms  vl12.cpt-hscore-2.optinet.net [197.84.5.254] 
  8   109 ms   112 ms   117 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70] 
  9    22 ms    22 ms    23 ms  gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166] 
 10    96 ms    71 ms    48 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 11    23 ms    23 ms    25 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 12   125 ms   122 ms   116 ms  41-86-110-200.mweb.co.za [41.86.110.200] 

Trace complete.

Ping to 196.10.140.145

Code:

Pinging 196.10.140.145 with 32 bytes of data:
Reply from 196.10.140.145: bytes=32 time=103ms TTL=251
Reply from 196.10.140.145: bytes=32 time=103ms TTL=251
Reply from 196.10.140.145: bytes=32 time=121ms TTL=251
Reply from 196.10.140.145: bytes=32 time=123ms TTL=251
Reply from 196.10.140.145: bytes=32 time=125ms TTL=251
Reply from 196.10.140.145: bytes=32 time=51ms TTL=251
Reply from 196.10.140.145: bytes=32 time=81ms TTL=251
Reply from 196.10.140.145: bytes=32 time=101ms TTL=251
Reply from 196.10.140.145: bytes=32 time=127ms TTL=251
Reply from 196.10.140.145: bytes=32 time=53ms TTL=251

Ping to 169.1.5.82

Code:

Pinging 169.1.5.82 with 32 bytes of data:
Reply from 169.1.5.82: bytes=32 time=72ms TTL=60
Reply from 169.1.5.82: bytes=32 time=48ms TTL=60
Reply from 169.1.5.82: bytes=32 time=25ms TTL=60
Reply from 169.1.5.82: bytes=32 time=40ms TTL=60
Reply from 169.1.5.82: bytes=32 time=44ms TTL=60
Reply from 169.1.5.82: bytes=32 time=66ms TTL=60
Reply from 169.1.5.82: bytes=32 time=99ms TTL=60
Reply from 169.1.5.82: bytes=32 time=22ms TTL=60
Reply from 169.1.5.82: bytes=32 time=92ms TTL=60
Reply from 169.1.5.82: bytes=32 time=60ms TTL=60
Reply from 169.1.5.82: bytes=32 time=97ms TTL=60
Reply from 169.1.5.82: bytes=32 time=61ms TTL=60
Reply from 169.1.5.82: bytes=32 time=82ms TTL=60
Reply from 169.1.5.82: bytes=32 time=85ms TTL=60
Reply from 169.1.5.82: bytes=32 time=43ms TTL=60
Reply from 169.1.5.82: bytes=32 time=218ms TTL=60
Reply from 169.1.5.82: bytes=32 time=85ms TTL=60
Reply from 169.1.5.82: bytes=32 time=79ms TTL=60
Reply from 169.1.5.82: bytes=32 time=102ms TTL=60
Reply from 169.1.5.82: bytes=32 time=112ms TTL=60

standerr said:

Definitely something not lekker going on. Just switched over to Telkom and things are much better. Could not even upload files to OneDrive on Afrihost, but all works fine on Telkom.

News24 Telkom

Code:

Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3    21 ms    21 ms    21 ms  ipc-1-up.south.dsl.telkomsa.net [105.226.0.6] 
  4    21 ms    20 ms    24 ms  ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13] 
  5    23 ms    22 ms    21 ms  blv-pr-02-be200-vl1.net.telkomsa.net [105.226.0.54] 
  6    21 ms    21 ms    21 ms  ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138] 
  7    22 ms    31 ms    22 ms  optinet.ixp.capetown [196.10.140.15] 
  8    26 ms    27 ms    23 ms  te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2] 
  9    22 ms    21 ms    21 ms  vl12.cpt-hscore-2.optinet.net [197.84.5.254] 
 10    22 ms    22 ms    22 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70] 
 11    22 ms    22 ms    23 ms  gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166] 
 12    24 ms    23 ms    23 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 13    22 ms    22 ms    22 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 14    22 ms    31 ms    23 ms  41-86-110-200.mweb.co.za [41.86.110.200] 

Trace complete.

News24 Afrihost

Code:

Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3    69 ms    65 ms    64 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    21 ms    21 ms    22 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5    70 ms    69 ms    72 ms  optinet.ixp.capetown [196.10.140.145] 
  6    95 ms    97 ms   100 ms  te0-0-0-1.cpt-p-1.optinet.net [197.84.7.1] 
  7    58 ms    57 ms    67 ms  vl12.cpt-hscore-2.optinet.net [197.84.5.254] 
  8   114 ms    99 ms    86 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70] 
  9    22 ms    22 ms    22 ms  gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166] 
 10    81 ms    85 ms    94 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 11    23 ms    23 ms    21 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 12    91 ms    99 ms    98 ms  41-86-110-200.mweb.co.za [41.86.110.200] 

Trace complete.

Stackoverflow Telkom

Code:

Tracing route to stackoverflow.com [151.101.1.69]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3    22 ms    20 ms    21 ms  ipc-1-up.south.dsl.telkomsa.net [105.226.0.6] 
  4    25 ms    21 ms    21 ms  ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13] 
  5    21 ms    24 ms    22 ms  wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39.45] 
  6   189 ms   190 ms   190 ms  fra-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.43.9.110] 
  7   216 ms   221 ms   222 ms  te0-7-0-11.agr21.fra06.atlas.cogentco.com [149.11.20.65] 
  8     *        *        *     Request timed out.
  9   221 ms   209 ms   199 ms  151.101.1.69 

Trace complete.

Stackoverflow Afrihost

Code:

Tracing route to stackoverflow.com [151.101.193.69]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3    75 ms    76 ms    79 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    20 ms    21 ms    21 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5    22 ms    22 ms    21 ms  41.164.52.40 
  6   146 ms   148 ms   146 ms  172.18.1.162 
  7   453 ms   465 ms   475 ms  ix-xe-0-0-0-231.thar2.1MH-Sydney.as6453.net [180.87.29.121] 
  8   451 ms   590 ms   404 ms  220.101.73.73 
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13   472 ms   482 ms   503 ms  59.154.57.222 
 14   533 ms   494 ms   641 ms  Bundle-Ether11.lon-edge901.melbourne.telstra.net [139.130.105.1] 
 15   420 ms   418 ms   419 ms  bundle-ether2.win-edge901.melbourne.telstra.net [203.50.11.114] 
 16     *        *        *     Request timed out.
 17   446 ms   455 ms   468 ms  151.101.193.69 

Trace complete.

OneDrive Telkom

Code:

Tracing route to a-0014.a-msedge.net [204.79.197.217]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3    22 ms    20 ms    20 ms  ipc-1-up.south.dsl.telkomsa.net [105.226.0.6] 
  4    21 ms    20 ms    21 ms  ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13] 
  5    21 ms    21 ms    21 ms  blv-pr-02-be200-vl1.net.telkomsa.net [105.226.0.54] 
  6    21 ms    21 ms    21 ms  ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138] 
  7    21 ms    25 ms    21 ms  microsoft.ixp.capetown [196.10.140.47] 
  8    22 ms    25 ms    22 ms  ae0-0.cpt02-96cbe-1b.ntwk.msn.net [104.44.228.15] 
  9    91 ms    87 ms    84 ms  ae1-0.jnb02-96cbe-1b.ntwk.msn.net [104.44.228.16] 
 10    88 ms    97 ms    89 ms  tor1.jnb02.msedge.net [131.253.6.215] 
 11     *        *        *     Request timed out.
 12    91 ms    90 ms    88 ms  204.79.197.217 

Trace complete.

OneDrive Afrihost

Code:

Tracing route to a-0014.a-msedge.net [204.79.197.217]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3   111 ms   111 ms   115 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    21 ms    22 ms    22 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5    22 ms    21 ms    22 ms  41.164.52.40 
  6   385 ms   190 ms   182 ms  microsoft.ixp.capetown [196.10.140.47] 
  7   189 ms   201 ms   185 ms  ae0-0.cpt02-96cbe-1b.ntwk.msn.net [104.44.228.15] 
  8   186 ms   186 ms   186 ms  ae1-0.jnb02-96cbe-1b.ntwk.msn.net [104.44.228.16] 
  9   184 ms   182 ms   188 ms  tor1.jnb02.msedge.net [131.253.6.215] 
 10     *        *        *     Request timed out.
 11   209 ms   218 ms   220 ms  204.79.197.217 

Trace complete.

Afrihost you need to get a handle on this.

Yeah... I'm seeing some spikes that probably shouldn't be that high. I'm going to pass these results onto our Team to have a look at.

Masik3R · Jul 28, 2016

AfriGenie said:
Yeah... I'm seeing some spikes that probably shouldn't be that high. I'm going to pass these results onto our Team to have a look at.

Please note that this only happens in the evenings

AfriGuy · Jul 28, 2016

Masik3R said:
That is very weird

standerr said:
Struggling with latency again

-snip

Masik3R said:
Please note that this only happens in the evenings

Morning guys

Thanks for posting up these results, they're hugely helpful

Seeing as you're all running via the South IPC there may be a trend here. I personally can't see anything wrong, but that doesn't mean there's something odd happening.

My latency to MWEB seemed to hover around 60ms last night during my tests between 21:00 and 22:00, but not on hops within our network.

I'll get all the results passed onto our NOC guys for a thorough look through.

Icemanbrfc · Jul 28, 2016

AG are you here?

Freak_c · Jul 28, 2016

So last night was also getting the high latencey issue again started around 6:30pm then line went completely dead at 9pm.

Got this from a live chat this morning from Afrihost.

Outage No: 121291 - ADSL outage affecting elm & bloekom f9a5 msan 1 (011452, 011524, 011609) detected on 27-Jul at 20:46
telkom is working on it

So now i wait to see if it comes back

krustyrsa · Jul 28, 2016

Youtube not loading HD, stuck on 144p on AUTO.

With Getflix DNS

with Afrihost DNS

Speed test show no issues

tracert test

AfriGuy · Jul 28, 2016

Icemanbrfc said:
AG are you here?

Always

AfriGuy · Jul 28, 2016

Freak_c said:
So last night was also getting the high latencey issue again started around 6:30pm then line went completely dead at 9pm.

Got this from a live chat this morning from Afrihost.

So now i wait to see if it comes back

Hopefully it's a quick fix

Join the MyBroadband community

Get started

Afrihost New Network Feedback - Part 2

Honorary Master

Afrihost

Well-Known Member

Afrihost

Expert Member

Well-Known Member

Afrihost

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Expert Member

Afrihost

Well-Known Member

Afrihost

Honorary Master

Well-Known Member

Senior Member

Afrihost

Afrihost