Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
Yep still issue for me too. So frustrating that we're not getting any real feedback. We're looking into it.....

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   106 ms   103 ms   113 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    24 ms    21 ms    20 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5    26 ms    21 ms    21 ms  africainx.ixp.capetown [196.10.140.7] 
  6    39 ms    37 ms    51 ms  CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za.africainx.net [41.84.13.228] 
  7    37 ms    38 ms    38 ms  41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59] 
  8   125 ms   120 ms   118 ms  104.20.31.244 

Trace complete.

cpt-rx2.ip.adsl.co.za seems to be issue when doing to tracert to www.afrihost.com
Pinging it fluctuates widely

Code: 
Pinging 169.1.5.82 with 32 bytes of data:
Reply from 169.1.5.82: bytes=32 time=105ms TTL=60
Reply from 169.1.5.82: bytes=32 time=99ms TTL=60
Reply from 169.1.5.82: bytes=32 time=115ms TTL=60
Reply from 169.1.5.82: bytes=32 time=67ms TTL=60
Reply from 169.1.5.82: bytes=32 time=120ms TTL=60
Reply from 169.1.5.82: bytes=32 time=119ms TTL=60
Reply from 169.1.5.82: bytes=32 time=49ms TTL=60
Reply from 169.1.5.82: bytes=32 time=77ms TTL=60
Reply from 169.1.5.82: bytes=32 time=79ms TTL=60
Reply from 169.1.5.82: bytes=32 time=90ms TTL=60
Reply from 169.1.5.82: bytes=32 time=113ms TTL=60
Reply from 169.1.5.82: bytes=32 time=102ms TTL=60
Reply from 169.1.5.82: bytes=32 time=71ms TTL=60
Reply from 169.1.5.82: bytes=32 time=90ms TTL=60
Reply from 169.1.5.82: bytes=32 time=96ms TTL=60
Reply from 169.1.5.82: bytes=32 time=82ms TTL=60
Reply from 169.1.5.82: bytes=32 time=98ms TTL=60
Reply from 169.1.5.82: bytes=32 time=112ms TTL=60
Reply from 169.1.5.82: bytes=32 time=113ms TTL=60
Reply from 169.1.5.82: bytes=32 time=108ms TTL=60

Code: 
Tracing route to www.mybroadband.co.za [104.20.71.110]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3   121 ms   122 ms   123 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    22 ms    25 ms    22 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5    25 ms    23 ms    21 ms  africainx.ixp.capetown [196.10.140.7] 
  6    38 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    58 ms    38 ms    38 ms  41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59] 
  8   155 ms   148 ms   258 ms  104.20.71.110 

Trace complete.

And as usual the website says nothing about acknowledging that there is an issue. All is green, but obviously there a quite a few people struggling with this.
 
standerr said:
Yep still issue for me too. So frustrating that we're not getting any real feedback. We're looking into it.....

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   106 ms   103 ms   113 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    24 ms    21 ms    20 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5    26 ms    21 ms    21 ms  africainx.ixp.capetown [196.10.140.7] 
  6    39 ms    37 ms    51 ms  CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za.africainx.net [41.84.13.228] 
  7    37 ms    38 ms    38 ms  41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59] 
  8   125 ms   120 ms   118 ms  104.20.31.244 

Trace complete.

cpt-rx2.ip.adsl.co.za seems to be issue when doing to tracert to www.afrihost.com
Pinging it fluctuates widely

Code: 
Pinging 169.1.5.82 with 32 bytes of data:
Reply from 169.1.5.82: bytes=32 time=105ms TTL=60
Reply from 169.1.5.82: bytes=32 time=99ms TTL=60
Reply from 169.1.5.82: bytes=32 time=115ms TTL=60
Reply from 169.1.5.82: bytes=32 time=67ms TTL=60
Reply from 169.1.5.82: bytes=32 time=120ms TTL=60
Reply from 169.1.5.82: bytes=32 time=119ms TTL=60
Reply from 169.1.5.82: bytes=32 time=49ms TTL=60
Reply from 169.1.5.82: bytes=32 time=77ms TTL=60
Reply from 169.1.5.82: bytes=32 time=79ms TTL=60
Reply from 169.1.5.82: bytes=32 time=90ms TTL=60
Reply from 169.1.5.82: bytes=32 time=113ms TTL=60
Reply from 169.1.5.82: bytes=32 time=102ms TTL=60
Reply from 169.1.5.82: bytes=32 time=71ms TTL=60
Reply from 169.1.5.82: bytes=32 time=90ms TTL=60
Reply from 169.1.5.82: bytes=32 time=96ms TTL=60
Reply from 169.1.5.82: bytes=32 time=82ms TTL=60
Reply from 169.1.5.82: bytes=32 time=98ms TTL=60
Reply from 169.1.5.82: bytes=32 time=112ms TTL=60
Reply from 169.1.5.82: bytes=32 time=113ms TTL=60
Reply from 169.1.5.82: bytes=32 time=108ms TTL=60

Code: 
Tracing route to www.mybroadband.co.za [104.20.71.110]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3   121 ms   122 ms   123 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    22 ms    25 ms    22 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5    25 ms    23 ms    21 ms  africainx.ixp.capetown [196.10.140.7] 
  6    38 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    58 ms    38 ms    38 ms  41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59] 
  8   155 ms   148 ms   258 ms  104.20.71.110 

Trace complete.

And as usual the website says nothing about acknowledging that there is an issue. All is green, but obviously there a quite a few people struggling with this.
Click to expand...
'critical care' told me this is a isolated case, only I seem to be affected. Well, pure lies it would seem. What do we have to do to get this fixed?
 
Hummercellc said:
'critical care' told me this is a isolated case, only I seem to be affected. Well, pure lies it would seem. What do we have to do to get this fixed?
Click to expand...

Even CPT is congested at night... Each and every night, some additional 150ms+ latency on the network. Use another ISP, latency back to normal.

Seems AH is running out of bandwidth, again... Same ***** different story it seems.
 
savage said:
Even CPT is congested at night... Each and every night, some additional 150ms+ latency on the network. Use another ISP, latency back to normal.

Seems AH is running out of bandwidth, again... Same ***** different story it seems.
Click to expand...
If things play out like last time with MTN, this could take a while.
Deny, deny, deny, acknowledge, apologise, long break, move backbone for a forth time.

EDIT: you would have thought Afrihost would have increased capacity with the latest IPC price cuts? Clearly not.
 
Last edited:
[Major???] Issues in Cape Town

Hiya AfriPeeps,

Been a while since I've had cause to resort to seeking support here on the Forum - sadly the problem appears outside the ability of the telephone support team to resolve.

I have a 20mbps VDSL line in Century City, Cape Town.
Two weeks ago my local latency [to afrihost.com] shot up to 1000ms with signifciant packet loss - so unusable.
I called the support line and spoke with a consultant who informed me that there was a major Telkom outage in Milnerton. Thankfully the problem was rectified the next day... only it wasn't. It recurred a week later :(. This time around the consultant found no work being undertaken by Telkom. He did a port recreate and this corrected the latency and packet loss... well for a couple of days at least - it didn't last. A few days later I had to call support again with the same issue - latency and packet loss all the way from hop 3. I referred the consultant to the prior calls. This time I was informed that there was a node down in Milnerton. No ETA was available. The consultant logged a fault with Telkom in an attempt to keep me updated - I received no updates from Telkom. The problem appeared to have been rectified when I checked a couple of days later, but again it didn't last. I made the 5th call in two weeks this weekend. There was again no sign of Telkom work being undertaken. The line again tested clean. A port recreate again stabilized... BUT IT'S BACK... :mad:

I need someone to get to the root-cause and rectify this. It's been two weeks and six incidents later.
I've scanned the forums and note posts with similar experiences. This worries me greatly and I've lived through the pre-AfriGreen days. :erm:

Here's the latest - latency is not as horrendous as the last incidents however there's packet loss and streaming is a mess - buffering everything at the moment.

Code: 
Target Name: www.afrihost.com
         IP: 104.20.31.244
  Date/Time: 01/08/2016 22:04:24 to 01/08/2016 22:21:42

Hop Sent Err   PL% Min Max Avg  Host Name / [IP]
 1   414   0   0.0   0   6   0  router.asus.com [192.168.1.1]
 2   414 414 100.0   0   0   0   [-]
[COLOR="#FF0000"] 3   414  97  23.4  20 232  60  cpt-up1.ip.adsl.co.za [169.1.5.105]
[/COLOR] 4   414  11   2.7  21 263 118  cpt-in1.ip.adsl.co.za [169.1.5.118]
 5   414   0   0.0  19  94  21  cpt-net1.ip.adsl.co.za [169.1.5.128]
 6   414   0   0.0  19 146  23  africainx.ixp.capetown [196.10.140.7]
 7   414   7   1.7  36 269 134  CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za.africainx.net [41.84.13.228]
 8   414   6   1.4  44 285 135  41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59]
 9   414   0   0.0  36  55  37  [104.20.31.244]
 
steel_dog said:
Hiya AfriPeeps,

Been a while since I've had cause to resort to seeking support here on the Forum - sadly the problem appears outside the ability of the telephone support team to resolve.

I have a 20mbps VDSL line in Century City, Cape Town.
Two weeks ago my local latency [to afrihost.com] shot up to 1000ms with signifciant packet loss - so unusable.
I called the support line and spoke with a consultant who informed me that there was a major Telkom outage in Milnerton. Thankfully the problem was rectified the next day... only it wasn't. It recurred a week later :(. This time around the consultant found no work being undertaken by Telkom. He did a port recreate and this corrected the latency and packet loss... well for a couple of days at least - it didn't last. A few days later I had to call support again with the same issue - latency and packet loss all the way from hop 3. I referred the consultant to the prior calls. This time I was informed that there was a node down in Milnerton. No ETA was available. The consultant logged a fault with Telkom in an attempt to keep me updated - I received no updates from Telkom. The problem appeared to have been rectified when I checked a couple of days later, but again it didn't last. I made the 5th call in two weeks this weekend. There was again no sign of Telkom work being undertaken. The line again tested clean. A port recreate again stabilized... BUT IT'S BACK... :mad:

I need someone to get to the root-cause and rectify this. It's been two weeks and six incidents later.
I've scanned the forums and note posts with similar experiences. This worries me greatly and I've lived through the pre-AfriGreen days. :erm:

Here's the latest - latency is not as horrendous as the last incidents however there's packet loss and streaming is a mess - buffering everything at the moment.

Code: 
Target Name: www.afrihost.com
         IP: 104.20.31.244
  Date/Time: 01/08/2016 22:04:24 to 01/08/2016 22:21:42

Hop Sent Err   PL% Min Max Avg  Host Name / [IP]
 1   414   0   0.0   0   6   0  router.asus.com [192.168.1.1]
 2   414 414 100.0   0   0   0   [-]
[COLOR="#FF0000"] 3   414  97  23.4  20 232  60  cpt-up1.ip.adsl.co.za [169.1.5.105]
[/COLOR] 4   414  11   2.7  21 263 118  cpt-in1.ip.adsl.co.za [169.1.5.118]
 5   414   0   0.0  19  94  21  cpt-net1.ip.adsl.co.za [169.1.5.128]
 6   414   0   0.0  19 146  23  africainx.ixp.capetown [196.10.140.7]
 7   414   7   1.7  36 269 134  CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za.africainx.net [41.84.13.228]
 8   414   6   1.4  44 285 135  41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59]
 9   414   0   0.0  36  55  37  [104.20.31.244]
Click to expand...

Sounds like you got some major telkom problems there, in which case, not much one can do but have a little faith :)
 
Masik3R said:
AfriPeeps, the issue still remains :)

-snip
Click to expand...

Doesn't look good :(
Please drop me a PM with your DSL username so I can check things out from there.

EDIT: Nevermind, sifted through my inbox and got your details.
 
Last edited:
tigerminx said:
C'mon guys, stop saying you logging calls and lets start seeing some results. Peering to M-Web is broken once again. This is now dragging on far too long. I have been with Afrihost through all the rough patches. But I think it's time to start looking elsewhere.

-snip


:mad:
Click to expand...

Our team are actively working on this.
Please PM me your DSL username so I can query this directly with our NOC team.
 
standerr said:
Yep still issue for me too. So frustrating that we're not getting any real feedback. We're looking into it.....

-snip

And as usual the website says nothing about acknowledging that there is an issue. All is green, but obviously there a quite a few people struggling with this.
Click to expand...

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.
 
savage said:
Even CPT is congested at night... Each and every night, some additional 150ms+ latency on the network. Use another ISP, latency back to normal.

Seems AH is running out of bandwidth, again... Same ***** different story it seems.
Click to expand...

Definitely no where near that much latency on our end - are there any test results you can post here?
 
steel_dog said:
Hiya AfriPeeps,

Been a while since I've had cause to resort to seeking support here on the Forum - sadly the problem appears outside the ability of the telephone support team to resolve.

I have a 20mbps VDSL line in Century City, Cape Town.
Two weeks ago my local latency [to afrihost.com] shot up to 1000ms with signifciant packet loss - so unusable.
I called the support line and spoke with a consultant who informed me that there was a major Telkom outage in Milnerton. Thankfully the problem was rectified the next day... only it wasn't. It recurred a week later :(. This time around the consultant found no work being undertaken by Telkom. He did a port recreate and this corrected the latency and packet loss... well for a couple of days at least - it didn't last. A few days later I had to call support again with the same issue - latency and packet loss all the way from hop 3. I referred the consultant to the prior calls. This time I was informed that there was a node down in Milnerton. No ETA was available. The consultant logged a fault with Telkom in an attempt to keep me updated - I received no updates from Telkom. The problem appeared to have been rectified when I checked a couple of days later, but again it didn't last. I made the 5th call in two weeks this weekend. There was again no sign of Telkom work being undertaken. The line again tested clean. A port recreate again stabilized... BUT IT'S BACK... :mad:

I need someone to get to the root-cause and rectify this. It's been two weeks and six incidents later.
I've scanned the forums and note posts with similar experiences. This worries me greatly and I've lived through the pre-AfriGreen days. :erm:

Here's the latest - latency is not as horrendous as the last incidents however there's packet loss and streaming is a mess - buffering everything at the moment.

-snip
Click to expand...

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.
What is the experience like when switching to another ISP to test?
 
I barely have access to the internet at the moment, on for 10 seconds and off for 30, I have requested a downgrade back to 10Mbs yesterday, today my internet is even worse than yesterday, I can't understand how it can be this bad totally pathetic from telkom.
 
dj2381 said:
I barely have access to the internet at the moment, on for 10 seconds and off for 30, I have requested a downgrade back to 10Mbs yesterday, today my internet is even worse than yesterday, I can't understand how it can be this bad totally pathetic from telkom.
Click to expand...

Drop me a PM with your line number, I'll see if I can stabilise the line for you.
 
Cape Town East

tracert www.google.com

Tracing route to www.google.com [216.58.223.4]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 12 ms 12 ms 12 ms 169-0-44-1.ip.afrihost.co.za [169.0.44.1]

3 1193 ms * 1185 ms cpt-up1.ip.adsl.co.za [169.1.5.105] :wtf:

4 15 ms 13 ms 13 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 12 ms 13 ms 13 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 15 ms 13 ms 13 ms 41.164.52.40
7 35 ms 34 ms 34 ms 172.18.1.162
8 35 ms 36 ms 35 ms 72.14.194.206
9 35 ms 35 ms 36 ms 72.14.237.239
10 35 ms 36 ms 35 ms jnb01s07-in-f4.1e100.net [216.58.223.4]

Trace complete.
 
DeSLAM said:
Cape Town East

tracert www.google.com

Tracing route to www.google.com [216.58.223.4]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 12 ms 12 ms 12 ms 169-0-44-1.ip.afrihost.co.za [169.0.44.1]

3 1193 ms * 1185 ms cpt-up1.ip.adsl.co.za [169.1.5.105] :wtf:

4 15 ms 13 ms 13 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 12 ms 13 ms 13 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 15 ms 13 ms 13 ms 41.164.52.40
7 35 ms 34 ms 34 ms 172.18.1.162
8 35 ms 36 ms 35 ms 72.14.194.206
9 35 ms 35 ms 36 ms 72.14.237.239
10 35 ms 36 ms 35 ms jnb01s07-in-f4.1e100.net [216.58.223.4]

Trace complete.
Click to expand...

o.0
Not too sure what's happening here. What happens when you ping that hop?

Here are my results.

Code: 
traceroute to google.com (216.58.223.46), 64 hops max, 52 byte packets
 1  router.asus.com (192.168.1.1)  0.641 ms  0.424 ms  0.344 ms
 2  * * *
 3  * cpt-up1.ip.adsl.co.za (169.1.5.105)  13.767 ms  11.812 ms
 4  cpt-in1.ip.adsl.co.za (169.1.5.118)  13.372 ms  12.702 ms  12.021 ms
 5  cpt-net1.ip.adsl.co.za (169.1.5.128)  11.512 ms  11.264 ms  50.918 ms
 6  41.164.52.40 (41.164.52.40)  12.084 ms  12.317 ms  13.097 ms
 7  172.18.1.162 (172.18.1.162)  35.096 ms  32.607 ms  33.103 ms
 8  72.14.194.206 (72.14.194.206)  33.275 ms  34.587 ms  33.856 ms
 9  72.14.239.129 (72.14.239.129)  33.678 ms  34.551 ms  33.421 ms
10  jnb01s08-in-f14.1e100.net (216.58.223.46)  34.180 ms  34.386 ms  34.660 ms

--- 169.1.5.105 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 12.085/12.705/13.691/0.406 ms
 
AfriGuy said:
o.0
Not too sure what's happening here. What happens when you ping that hop?
Click to expand...

Code: 
Pinging 169.1.5.105 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 169.1.5.105:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


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


PS C:\Windows\system32> ping cpt-up1.ip.adsl.co.za

Pinging cpt-up1.ip.adsl.co.za [169.1.5.93] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 169.1.5.93:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
 
Rickster said:
Code: 
Pinging 169.1.5.105 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 169.1.5.105:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


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


PS C:\Windows\system32> ping cpt-up1.ip.adsl.co.za

Pinging cpt-up1.ip.adsl.co.za [169.1.5.93] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 169.1.5.93:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Click to expand...

Not sure if that'll work as you're on JHB.
 
AfriGuy your DNS routing skips (2) ip.afrihost.co.za [169.0.44.1]

169.1.5.105 ping fine at the moment. But when this was happening *** 3 1193 ms * 1185 ms cpt-up1.ip.adsl.co.za [169.1.5.105]

There was basically no internet access.
 
DeSLAM said:
AfriGuy your DNS routing skips (2) ip.afrihost.co.za [169.0.44.1]

169.1.5.105 ping fine at the moment. But when this was happening *** 3 1193 ms * 1185 ms cpt-up1.ip.adsl.co.za [169.1.5.105]

There was basically no internet access.
Click to expand...

It isn't necessarily an indication of a problem, could just be that ICMP isn't a priority that routing equipment at the moment. If there was an issue affecting latency from that hop it would affect hops after that.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X