Afrihost Capped DSL Feedback

Yes so you say. Im asking for a logical explanation to those three posts which date back to January indicating capacity issues that you never responded to.

There weren't any capacity issues in January that I'm aware of. It really would depend on the type of account that was in use during that period. There could have been an issue on the DSL line or on the Exchange. I'm afraid it's going to be difficult to determine that cause now.
 
There weren't any capacity issues in January that I'm aware of. It really would depend on the type of account that was in use during that period. There could have been an issue on the DSL line or on the Exchange. I'm afraid it's going to be difficult to determine that cause now.

OMF I clearly state in each post 20Mbps unshaped capped. Issue on the line or the exchange yet tests run minutes apart using another ISP account tells a different story??

It's clearly there in the post, I'm sure you can see/read it.
 
Last edited:
OMF I clearly state in each post 20Mbps unshaped capped. Issue on the line or the exchange yet tests run minutes apart using another ISP account tells a different story??

It's clearly there in the post, I'm sure you can see/read it.

When it comes to exchange related issues, the switching of ISP accounts is inconclusive until you run with that account for an extended period of time. Please let me now if your experience improves after our upgrades. If you're still battling with your Capped account, we'll know that the cause of your problem is elsewhere.
 
You just lost international? I lost international and local... Looks like KZN has got some or other issue again?
 
KZN ... Issue on Hop 5 (169.1.21.32)

PS C:\WINDOWS\system32> tracert www.afrihost.com

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

1 <1 ms <1 ms <1 ms tew-721brm.lan [192.168.1.1]
2 * * * Request timed out.
3 25 ms 25 ms 24 ms dbn-up2.ip.adsl.co.za [169.1.5.162]
4 25 ms 23 ms 25 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
5 * 172 ms 166 ms 169-1-21-32.ip.afrihost.co.za [169.1.21.32]
6 172 ms 166 ms * cloudflare.ixp.joburg [196.60.8.198]
7 * * * Request timed out.
8 146 ms 146 ms 157 ms 104.20.31.244

Trace complete.
PS C:\WINDOWS\system32> ping 169.1.21.32 -t

Pinging 169.1.21.32 with 32 bytes of data:
Reply from 169.1.21.32: bytes=32 time=122ms TTL=59
Reply from 169.1.21.32: bytes=32 time=122ms TTL=59
Reply from 169.1.21.32: bytes=32 time=122ms TTL=59
Reply from 169.1.21.32: bytes=32 time=121ms TTL=59
Reply from 169.1.21.32: bytes=32 time=123ms TTL=59
Request timed out.
Reply from 169.1.21.32: bytes=32 time=174ms TTL=59
Request timed out.
Reply from 169.1.21.32: bytes=32 time=165ms TTL=59
Reply from 169.1.21.32: bytes=32 time=169ms TTL=59
Reply from 169.1.21.32: bytes=32 time=168ms TTL=59
Reply from 169.1.21.32: bytes=32 time=162ms TTL=59
Reply from 169.1.21.32: bytes=32 time=146ms TTL=59
Reply from 169.1.21.32: bytes=32 time=169ms TTL=59
Reply from 169.1.21.32: bytes=32 time=163ms TTL=59
Reply from 169.1.21.32: bytes=32 time=166ms TTL=59
Request timed out.
Request timed out.
Request timed out.
Reply from 169.1.21.32: bytes=32 time=168ms TTL=59
Reply from 169.1.21.32: bytes=32 time=180ms TTL=59
Reply from 169.1.21.32: bytes=32 time=167ms TTL=59
Reply from 169.1.21.32: bytes=32 time=168ms TTL=59
Request timed out.
Reply from 169.1.21.32: bytes=32 time=165ms TTL=59
Reply from 169.1.21.32: bytes=32 time=171ms TTL=59
Reply from 169.1.21.32: bytes=32 time=162ms TTL=59
Reply from 169.1.21.32: bytes=32 time=177ms TTL=59
Reply from 169.1.21.32: bytes=32 time=172ms TTL=59
Reply from 169.1.21.32: bytes=32 time=165ms TTL=59
Reply from 169.1.21.32: bytes=32 time=170ms TTL=59

Ping statistics for 169.1.21.32:
Packets: Sent = 31, Received = 25, Lost = 6 (19% loss),
Approximate round trip times in milli-seconds:
Minimum = 121ms, Maximum = 180ms, Average = 158ms
Control-C
PS C:\WINDOWS\system32>

I'm so done with ADSL. Signed on to a WISP at home, get a solid 30mb up & down. Will do the same at my office soon!
 
Last edited:
Morning Guys. Our NOC Team have detected an issue with a backhaul link between KZN and Joburg. This is causing intermittent latency issues for clients connecting in Durban and surrounding areas. We've put a notice up on our site. Apologies for any inconvenience that this might cause.
 
Morning Guys. Our NOC Team have detected an issue with a backhaul link between KZN and Joburg. This is causing intermittent latency issues for clients connecting in Durban and surrounding areas. We've put a notice up on our site. Apologies for any inconvenience that this might cause.

I see the routing has been changed but general performance is awful... web pages are not loading properly... 6 hour estimate to download a 7mb file... something is not right.
 
Just had my cap reduced to 100GB and increased my line speed up to 8mbps.
Such a beautiful feeling.

My line speed used to be 4mbps.

I was wondering though, AH did the 8mbps thing on their side before Telkom did, and because of this, I actually reached the 4mbps speed that I was supposed to get while having the 4meg line.

Can this actually be the case?
 
So you only miraculously noticed the spike on the network now...

Please give a reasonable explanation for this issue I reported to you on 15/01.

https://mybroadband.co.za/vb/showth...ack-Part-3?p=18979458&viewfull=1#post18979458

I don't believe any AH rep ever responded to the post.

I see the routing has been changed but general performance is awful... web pages are not loading properly... 6 hour estimate to download a 7mb file... something is not right.

I believe our Team is still working on this, I'll see if I can get an update for our Clients in the East.
 
Just had my cap reduced to 100GB and increased my line speed up to 8mbps.
Such a beautiful feeling.

My line speed used to be 4mbps.

I was wondering though, AH did the 8mbps thing on their side before Telkom did, and because of this, I actually reached the 4mbps speed that I was supposed to get while having the 4meg line.

Can this actually be the case?

My apologies, I'm not sure I follow. :(

4Mbps DSL lines should now sync on 5120Kbps and 8Mbps lines on 8192Kbps. This bit of extra speed is to make sure that you get as close as possible to the speed on offer.
 
Morning Guys. Our NOC Team have detected an issue with a backhaul link between KZN and Joburg. This is causing intermittent latency issues for clients connecting in Durban and surrounding areas. We've put a notice up on our site. Apologies for any inconvenience that this might cause.

Any updates yet @Afrifella?
 
Any updates yet @Afrifella?

I just got an update from our Team, the on-site Team is experiencing a number of delays. They are doing their best to work-around these delays and get everyone's connection running normally again.
 
My apologies, I'm not sure I follow. :(

4Mbps DSL lines should now sync on 5120Kbps and 8Mbps lines on 8192Kbps. This bit of extra speed is to make sure that you get as close as possible to the speed on offer.

This is exactly what I am talking about, but I never really got close to 4mbps speeds when I was on a 4meg line.
Should the same hold true for the 8meg line? Should you not sync it to a bit of a higher speed to get me closer to the 8mbps speed at least?
I'm paying for an 8meg line but getting 6meg line speeds.
 
This is exactly what I am talking about, but I never really got close to 4mbps speeds when I was on a 4meg line.
Should the same hold true for the 8meg line? Should you not sync it to a bit of a higher speed to get me closer to the 8mbps speed at least?
I'm paying for an 8meg line but getting 6meg line speeds.

Ah! I'll need to check what the DSL line sync is at the moment, can you please PM me the line number quickly.
 
Top
Sign up to the MyBroadband newsletter
X