South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)
Pinging 105.236.6.65 with 32 bytes of data:
Reply from 105.236.6.65: bytes=32 time=8ms TTL=254
Reply from 105.236.6.65: bytes=32 time=8ms TTL=254
Reply from 105.236.6.65: bytes=32 time=8ms TTL=254
Reply from 105.236.6.65: bytes=32 time=8ms TTL=254
Reply from 105.236.6.65: bytes=32 time=7ms TTL=254
Reply from 105.236.6.65: bytes=32 time=8ms TTL=254
Reply from 105.236.6.65: bytes=32 time=8ms TTL=254
Reply from 105.236.6.65: bytes=32 time=8ms TTL=254
Reply from 105.236.6.65: bytes=32 time=11ms TTL=254
Reply from 105.236.6.65: bytes=32 time=7ms TTL=254
Reply from 105.236.6.65: bytes=32 time=9ms TTL=254
Reply from 105.236.6.65: bytes=32 time=8ms TTL=254
Reply from 105.236.6.65: bytes=32 time=8ms TTL=254
Reply from 105.236.6.65: bytes=32 time=8ms TTL=254
Reply from 105.236.6.65: bytes=32 time=8ms TTL=254
Reply from 105.236.6.65: bytes=32 time=7ms TTL=254
Reply from 105.236.6.65: bytes=32 time=8ms TTL=254
Reply from 105.236.6.65: bytes=32 time=7ms TTL=254
Reply from 105.236.6.65: bytes=32 time=9ms TTL=254
Reply from 105.236.6.65: bytes=32 time=8ms TTL=254
Reply from 105.236.6.65: bytes=32 time=11ms TTL=254
Reply from 105.236.6.65: bytes=32 time=9ms TTL=254
Reply from 105.236.6.65: bytes=32 time=8ms TTL=254
Reply from 105.236.6.65: bytes=32 time=8ms TTL=254
Reply from 105.236.6.65: bytes=32 time=8ms TTL=254
Reply from 105.236.6.65: bytes=32 time=8ms TTL=254
Reply from 105.236.6.65: bytes=32 time=7ms TTL=254
Reply from 105.236.6.65: bytes=32 time=8ms TTL=254
Reply from 105.236.6.65: bytes=32 time=7ms TTL=254
Reply from 105.236.6.65: bytes=32 time=8ms TTL=254
Ping statistics for 105.236.6.65:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 11ms, Average = 8ms
2014-05-15 17:54:32,80
Any comments on if this is truly uncapped and unshaped? Wanting to move from my current ISP and checking out other ISPs...
Yes. It is indeed
So they aren't going to be knobs like Ope_We_ and make my account unusable when I hit a certain amount per month?
So they aren't going to be knobs like Ope_We_ and make my account unusable when I hit a certain amount per month?
Zertop doesn't actually have an account. He's the Afrihost shill.AH Business is completely unshaped... you'll love it
Z
Zertop doesn't actually have an account. He's the Afrihost shill.
They don't call it shaped, but it sure feels the same.
Yes it is, its the way internet is supposed to be.Any comments on if this is truly uncapped and unshaped? Wanting to move from my current ISP and checking out other ISPs...
Sorry MikeStole my saying![]()
Judging by these comments, Afrihost is the way to go? So far, this thread offers the only positive comments i've seen from any ISP.
I'm currently with MWEB and i've recently been MmmmWEBBED!
Raped my account this month, currently on about 600GB and badly throttled to a crawl as a result. My DSL is basically unusable. Can't even open the MWEB home page during the day
I run a one man business from home and obviously I need connectivity. I'm definitely divorcing MWEB but I'm not sure who I should marry.
Any advice about Afrihost would be appreciated.
Zertop doesn't actually have an account. He's the Afrihost shill.
They don't call it shaped, but it sure feels the same.
Any comments on if this is truly uncapped and unshaped? Wanting to move from my current ISP and checking out other ISPs...
Our product is absolutely unshaped, and uncapped. We don't impose any rules on the product, except for a rate limit to the base line speed (like 4Mbps Business) and we restrict the account to one concurrent connection. Otherwise we don't touch it at all.
Epic. Will be signing up soon when my cancellation period with OW is done... Thanks for the details
Here are the resuts:
Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 8ms
Your maximum ping was 11ms
Looking at your average ping, your line seems to be running perfectly![]()
It seems that your maximum ping is also good. If there are any issues, they most probably lie with your ISP :-(
Detailed Report
Code:Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) Pinging 105.236.6.65 with 32 bytes of data: Reply from 105.236.6.65: bytes=32 time=8ms TTL=254 Reply from 105.236.6.65: bytes=32 time=8ms TTL=254 Reply from 105.236.6.65: bytes=32 time=8ms TTL=254 Reply from 105.236.6.65: bytes=32 time=8ms TTL=254 Reply from 105.236.6.65: bytes=32 time=7ms TTL=254 Reply from 105.236.6.65: bytes=32 time=8ms TTL=254 Reply from 105.236.6.65: bytes=32 time=8ms TTL=254 Reply from 105.236.6.65: bytes=32 time=8ms TTL=254 Reply from 105.236.6.65: bytes=32 time=11ms TTL=254 Reply from 105.236.6.65: bytes=32 time=7ms TTL=254 Reply from 105.236.6.65: bytes=32 time=9ms TTL=254 Reply from 105.236.6.65: bytes=32 time=8ms TTL=254 Reply from 105.236.6.65: bytes=32 time=8ms TTL=254 Reply from 105.236.6.65: bytes=32 time=8ms TTL=254 Reply from 105.236.6.65: bytes=32 time=8ms TTL=254 Reply from 105.236.6.65: bytes=32 time=7ms TTL=254 Reply from 105.236.6.65: bytes=32 time=8ms TTL=254 Reply from 105.236.6.65: bytes=32 time=7ms TTL=254 Reply from 105.236.6.65: bytes=32 time=9ms TTL=254 Reply from 105.236.6.65: bytes=32 time=8ms TTL=254 Reply from 105.236.6.65: bytes=32 time=11ms TTL=254 Reply from 105.236.6.65: bytes=32 time=9ms TTL=254 Reply from 105.236.6.65: bytes=32 time=8ms TTL=254 Reply from 105.236.6.65: bytes=32 time=8ms TTL=254 Reply from 105.236.6.65: bytes=32 time=8ms TTL=254 Reply from 105.236.6.65: bytes=32 time=8ms TTL=254 Reply from 105.236.6.65: bytes=32 time=7ms TTL=254 Reply from 105.236.6.65: bytes=32 time=8ms TTL=254 Reply from 105.236.6.65: bytes=32 time=7ms TTL=254 Reply from 105.236.6.65: bytes=32 time=8ms TTL=254 Ping statistics for 105.236.6.65: Packets: Sent = 30, Received = 30, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 7ms, Maximum = 11ms, Average = 8ms 2014-05-15 17:54:32,80
Bumping this in hopes of a solution. HTTP down to a trickle from what my brother tells me at the moment. Any idea what could be going on?