Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
No they are not, they don't know what to do?
They say they are not dismissing it, but in the same breath they say everything is fine on the network front. :whistle:

If I take a look at the ticket our team are querying your setup so we can better try to replicate the issue.
Please keep our Critical Care team updated.
 
If I take a look at the ticket our team are querying your setup so we can better try to replicate the issue.
Please keep our Critical Care team updated.

This is the second time they are asking this question, to which I have already provided the details. I will reply just now.
 
This is the second time they are asking this question, to which I have already provided the details. I will reply just now.

Then you can simply quote your previous replies?
Our team really are doing their best to help and have setup multiple test scenarios to assist. Our Critical Care guys are the best team to chat to, to see this resolved.
 
Yes, we cannot pick up nor replicate any issues.

Seems Cancellation will be my only solution here, I have provided enough information, but they always want more.
I have tested everything I can from my side as I said in my very first message to Critical Care.
Critical Care are disputing that YouTube is being pulled from the Mweb Network, which in my case it is in fact pulling the video files from Mweb.
Hence the reason YouTube buffers for me between 7:30pm until 10:30pm, as YouTube can not access the Mweb Network from my side, so YouTube changes source to International.

EDIT: The reason I am hot under the collar here is, I maintain some sites hosted at Mweb and at 7:30 every night for the past ten night I have been able to do sweet nothing, I have to change over to another ISP to work. Which costs me more money as I am paying for two ISP's now...
 
Last edited:
Seems Cancellation will be my only solution here, I have provided enough information, but they always want more.
I have tested everything I can from my side as I said in my very first message to Critical Care.
Critical Care are disputing that YouTube is being pulled from the Mweb Network, which in my case it is in fact pulling the video files from Mweb.
Hence the reason YouTube buffers for me between 7:30pm until 10:30pm, as YouTube can not access the Mweb Network from my side, so YouTube changes source to International.

EDIT: The reason I am hot under the collar here is, I maintain some sites hosted at Mweb and at 7:30 every night for the past ten night I have been able to do sweet nothing, I have to change over to another ISP to work. Which costs me more money as I am paying for two ISP's now...

:(

The Critical Care Team is definitely making progress, they've figured out where the routing on your accounts is differing from how it should be routing. Once we've figured out WHY this is happening to you, and to no-one else from what we can see, we'll get you 100% sorted.
 
Uh... There's something seriously wrong there... That looks like there's an issue on your line or Exchange.

How are your speedtests looking at the moment?

Last speedtest i did after resetting router was 9.5mb down and 0.89mb up. ping was 25, but was spiking around 25 and 1000ms.

Then after 9:30pm or so last night was getting full HD on youtube no problem. then went to bed. My Kodi was a problem. When checking my sync i was getting full sync of 12mb down and 1mb up. Attenuation was Noise were spot on.

So no idea what it was, exchange congesstion?
 
Last speedtest i did after resetting router was 9.5mb down and 0.89mb up. ping was 25, but was spiking around 25 and 1000ms.

Then after 9:30pm or so last night was getting full HD on youtube no problem. then went to bed. My Kodi was a problem. When checking my sync i was getting full sync of 12mb down and 1mb up. Attenuation was Noise were spot on.

So no idea what it was, exchange congesstion?

It could be Exchange-related, we'll need to keep an eye on it to see if it congestion-related or damage or an issue with the hardware.

If it happens again, we'll need to get you to test with a Test Account.
 
Yes, we cannot pick up nor replicate any issues.

I've built a utility that does trace routes over time for me to at least have historical data
tracert www.afrihost.com
Note IP 196.10.140.7
According to http://www.speedguide.net/ip/196.10.140.7 this is MWEB

Yesterday 3pm
Code:
Tracing route to www.afrihost.com [104.20.31.244]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3    24 ms    21 ms    22 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    22 ms    21 ms    22 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5    21 ms    21 ms    22 ms  africainx.ixp.capetown [196.10.140.7] 
  6    37 ms    37 ms    37 ms  CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za.africainx.net [41.84.13.228] 
  7    37 ms    39 ms    67 ms  41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59] 
  8    37 ms    38 ms    38 ms  104.20.31.244 

Trace complete.

Yesterday 9:30pm
Code:
Tracing route to www.afrihost.com [104.20.30.244]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3    24 ms    22 ms    33 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    61 ms    64 ms    71 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5   119 ms   250 ms   108 ms  africainx.ixp.capetown [196.10.140.7] 
  6    62 ms    54 ms    53 ms  CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za.africainx.net [41.84.13.228] 
  7    55 ms    57 ms    48 ms  41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59] 
  8    71 ms    71 ms    68 ms  104.20.30.244 

Trace complete.

Yesterday 9:45pm
Code:
Tracing route to www.afrihost.com [104.20.31.244]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3    22 ms    25 ms    21 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    86 ms    81 ms    81 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5    94 ms   100 ms   103 ms  africainx.ixp.capetown [196.10.140.7] 
  6    86 ms    96 ms    94 ms  CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za.africainx.net [41.84.13.228] 
  7   103 ms   109 ms   107 ms  41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59] 
  8    37 ms    37 ms    37 ms  104.20.31.244 

Trace complete.

tracert www.exa.co.za
Note IP 196.10.140.21
According to http://www.speedguide.net/ip/196.10.140.21 this is MWEB

Yesterday 3pm
Code:
Tracing route to www.exa.co.za [197.221.2.20]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3    22 ms    21 ms    22 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    21 ms    20 ms    20 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5    30 ms    29 ms    26 ms  hetzner2.ixp.capetown [196.10.140.21] 
  6    21 ms    23 ms    22 ms  41.204.206.38 
  7     *       22 ms    23 ms  www20.cpt1.host-h.net [197.221.2.20] 

Trace complete.

Yesterday 9:45pm:
Code:
Tracing route to www.exa.co.za [197.221.2.20]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3    23 ms    21 ms    21 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4   128 ms   158 ms   123 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5   130 ms   126 ms   128 ms  hetzner2.ixp.capetown [196.10.140.21] 
  6    31 ms    29 ms    21 ms  41.204.206.38 
  7    28 ms    26 ms    26 ms  www20.cpt1.host-h.net [197.221.2.20] 

Trace complete.


tracert www.mweb.co.za
Note IP 196.10.140.145
According to http://www.speedguide.net/ip/196.10.140.145 this is MWEB
Note IP 197.84.7.33
According to http://www.speedguide.net/ip/197.84.7.33 this is MWEB

Yesterday 3pm
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     *        *        *     Request timed out.
  3    24 ms    21 ms    21 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    23 ms    22 ms    21 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5    22 ms    22 ms    22 ms  optinet.ixp.capetown [196.10.140.145] 
  6    23 ms    27 ms    23 ms  bu-ether1.cpt-p-1.optinet.net [197.84.7.33] 
  7    23 ms    21 ms    23 ms  vl11.cpt-hscore-1.optinet.net [197.84.5.238] 
  8    34 ms    26 ms    26 ms  196.28.178.66 
  9    23 ms    22 ms    22 ms  cte-core-sw2.vwol.net [196.41.144.35] 
 10    26 ms    21 ms    24 ms  www.mweb.co.za [196.2.63.110] 

Trace complete.

Yesterday 8:30pm
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     *        *        *     Request timed out.
  3    22 ms    31 ms    23 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    96 ms    95 ms    99 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5   113 ms   107 ms    99 ms  optinet.ixp.capetown [196.10.140.145] 
  6    97 ms    94 ms    94 ms  bu-ether1.cpt-p-1.optinet.net [197.84.7.33] 
  7   116 ms   118 ms   234 ms  vl11.cpt-hscore-1.optinet.net [197.84.5.238] 
  8   125 ms   119 ms   123 ms  196.28.178.66 
  9   124 ms   123 ms   123 ms  cte-core-sw2.vwol.net [196.41.144.35] 
 10    22 ms    22 ms    22 ms  www.mweb.co.za [196.2.63.110] 

Trace complete.

Yesterday 9:30pm
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     *        *        *     Request timed out.
  3    30 ms    22 ms    24 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    26 ms    26 ms    29 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5   120 ms   124 ms   135 ms  optinet.ixp.capetown [196.10.140.145] 
  6    86 ms    84 ms   222 ms  bu-ether1.cpt-p-1.optinet.net [197.84.7.33] 
  7    46 ms    45 ms    51 ms  vl11.cpt-hscore-1.optinet.net [197.84.5.238] 
  8   172 ms   150 ms   163 ms  196.28.178.66 
  9    22 ms    22 ms    23 ms  cte-core-sw2.vwol.net [196.41.144.35] 
 10    29 ms    22 ms    23 ms  www.mweb.co.za [196.2.63.110] 

Trace complete.
 
Last speedtest i did after resetting router was 9.5mb down and 0.89mb up. ping was 25, but was spiking around 25 and 1000ms.

Then after 9:30pm or so last night was getting full HD on youtube no problem. then went to bed. My Kodi was a problem. When checking my sync i was getting full sync of 12mb down and 1mb up. Attenuation was Noise were spot on.

So no idea what it was, exchange congesstion?

please dont use kodi to test anything speed related or streaming related. Use Netflix, or Youtube, but not Kodi.
 
I've built a utility that does trace routes over time for me to at least have historical data
-snip

Cheers for those tests. Have been unable to play csgo in the evenings on my Afrihost account for around TWO MONTHS...ping hovers around 100ms and I think most of the servers route through mweb. The odd servers that don't aren't effected..
 
I've built a utility that does trace routes over time for me to at least have historical data
tracert www.afrihost.com
Note IP 196.10.140.7
According to http://www.speedguide.net/ip/196.10.140.7 this is MWEB

Yesterday 3pm
Code:
Tracing route to www.afrihost.com [104.20.31.244]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3    24 ms    21 ms    22 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    22 ms    21 ms    22 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5    21 ms    21 ms    22 ms  africainx.ixp.capetown [196.10.140.7] 
  6    37 ms    37 ms    37 ms  CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za.africainx.net [41.84.13.228] 
  7    37 ms    39 ms    67 ms  41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59] 
  8    37 ms    38 ms    38 ms  104.20.31.244 

Trace complete.

Yesterday 9:30pm
Code:
Tracing route to www.afrihost.com [104.20.30.244]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3    24 ms    22 ms    33 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    61 ms    64 ms    71 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5   119 ms   250 ms   108 ms  africainx.ixp.capetown [196.10.140.7] 
  6    62 ms    54 ms    53 ms  CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za.africainx.net [41.84.13.228] 
  7    55 ms    57 ms    48 ms  41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59] 
  8    71 ms    71 ms    68 ms  104.20.30.244 

Trace complete.

Yesterday 9:45pm
Code:
Tracing route to www.afrihost.com [104.20.31.244]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3    22 ms    25 ms    21 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    86 ms    81 ms    81 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5    94 ms   100 ms   103 ms  africainx.ixp.capetown [196.10.140.7] 
  6    86 ms    96 ms    94 ms  CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za.africainx.net [41.84.13.228] 
  7   103 ms   109 ms   107 ms  41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59] 
  8    37 ms    37 ms    37 ms  104.20.31.244 

Trace complete.

tracert www.exa.co.za
Note IP 196.10.140.21
According to http://www.speedguide.net/ip/196.10.140.21 this is MWEB

Yesterday 3pm
Code:
Tracing route to www.exa.co.za [197.221.2.20]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3    22 ms    21 ms    22 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    21 ms    20 ms    20 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5    30 ms    29 ms    26 ms  hetzner2.ixp.capetown [196.10.140.21] 
  6    21 ms    23 ms    22 ms  41.204.206.38 
  7     *       22 ms    23 ms  www20.cpt1.host-h.net [197.221.2.20] 

Trace complete.

Yesterday 9:45pm:
Code:
Tracing route to www.exa.co.za [197.221.2.20]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3    23 ms    21 ms    21 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4   128 ms   158 ms   123 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5   130 ms   126 ms   128 ms  hetzner2.ixp.capetown [196.10.140.21] 
  6    31 ms    29 ms    21 ms  41.204.206.38 
  7    28 ms    26 ms    26 ms  www20.cpt1.host-h.net [197.221.2.20] 

Trace complete.


tracert www.mweb.co.za
Note IP 196.10.140.145
According to http://www.speedguide.net/ip/196.10.140.145 this is MWEB
Note IP 197.84.7.33
According to http://www.speedguide.net/ip/197.84.7.33 this is MWEB

Yesterday 3pm
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     *        *        *     Request timed out.
  3    24 ms    21 ms    21 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    23 ms    22 ms    21 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5    22 ms    22 ms    22 ms  optinet.ixp.capetown [196.10.140.145] 
  6    23 ms    27 ms    23 ms  bu-ether1.cpt-p-1.optinet.net [197.84.7.33] 
  7    23 ms    21 ms    23 ms  vl11.cpt-hscore-1.optinet.net [197.84.5.238] 
  8    34 ms    26 ms    26 ms  196.28.178.66 
  9    23 ms    22 ms    22 ms  cte-core-sw2.vwol.net [196.41.144.35] 
 10    26 ms    21 ms    24 ms  www.mweb.co.za [196.2.63.110] 

Trace complete.

Yesterday 8:30pm
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     *        *        *     Request timed out.
  3    22 ms    31 ms    23 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    96 ms    95 ms    99 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5   113 ms   107 ms    99 ms  optinet.ixp.capetown [196.10.140.145] 
  6    97 ms    94 ms    94 ms  bu-ether1.cpt-p-1.optinet.net [197.84.7.33] 
  7   116 ms   118 ms   234 ms  vl11.cpt-hscore-1.optinet.net [197.84.5.238] 
  8   125 ms   119 ms   123 ms  196.28.178.66 
  9   124 ms   123 ms   123 ms  cte-core-sw2.vwol.net [196.41.144.35] 
 10    22 ms    22 ms    22 ms  www.mweb.co.za [196.2.63.110] 

Trace complete.

Yesterday 9:30pm
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     *        *        *     Request timed out.
  3    30 ms    22 ms    24 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    26 ms    26 ms    29 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5   120 ms   124 ms   135 ms  optinet.ixp.capetown [196.10.140.145] 
  6    86 ms    84 ms   222 ms  bu-ether1.cpt-p-1.optinet.net [197.84.7.33] 
  7    46 ms    45 ms    51 ms  vl11.cpt-hscore-1.optinet.net [197.84.5.238] 
  8   172 ms   150 ms   163 ms  196.28.178.66 
  9    22 ms    22 ms    23 ms  cte-core-sw2.vwol.net [196.41.144.35] 
 10    29 ms    22 ms    23 ms  www.mweb.co.za [196.2.63.110] 

Trace complete.

Before you blame AH have a look at this, those traceroutes mean nothing actually. The fact that you see those results at night, could also point to congestion on that particular "MWEB" peering link , or it could just mean them dropping ICMP packets to prioritize real time traffic. You don't see these results on other ISP's, because they don't use the same upstream providers, peers or traffic prioritization protocols as Afrihost does.

https://www.freeccnaworkbook.com/blog/ccna/ping-vs-traceroute-vs-pathping
 
Before you blame AH have a look at this, those traceroutes mean nothing actually. The fact that you see those results at night, could also point to congestion on that particular "MWEB" peering link , or it could just mean them dropping ICMP packets to prioritize real time traffic. You don't see these results on other ISP's, because they don't use the same upstream providers, peers or traffic prioritization protocols as Afrihost does.

https://www.freeccnaworkbook.com/blog/ccna/ping-vs-traceroute-vs-pathping

Even if it isn't Afrihost's problem directly, they still need to look into it, especially seeing as it only happens when using their network.
 
Before you blame AH have a look at this, those traceroutes mean nothing actually. The fact that you see those results at night, could also point to congestion on that particular "MWEB" peering link , or it could just mean them dropping ICMP packets to prioritize real time traffic. You don't see these results on other ISP's, because they don't use the same upstream providers, peers or traffic prioritization protocols as Afrihost does.

https://www.freeccnaworkbook.com/blog/ccna/ping-vs-traceroute-vs-pathping

Currently I'm not blaming anybody, yet ;) If anything I'm starting to point the finger at MWEB.

What is clear is that I'm one of the people in the south struggling in the early evening with YouTube streaming and overall latency issues. Also top end throughput also suffers during this time.

Afrihost is saying they can't reproduce the issue, thus I'm giving the info I have to try and solve this.

I've checked the general experience with other Afrihost users (friends) living in other parts of Cape Town. They all have the same issue. So definitely not exchange related.

Somebody earlier in the thread mentioned that some Afrihost traffic depends on MWEB. Thus looking at my results MWEB looks like the common denominator.
 
Even if it isn't Afrihost's problem directly, they still need to look into it, especially seeing as it only happens when using their network.

If this is indeed MWEB screwing up, don't you think everybody on AH network would have the same issue ?:)
 
I've built a utility that does trace routes over time for me to at least have historical data
-megasnip

Trace complete.[/CODE]

Very interesting results here, thanks for setting this up and posting them :)
I've made a note to test things on my end this evening too - would you mind testing some pings to the hops that list higher than normal latency this evening?
 
Cheers for those tests. Have been unable to play csgo in the evenings on my Afrihost account for around TWO MONTHS...ping hovers around 100ms and I think most of the servers route through mweb. The odd servers that don't aren't effected..

Sorry to hear that, do you see similar results to what's been posted by standerr?
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X