Afrihost Capped DSL Feedback

Thanks, first I'll email a friend here who works for Telkom and see what he can do.
With my line stats I should get max speed :)

It's always hard to say, it depends on a lot of other factors - but definitely chat to Telkom peeps, they know more than everyone ;)
 
hey capped customers, can anyone give some feedback on the AH NNTP? Good, bad, average and working?
 
Currently seeing high latency and slow performance here in Cape Town. Are there currently any issues?

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=106ms TTL=56
Reply from 8.8.8.8: bytes=32 time=114ms TTL=56
Reply from 8.8.8.8: bytes=32 time=111ms TTL=56
Reply from 8.8.8.8: bytes=32 time=111ms TTL=56


Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=92ms TTL=63
Reply from 155.239.255.250: bytes=32 time=93ms TTL=63
Reply from 155.239.255.250: bytes=32 time=93ms TTL=63
Reply from 155.239.255.250: bytes=32 time=92ms TTL=63


Pinging 169.1.1.1 with 32 bytes of data:
Reply from 169.1.1.1: bytes=32 time=94ms TTL=57
Reply from 169.1.1.1: bytes=32 time=97ms TTL=57
Reply from 169.1.1.1: bytes=32 time=96ms TTL=57
Reply from 169.1.1.1: bytes=32 time=97ms TTL=57


Pinging battle.net [24.105.29.30] with 32 bytes of data:
Reply from 24.105.29.30: bytes=32 time=529ms TTL=40
Reply from 24.105.29.30: bytes=32 time=382ms TTL=40
Reply from 24.105.29.30: bytes=32 time=378ms TTL=40
Reply from 24.105.29.30: bytes=32 time=378ms TTL=40
 
Currently seeing high latency and slow performance here in Cape Town. Are there currently any issues?

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=106ms TTL=56
Reply from 8.8.8.8: bytes=32 time=114ms TTL=56
Reply from 8.8.8.8: bytes=32 time=111ms TTL=56
Reply from 8.8.8.8: bytes=32 time=111ms TTL=56


Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=92ms TTL=63
Reply from 155.239.255.250: bytes=32 time=93ms TTL=63
Reply from 155.239.255.250: bytes=32 time=93ms TTL=63
Reply from 155.239.255.250: bytes=32 time=92ms TTL=63


Pinging 169.1.1.1 with 32 bytes of data:
Reply from 169.1.1.1: bytes=32 time=94ms TTL=57
Reply from 169.1.1.1: bytes=32 time=97ms TTL=57
Reply from 169.1.1.1: bytes=32 time=96ms TTL=57
Reply from 169.1.1.1: bytes=32 time=97ms TTL=57


Pinging battle.net [24.105.29.30] with 32 bytes of data:
Reply from 24.105.29.30: bytes=32 time=529ms TTL=40
Reply from 24.105.29.30: bytes=32 time=382ms TTL=40
Reply from 24.105.29.30: bytes=32 time=378ms TTL=40
Reply from 24.105.29.30: bytes=32 time=378ms TTL=40

Seeing high latency here, even to the bras though. Are you still seeing similar results today?
 
Latency was fine during the day, but now in the evening again its high and browsing is slow.

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=92ms TTL=56
Reply from 8.8.8.8: bytes=32 time=91ms TTL=56
Reply from 8.8.8.8: bytes=32 time=81ms TTL=56
Reply from 8.8.8.8: bytes=32 time=93ms TTL=56

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=75ms TTL=63
Reply from 155.239.255.250: bytes=32 time=90ms TTL=63
Reply from 155.239.255.250: bytes=32 time=91ms TTL=63
Reply from 155.239.255.250: bytes=32 time=89ms TTL=63


Pinging 169.1.1.1 with 32 bytes of data:
Reply from 169.1.1.1: bytes=32 time=83ms TTL=57
Reply from 169.1.1.1: bytes=32 time=86ms TTL=57
Reply from 169.1.1.1: bytes=32 time=90ms TTL=57
Reply from 169.1.1.1: bytes=32 time=90ms TTL=57
 
Latency was fine during the day, but now in the evening again its high and browsing is slow.

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=92ms TTL=56
Reply from 8.8.8.8: bytes=32 time=91ms TTL=56
Reply from 8.8.8.8: bytes=32 time=81ms TTL=56
Reply from 8.8.8.8: bytes=32 time=93ms TTL=56

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=75ms TTL=63
Reply from 155.239.255.250: bytes=32 time=90ms TTL=63
Reply from 155.239.255.250: bytes=32 time=91ms TTL=63
Reply from 155.239.255.250: bytes=32 time=89ms TTL=63


Pinging 169.1.1.1 with 32 bytes of data:
Reply from 169.1.1.1: bytes=32 time=83ms TTL=57
Reply from 169.1.1.1: bytes=32 time=86ms TTL=57
Reply from 169.1.1.1: bytes=32 time=90ms TTL=57
Reply from 169.1.1.1: bytes=32 time=90ms TTL=57

Bras is still showing a latency spike. :( It's possible that your exchange is congested.
 
Cape Town, Southern

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=107ms TTL=63
Reply from 155.239.255.250: bytes=32 time=96ms TTL=63
Reply from 155.239.255.250: bytes=32 time=106ms TTL=63
Request timed out.

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 96ms, Maximum = 107ms, Average = 103ms

C:\Users\Matthew>ping bras.afrihost.com

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Reply from 155.239.255.250: bytes=32 time=83ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 83ms, Maximum = 83ms, Average = 83ms

C:\Users\Matthew>
 
Kleinmond, Western Cape

Pinging 169.1.1.1 with 32 bytes of data:
Reply from 169.1.1.1: bytes=32 time=619ms TTL=57
Reply from 169.1.1.1: bytes=32 time=446ms TTL=57
Reply from 169.1.1.1: bytes=32 time=547ms TTL=57
Reply from 169.1.1.1: bytes=32 time=466ms TTL=57

Ping statistics for 169.1.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 446ms, Maximum = 619ms, Average = 519ms


Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

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


Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=718ms TTL=56
Request timed out.
Reply from 8.8.8.8: bytes=32 time=461ms TTL=56
Reply from 8.8.8.8: bytes=32 time=566ms TTL=56

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 461ms, Maximum = 718ms, Average = 581ms

Please help us with this problem!!!

Please please please.
 
Hi am I currently on the Afrihost 100gb account for R110 (shaped I believe)
I would like to know if I move to the Afrihost 50gb account if it will be 100% unshapped for DSTV streaming
Most of the time, DSTV streaming is bad on my shaped account, I am willing to go for an unshapped account for a better streaming experience.
Thanks

I do have a 2mb line, a few times the last few months streaming has been decent, most of the time it is not
 
Hi am I currently on the Afrihost 100gb account for R110 (shaped I believe)
I would like to know if I move to the Afrihost 50gb account if it will be 100% unshapped for DSTV streaming
Most of the time, DSTV streaming is bad on my shaped account, I am willing to go for an unshapped account for a better streaming experience.
Thanks

I do have a 2mb line, a few times the last few months streaming has been decent, most of the time it is not

Do not waste your time, I did the same and found no difference between the 100GB shaped and the 50GB unshaped.
Am now back to the 100GB shaped and streaming happily ever after.
Just make sure you have a cable from the router to the TV set and not using wireless as that slows you down by 50%.
 
Can anyone tell me if the Afrihost/Axxess news servers are down? connect error 10061
 
Can anyone tell me if the Afrihost/Axxess news servers are down? connect error 10061

I was seeing the same from about 1am last night, but checked and seems working now from AH at least, my connection test works but I don't have anything I need to download right now.
 
Hi am I currently on the Afrihost 100gb account for R110 (shaped I believe)
I would like to know if I move to the Afrihost 50gb account if it will be 100% unshapped for DSTV streaming
Most of the time, DSTV streaming is bad on my shaped account, I am willing to go for an unshapped account for a better streaming experience.
Thanks

I do have a 2mb line, a few times the last few months streaming has been decent, most of the time it is not

Hi there. Realtime services such as streaming does not get shaped at all. :) If you are experiencing problems, it is likely being caused by something else. What DNS settings are you using?
 
Do not waste your time, I did the same and found no difference between the 100GB shaped and the 50GB unshaped.
Am now back to the 100GB shaped and streaming happily ever after.
Just make sure you have a cable from the router to the TV set and not using wireless as that slows you down by 50%.

Great advice. :) If you ever have any future problems, please let me know.
 
Top
Sign up to the MyBroadband newsletter
X