Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
AfriGuy said:
I don't think that snippet gives the impression we're simply giving up? We're simply requesting Wireshark dumps to better trace how the traffic works from your connection.

The traceroutes you've posted here also seem to reflect an issue with various time-outs.
Either way, please keep our Critical Care team posted to see this through.
Click to expand...

It takes you 17 days to ask for Wireshark dumps.
 
AfriGuy said:
Don't think it's fair to comment on the query here without a good history.
We've run through multiple troubleshooting options.
Click to expand...

Next time you have an "unusual" problem like this, maybe start with wireshark dump.
 
wingnut771 said:
Next time you have an "unusual" problem like this, maybe start with wireshark dump.
Click to expand...

If our team felt a traffic dump were required off the bat then it would have been requested then, in this case it wasn't.
 
Last edited:
We're out of here - our Social will return on Thursday morning.
In the mean time, if there's anything urgent please bring this up directly with our Support team so we can assist.

Thanks guys.
 
Well I never, it looks like the Mweb Peering problem in KZN has been fixed, I honestly can't believe it. Will see tomorrow night if it is too good to be true.
 
Hummercellc said:
Can you please test if you can access mweb.co.za, looks like it has been fixed? A freaking miracle.
Click to expand...

Not working for me, usual evening story. Issues streaming on YouTube. But I bet if I drop my PPPoE connection, it will come right. Something I should not have to do on a daily basis.

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.254
2 * * * Request timed out.
3 20 ms 19 ms 19 ms dbn-up1.ip.adsl.co.za [169.1.5.161]
4 56 ms 55 ms 56 ms dbn-up2.ip.adsl.co.za [169.1.5.162]
5 19 ms 19 ms 18 ms 169-1-5-208.ip.afrihost.co.za [169.1.5.208]
6 19 ms 19 ms 19 ms optinet.ixp.durban [196.10.141.75]
7 * * * Request timed out.
8 * * * Request timed out.

Exactly the same tracert result. Dying somewhere in Optinet's network....
 
Afrihost local latency is crap beyond bras tonight:
Pinging cpt-rx2.ip.adsl.co.za [169.1.5.82] with 32 bytes of data:
Reply from 169.1.5.82: bytes=32 time=27ms TTL=59
Reply from 169.1.5.82: bytes=32 time=74ms TTL=59
Reply from 169.1.5.82: bytes=32 time=94ms TTL=59
Reply from 169.1.5.82: bytes=32 time=122ms TTL=59
Request timed out.
Reply from 169.1.5.82: bytes=32 time=27ms TTL=59
Reply from 169.1.5.82: bytes=32 time=23ms TTL=59
Reply from 169.1.5.82: bytes=32 time=90ms TTL=59
Reply from 169.1.5.82: bytes=32 time=106ms TTL=59
Reply from 169.1.5.82: bytes=32 time=119ms TTL=59
Reply from 169.1.5.82: bytes=32 time=123ms TTL=59
Reply from 169.1.5.82: bytes=32 time=119ms TTL=59
Reply from 169.1.5.82: bytes=32 time=104ms TTL=59
Reply from 169.1.5.82: bytes=32 time=112ms TTL=59
Reply from 169.1.5.82: bytes=32 time=117ms TTL=59
Reply from 169.1.5.82: bytes=32 time=133ms TTL=59
Reply from 169.1.5.82: bytes=32 time=96ms TTL=59
Reply from 169.1.5.82: bytes=32 time=99ms TTL=59

Ping statistics for 169.1.5.82:
Packets: Sent = 18, Received = 17, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 133ms, Average = 93ms

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 18, Received = 18, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 13ms, Average = 11ms
 
My Afrihost performing great this evening. Streaming 1080p while downloading some stuff in the background.

Pta, 10meg capped

ImageUploadedByMyBroadband1470166994.417577.jpg
 
AfriGuy said:
Did you manage to grab similar tests to what you did before, including bras.afrihost.com?
I've got your PM - have passed on the details.

I need to stress that our team are actively working on it. There's no feedback because our team are still running through various scenarios to pin point the cause.
Click to expand...

Just sent you updated tests. bras is included in the spreadsheet.
 
Getting 280ms in LoL EUW tonight but everything else is fine, strange.
Code: 
Tracing route to mybroadband.co.za [104.20.72.110]
over a maximum of 30 hops:

  1     1 ms     2 ms   1 ms  ARCHER_D5 [192.168.0.1]
  2     2 ms     3 ms     1 ms  HOME [192.168.1.1]
  3     *        *        *     Request timed out.
  4    27 ms    24 ms    24 ms  cpt-up1.ip.adsl.co.za [169.1.5.105]
  5    25 ms    25 ms    24 ms  cpt-up2.ip.adsl.co.za [169.1.5.106]
  6    24 ms    55 ms    37 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  7    23 ms    64 ms    24 ms  africainx.ixp.capetown [196.10.140.7]
  8    74 ms    79 ms    67 ms  CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za.africainx.net [41.84.13.228]
  9    95 ms    98 ms    99 ms  41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59]
 10    41 ms    40 ms    41 ms  104.20.72.110

Trace complete.

---------------------

Tracing route to vienna.at [194.183.128.94]
over a maximum of 30 hops:

  1     1 ms     1 ms     2 ms  ARCHER_D5 [192.168.0.1]
  2     2 ms     1 ms     1 ms  HOME [192.168.1.1]
  3     *        *        *     Request timed out.
  4    25 ms    24 ms    24 ms  cpt-up1.ip.adsl.co.za [169.1.5.105]
  5    25 ms    25 ms    25 ms  cpt-in1.ip.adsl.co.za [169.1.5.118]
  6    32 ms    24 ms    22 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  7    25 ms    26 ms    25 ms  41.164.52.40
  8    25 ms     *       41 ms  if-ae-7-0.tcore1.KLT-Cape-Town.as6453.net [41.206.164.53]
  9   174 ms   173 ms   173 ms  if-ae-5-40.tcore2.PV9-Lisbon.as6453.net [80.231.159.89]
 10   173 ms   174 ms   174 ms  if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
 11   267 ms   273 ms   287 ms  if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
 12   166 ms   168 ms   169 ms  if-ae-19-2.tcore2.L78-London.as6453.net [80.231.138.22]
 13   167 ms   182 ms   168 ms  if-ae-15-2.tcore2.LDN-London.as6453.net [80.231.131.118]
 14   223 ms   209 ms     *     ldn-b5-link.telia.net [62.115.9.173]
 15   167 ms   166 ms   168 ms  ldn-bb3-link.telia.net [80.91.246.144]
 16   200 ms   197 ms   309 ms  prs-bb3-link.telia.net [62.115.134.104]
 17   193 ms   192 ms   195 ms  zch-b2-link.telia.net [62.115.135.121]
 18   299 ms   299 ms   283 ms  russmedia-ic-317231-zch-b2.c.telia.net [62.115.146.227]
 19   203 ms   202 ms   203 ms  194-208-001-038.tele.net [194.208.1.38]
 20   205 ms   204 ms   205 ms  gi0-0-1-75-asr1k-2-swz1.net.tele.net [194.183.142.174]
 21   201 ms   201 ms   201 ms  service.tele.net [194.183.128.94]

Trace complete.
Speedtest isn't that great though.
local.png
High latency considering that's normally at ~27ms or so.
 
Last edited:
When is going to be solved? Switching over to Telkom and all is fine.
Cannot do any Android updates.

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   132 ms   123 ms   116 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    34 ms    34 ms    35 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5    73 ms    68 ms    68 ms  africainx.ixp.capetown [196.10.140.7] 
  6    37 ms    38 ms    38 ms  CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za.africainx.net [41.84.13.228] 
  7    38 ms    38 ms    40 ms  41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59] 
  8   120 ms   125 ms   126 ms  104.20.30.244 

Trace complete.

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   241 ms    77 ms    55 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    66 ms    66 ms    68 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5    68 ms    73 ms    76 ms  optinet.ixp.capetown [196.10.140.145] 
  6    93 ms    90 ms    95 ms  te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2] 
  7   126 ms   128 ms   129 ms  vl12.cpt-hscore-2.optinet.net [197.84.5.254] 
  8    92 ms    87 ms    85 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   114 ms   122 ms     *     OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 11    57 ms    43 ms    46 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 12   119 ms   115 ms   110 ms  41-86-110-200.mweb.co.za [41.86.110.200] 

Trace complete.

bras no issue

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

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2    20 ms    21 ms    20 ms  155.239.255.250 

Trace complete.
 
standerr said:
When is going to be solved? Switching over to Telkom and all is fine.
Cannot do any Android updates.

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   132 ms   123 ms   116 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    34 ms    34 ms    35 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5    73 ms    68 ms    68 ms  africainx.ixp.capetown [196.10.140.7] 
  6    37 ms    38 ms    38 ms  CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za.africainx.net [41.84.13.228] 
  7    38 ms    38 ms    40 ms  41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59] 
  8   120 ms   125 ms   126 ms  104.20.30.244 

Trace complete.

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   241 ms    77 ms    55 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    66 ms    66 ms    68 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5    68 ms    73 ms    76 ms  optinet.ixp.capetown [196.10.140.145] 
  6    93 ms    90 ms    95 ms  te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2] 
  7   126 ms   128 ms   129 ms  vl12.cpt-hscore-2.optinet.net [197.84.5.254] 
  8    92 ms    87 ms    85 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   114 ms   122 ms     *     OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 11    57 ms    43 ms    46 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 12   119 ms   115 ms   110 ms  41-86-110-200.mweb.co.za [41.86.110.200] 

Trace complete.

bras no issue

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

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2    20 ms    21 ms    20 ms  155.239.255.250 

Trace complete.
Click to expand...
YouTube running at a whole 129kbps here, normally see 19mbps.
 
AfriGuy said:
Sounds like there could be a line/ exchange related issue here if a port reset is needed to normalise the experience for you. If your latency to bras.afrihost.com it'll indicate some kind of issue/ congestion there.
Click to expand...
"There" meaning the exchange?

I'm kinda flabbergasted that no-one from (telephone) support has contacted me as yet. I logged the latest incident around 22h38 on Monday. They had the full business day on Tuesday. Not hearing from them yet is poor form!

Here's the lastest pingtrace to www.afrihost.com
Note the latency issues from Hop 3 onward.

Code: 
Target Name: www.afrihost.com
         IP: 104.20.30.244
  Date/Time: 03/08/2016 20:30:42 to 03/08/2016 21:11:09

Hop Sent Err   PL% Min  Max Avg  Host Name / [IP]
 1   950   9   0.9   0 1853   9  router.asus.com [192.168.1.1]
 2   951 951 100.0   0    0   0   [-]
[B] 3   950 308  32.4  22 2058 455  cpt-up1.ip.adsl.co.za [169.1.5.105]
[/B] 4   950  27   2.8  29 2000 507  cpt-in1.ip.adsl.co.za [169.1.5.118]
 5   950  29   3.1  19 1743 397  cpt-net1.ip.adsl.co.za [169.1.5.128]
 6   950  23   2.4  20 1720 402  africainx.ixp.capetown [196.10.140.7]
 7   950  40   4.2  39 1772 523  CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za.africainx.net [41.84.13.228]
 8   950  46   4.8  51 1723 518  41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59]
 9   950  45   4.7  38 2162 460  [104.20.30.244]

Here's a pingtest to bras.afrihost.com. So the problem isn't showing up on bras.
Code: 
Target Name: bras.afrihost.com
         IP: 155.239.255.250
  Date/Time: 03/08/2016 21:11:30 to 03/08/2016 21:15:26

Hop Sent Err PL% Min Max Avg  Host Name / [IP]
 1    95   0 0.0   0   2   0  router.asus.com [192.168.1.1]
 2    95   0 0.0  18  93  30  [155.239.255.250]

AfriGuy said:
What is the experience like when switching to another ISP to test?
Click to expand...
Dunno. Don't deal with other ISP's.
I'm going to say this with the greatest of respect so please take it in context of someone who lived the horror show that was AH pre the new network and to whom such sounds like Deja Vu - it's akin to LG asking the customer to run their backup Bosch washer to see if the washing issues experienced are the same. Please please don't ask me for that :S.

Let's see what the situation is -
a) Telkom have had issues in the past two going on three weeks - these are documented
b) The symptoms experienced during those periods - high packet loss and latency at Hop 3 (specifically)
c) The current symptoms are the same - high packet loss and latency
d) Nothing has changed on my end so if AH is happy that their network is performing as expected the issue lies with Telkom.
e) Please do get Telkom to resolve this.

After the many interactions I've had with AH, and my requests for escalation, surely this should have been escalated already? Would have been nice to have had someone at AH (tele helpdesk) contact me already.

Regards,
SD.
 
Last edited:
All I know is that Afrihost is playing with loosing customers again.

Also a customer having gone through the hell of Afrihost at its worst. Also remembering how we were promised they will give back to the loyal customers, going through the network pain, when the time is right. As a business customer I've not received a single cent in refund since the new network was rolled out. So all lies it seems.

Now we're here again. According to the reports "our" network is fine. It's upstream where the issue lies. Well then why is everything fine when you switch over to a Telkom account. No issues.

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    41 ms    29 ms    30 ms  ipc-1-up.south.dsl.telkomsa.net [105.226.0.6] 
  4    26 ms    25 ms    21 ms  ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13] 
  5    25 ms    25 ms    25 ms  blv-pr-02-be200-vl1.net.telkomsa.net [105.226.0.54] 
  6    21 ms    23 ms    38 ms  ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138] 
  7    29 ms    53 ms    58 ms  optinet.ixp.capetown [196.10.140.15] 
  8    33 ms    23 ms    31 ms  te0-0-0-1.cpt-p-1.optinet.net [197.84.7.1] 
  9    26 ms    33 ms    58 ms  vl12.cpt-hscore-2.optinet.net [197.84.5.254] 
 10    75 ms    75 ms    69 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70] 
 11    27 ms    23 ms    24 ms  gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166] 
 12    24 ms    23 ms    25 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 13    27 ms    39 ms    33 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 14    24 ms    24 ms    24 ms  41-86-110-200.mweb.co.za [41.86.110.200] 

Trace complete.

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   105 ms   217 ms    73 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4   129 ms   122 ms   116 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5    54 ms    57 ms    65 ms  optinet.ixp.capetown [196.10.140.145] 
  6    83 ms    82 ms    82 ms  te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2] 
  7   110 ms   117 ms   114 ms  vl12.cpt-hscore-2.optinet.net [197.84.5.254] 
  8    76 ms    73 ms    72 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70] 
  9    26 ms    22 ms    22 ms  gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166] 
 10   102 ms    59 ms    37 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 11   129 ms   125 ms   120 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 12    50 ms    55 ms    62 ms  41-86-110-200.mweb.co.za [41.86.110.200] 

Trace complete.

If you look at those results you'll spot the same hops being repeated with Telkom and Afrihost, but you'll notice that on an Afrihost account those same hops have high latency.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X