Afrihost CAPPED ADSL Feedback (MTN)

Status
Not open for further replies.
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)
Ping request could not find host *[=. Please check the name and try again.

30/04/2014 11:51:41.25

Wifi connection directly from router:

Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)
Ping request could not find host *[=. Please check the name and try again.

30/04/2014 11:51:41.25

Tried rebooting a few times as well.
 
Drop me a PM, lets see if I can force a drop from my side :)

Disconnected everything from the router and connected my laptop directly. Rebooted a few times:


Zertop's "Is it my Line" Results
Basic Report:

Your average ping was 21ms
Your maximum ping was 36ms

Looking at your average ping, your line seems to be running perfectly :-)
Looking at your maximum ping, however, it seems as though there could be a slight intermittant issue on the line. If required, please post the results to a forum post.


Detailed Report

Code:
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 105.236.0.129 with 32 bytes of data:
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=21ms TTL=254
Reply from 105.236.0.129: bytes=32 time=21ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=21ms TTL=254
Reply from 105.236.0.129: bytes=32 time=21ms TTL=254
Reply from 105.236.0.129: bytes=32 time=21ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=21ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=21ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=27ms TTL=254
Reply from 105.236.0.129: bytes=32 time=22ms TTL=254
Reply from 105.236.0.129: bytes=32 time=29ms TTL=254
Reply from 105.236.0.129: bytes=32 time=36ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=21ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254

Ping statistics for 105.236.0.129:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 20ms, Maximum = 36ms, Average = 21ms
 
30/04/2014 13:20:25.25

First time linetest actually completed properly.

Seems much better.
 
With the lan cable plugged back in:

Zertop's "Is it my Line" Results
Basic Report:

Your average ping was 35ms
Your maximum ping was 178ms

Looking at your average ping, your line seems to be a bit dodgy :/ This may account for any slow speeds you may be experiencing. However, it could just be related to a high-latency home network (ie... Wi-Fi). If you feel the need, please post the results (at the end of the program) into the forum for advice


Detailed Report

Code:
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 105.236.0.129 with 32 bytes of data:
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=21ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=21ms TTL=254
Reply from 105.236.0.129: bytes=32 time=21ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=19ms TTL=254
Reply from 105.236.0.129: bytes=32 time=21ms TTL=254
Reply from 105.236.0.129: bytes=32 time=21ms TTL=254
Reply from 105.236.0.129: bytes=32 time=23ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=21ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=178ms TTL=254
Reply from 105.236.0.129: bytes=32 time=164ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=163ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=37ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254

Ping statistics for 105.236.0.129:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 19ms, Maximum = 178ms, Average = 35ms
 
30/04/2014 13:31:50.07
 
Disconnected everything from the router and connected my laptop directly. Rebooted a few times:


Zertop's "Is it my Line" Results
Basic Report:

Your average ping was 21ms
Your maximum ping was 36ms

Looking at your average ping, your line seems to be running perfectly :-)
Looking at your maximum ping, however, it seems as though there could be a slight intermittant issue on the line. If required, please post the results to a forum post.


Detailed Report

Code:
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 105.236.0.129 with 32 bytes of data:
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=21ms TTL=254
Reply from 105.236.0.129: bytes=32 time=21ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=21ms TTL=254
Reply from 105.236.0.129: bytes=32 time=21ms TTL=254
Reply from 105.236.0.129: bytes=32 time=21ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=21ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=21ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=27ms TTL=254
Reply from 105.236.0.129: bytes=32 time=22ms TTL=254
Reply from 105.236.0.129: bytes=32 time=29ms TTL=254
Reply from 105.236.0.129: bytes=32 time=36ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254
Reply from 105.236.0.129: bytes=32 time=21ms TTL=254
Reply from 105.236.0.129: bytes=32 time=20ms TTL=254

Ping statistics for 105.236.0.129:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 20ms, Maximum = 36ms, Average = 21ms
 
30/04/2014 13:20:25.25

First time linetest actually completed properly.

Seems much better.

Ping seems reasonably consistent to me, and no packet loss - would indicate all is well, I guess :)
 
Please be aware that there are some authentication issues on the network at the moment. I would advise those affected not to reboot their routers for the next while, until we get a handle on this.

The issues have been present intermittently over the last 24 hours, and seem to fluctuate. At present it does seem to be pretty poor. Please bear with us while our network team work on this. The guys have been working through the night, so we'll keep at it until it gets sorted out :(
 
OW refugee here, I would like some advice on the AH capped accounts.

Have been following this thread for a few weeks now, and can’t definitively figure out if the Cape Town situation has improved after the upgrade. I need for the internet to be working during the day. iOS and Android apps must be able to update, as well as moderate browsing and YouTube usage.

I’m not concerned if NNTP is heavily shaped during the day, but, I would like for AH to manage this. I.E. If I leave NNTP downloading during the day, it can be heavily shaped, but other protocols must be unaffected.

Would an AH capped account work for me? All advice would be much appreciated.

Thanks.

(Current authentication issues not included)
 
OW refugee here, I would like some advice on the AH capped accounts.

Have been following this thread for a few weeks now, and can’t definitively figure out if the Cape Town situation has improved after the upgrade. I need for the internet to be working during the day. iOS and Android apps must be able to update, as well as moderate browsing and YouTube usage.

I’m not concerned if NNTP is heavily shaped during the day, but, I would like for AH to manage this. I.E. If I leave NNTP downloading during the day, it can be heavily shaped, but other protocols must be unaffected.

Would an AH capped account work for me? All advice would be much appreciated.

Thanks.

(Current authentication issues not included)

We don't employ any form of shaping on Capped accounts. Since the upgrade (which was only partial) we have seen improvement in capped performance, especially in latency and overall throughput. We are, however, still expecting additional upgrades to ensure we can ensure better performance even at peak times.
 
We don't employ any form of shaping on Capped accounts. Since the upgrade (which was only partial) we have seen improvement in capped performance, especially in latency and overall throughput. We are, however, still expecting additional upgrades to ensure we can ensure better performance even at peak times.

Thanks for the response. I understand the company line, and really like the sound of it. Was hoping for the recent real world experiences of fellow Cape Town residents, as I'm still seeing a few niggles being posted. Would like to understand if these are the exception rather than the norm.

Thanks.
 
Please be aware that there are some authentication issues on the network at the moment. I would advise those affected not to reboot their routers for the next while, until we get a handle on this.

The issues have been present intermittently over the last 24 hours, and seem to fluctuate. At present it does seem to be pretty poor. Please bear with us while our network team work on this. The guys have been working through the night, so we'll keep at it until it gets sorted out :(

Damn, I saw this too late :(
Connected with another account because Afrihost won't authenticate.
 
Thanks for the response. I understand the company line, and really like the sound of it. Was hoping for the recent real world experiences of fellow Cape Town residents, as I'm still seeing a few niggles being posted. Would like to understand if these are the exception rather than the norm.

Thanks.

I'm sure a few other forumites will give you their experiences as well. But best to test for yourself with a Free GB capped account. You can sign up here:

https://www.afrihost.com/microsites/freegb/?src=socmed
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X