Afrihost POC Network - Afrigreen Feedback

Status
Not open for further replies.
And it is continuing its downward spiral - I really wish I had your optimism for the production version ... time will tell, I am sure :)

/snip

Ping statistics for 95.172.91.23:
Packets: Sent = 153, Received = 151, Lost = 2 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 197ms, Maximum = 411ms, Average = 209ms

In conclusion, I suppose this exercise just proves what I have been seeing all along on my ping plotter tests are pretty accurate :(
For some reason your line isn't consistent.
Code:
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\Lara>ping 95.172.91.23 -t

Pinging 95.172.91.23 with 32 bytes of data:
Reply from 95.172.91.23: bytes=32 time=218ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=218ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=218ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=218ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=218ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=218ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=216ms TTL=43
Reply from 95.172.91.23: bytes=32 time=218ms TTL=43
Reply from 95.172.91.23: bytes=32 time=218ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=218ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=218ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=218ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43
Reply from 95.172.91.23: bytes=32 time=218ms TTL=43
Reply from 95.172.91.23: bytes=32 time=217ms TTL=43

Ping statistics for 95.172.91.23:
    Packets: Sent = 51, Received = 51, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 216ms, Maximum = 218ms, Average = 217ms
Control-C
^C
C:\Users\Lara>
 
Well it was enough of a priority to come up with the idea of the 100gb AfriThanks for the capped accounts. Anyways, I will stop winging now. I really don't have the energy anymore. Just don't think it is right. But anyways. Cheers. Have a good evening.

That was for Capped users, yes.
The context of the conversation was for everyone else though - which was answered above.
 
If your account is anything like mine, do yourself a favour and run a pingpath test. Then switch accounts to another ISP and do the same test. You'll be in for a real eye opener.

TBH - if you followed my posts on this thread, you would notice that I have been doing back to back tests on the AfriGreen, the @afrihost (MYN) and a WebAfrica account and yes ....... the WA account runs like a swiss clock.

But then I need to be extremely fair - yes I am uber frustrated with Afrihost at this very moment and their ClientZone is not much to write home about either (I have personally been battling with this problem for a very long time). I even quit AH for a year and signed up with OpenWeb - 8 months later, I had the same problem with them, only issue with OW, is you have to deal with a lot more arrogance on their support division, I came back to AH ...... few months later - same latency issue (again after getting fed up with their poor ClientZone support, I quit AH again). Signed up with WebAfrica ..... within two months had latency issues on their network in the mornings around 8 am. WA have a superb Client Support group, I really had no issues dealing with them, but they reliant on their downstream service provider :(

Long story short, they could not resolve the problem and I came back to AH, hence my earlier statement "rather the devil I know"
 
TBH - if you followed my posts on this thread, you would notice that I have been doing back to back tests on the AfriGreen, the @afrihost (MYN) and a WebAfrica account and yes ....... the WA account runs like a swiss clock.

But then I need to be extremely fair - yes I am uber frustrated with Afrihost at this very moment and their ClientZone is not much to write home about either (I have personally been battling with this problem for a very long time). I even quit AH for a year and signed up with OpenWeb - 8 months later, I had the same problem with them, only issue with OW, is you have to deal with a lot more arrogance on their support division, I came back to AH ...... few months later - same latency issue (again after getting fed up with their poor ClientZone support, I quit AH again). Signed up with WebAfrica ..... within two months had latency issues on their network in the mornings around 8 am. WA have a superb Client Support group, I really had no issues dealing with them, but they reliant on their downstream service provider :(

Long story short, they could not resolve the problem and I came back to AH, hence my earlier statement "rather the devil I know"

Interested to hear your feedback around ClientZone - could you PM me the details that we can work through?
 
TBH - if you followed my posts on this thread, you would notice that I have been doing back to back tests on the AfriGreen, the @afrihost (MYN) and a WebAfrica account and yes ....... the WA account runs like a swiss clock.

But then I need to be extremely fair - yes I am uber frustrated with Afrihost at this very moment and their ClientZone is not much to write home about either (I have personally been battling with this problem for a very long time). I even quit AH for a year and signed up with OpenWeb - 8 months later, I had the same problem with them, only issue with OW, is you have to deal with a lot more arrogance on their support division, I came back to AH ...... few months later - same latency issue (again after getting fed up with their poor ClientZone support, I quit AH again). Signed up with WebAfrica ..... within two months had latency issues on their network in the mornings around 8 am. WA have a superb Client Support group, I really had no issues dealing with them, but they reliant on their downstream service provider :(

Long story short, they could not resolve the problem and I came back to AH, hence my earlier statement "rather the devil I know"
I hear what you are saying.

I just don't know how much more of this I can take. I was forced to buy a backup account today because this BS is having an impact on our business. I have defended Afrihost in the past and I have never left as a client. Been with them from the beginning. They were brilliant, then the whole MTN thing happened. It's been problematic since then.
I have looked at other service providers and I will definitely move if this new network does not work. There are good ISPs out there. I do not expect perfection but this is madness!
 
Last edited:
These are my pingpath tests using Afrigreen on the 2nd Hop:
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
2 --- 100/ 100 =100% 100/ 100 =100% 169-0-18-1.ip.afrihost.co.za [169.0.18.1]

On Afrigreen - The Round Trip Time (RTT) times out. 100% packet loss.

These are my pingpath tests using another ISP account on the 2nd Hop:
2 19ms 0/ 100 = 0% 0/ 100 = 0% 196-210-146-1.dynamic.isadsl.co.za [196.210.146.1]
On the other ISP - RTT 19 ms with Zero packet loss
 
Here is some of my stats that I have been used to:

traceroute google.co.za

traceroute to google.co.za (216.239.38.120), 30 hops max, 60 byte packets
1 DNSTHINGY.local (192.168.0.1) 0.258 ms 0.350 ms 0.592 ms
2 169-0-60-1.ip.afrihost.co.za (169.0.60.1) 6.445 ms 8.440 ms 10.608 ms
3 169-1-1-238.ip.afrihost.co.za (169.1.1.238 ) 15.530 ms 16.938 ms 18.216 ms
4 41.170.79.236 (41.170.79.236) 20.924 ms 22.590 ms 24.557 ms
5 google.jb1.napafrica.net (196.46.25.166) 26.800 ms 28.242 ms 30.441 ms
6 72.14.237.239 (72.14.237.239) 32.911 ms 72.14.239.129 (72.14.239.129) 25.384 ms 72.14.237.239 (72.14.237.239) 7.960 ms
7 any-in-2678.1e100.net (216.239.38.120) 9.921 ms 12.115 ms 14.260 ms


ping google.co.za


PING google.co.za (216.239.38.120) 56(84) bytes of data.64 bytes from any-in-2678.1e100.net (216.239.38.120): icmp_seq=1 ttl=57 time=7.53 ms
64 bytes from any-in-2678.1e100.net (216.239.38.120): icmp_seq=2 ttl=57 time=8.12 ms
64 bytes from any-in-2678.1e100.net (216.239.38.120): icmp_seq=3 ttl=57 time=7.90 ms
64 bytes from any-in-2678.1e100.net (216.239.38.120): icmp_seq=4 ttl=57 time=7.73 ms
64 bytes from any-in-2678.1e100.net (216.239.38.120): icmp_seq=5 ttl=57 time=7.64 ms
64 bytes from any-in-2678.1e100.net (216.239.38.120): icmp_seq=6 ttl=57 time=11.6 ms
64 bytes from any-in-2678.1e100.net (216.239.38.120): icmp_seq=7 ttl=57 time=7.53 ms
64 bytes from any-in-2678.1e100.net (216.239.38.120): icmp_seq=8 ttl=57 time=8.44 ms
64 bytes from any-in-2678.1e100.net (216.239.38.120): icmp_seq=9 ttl=57 time=8.19 ms
64 bytes from any-in-2678.1e100.net (216.239.38.120): icmp_seq=10 ttl=57 time=8.21 ms
64 bytes from any-in-2678.1e100.net (216.239.38.120): icmp_seq=11 ttl=57 time=8.01 ms
64 bytes from any-in-2678.1e100.net (216.239.38.120): icmp_seq=12 ttl=57 time=7.50 ms
64 bytes from any-in-2678.1e100.net (216.239.38.120): icmp_seq=13 ttl=57 time=8.46 ms
64 bytes from any-in-2678.1e100.net (216.239.38.120): icmp_seq=14 ttl=57 time=7.72 ms
64 bytes from any-in-2678.1e100.net (216.239.38.120): icmp_seq=15 ttl=57 time=7.27 ms
64 bytes from any-in-2678.1e100.net (216.239.38.120): icmp_seq=16 ttl=57 time=20.0 ms
64 bytes from any-in-2678.1e100.net (216.239.38.120): icmp_seq=17 ttl=57 time=7.41 ms
64 bytes from any-in-2678.1e100.net (216.239.38.120): icmp_seq=18 ttl=57 time=8.21 ms
64 bytes from any-in-2678.1e100.net (216.239.38.120): icmp_seq=19 ttl=57 time=8.01 ms
64 bytes from any-in-2678.1e100.net (216.239.38.120): icmp_seq=20 ttl=57 time=8.25 ms
^C
--- google.co.za ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19027ms
rtt min/avg/max/mdev = 7.275/8.697/20.033/2.749 ms

1496930434.png
 
Last edited:
Yeah somethings off tonight... Speedtests full speed but unable to load websites at any reasonable speed.

AfriRed working well though!

Z
 
Facebook slow,diablo3 latency is through the roof. Windows updates rocking it at sub 7kb/s. Definitely not 100%
 
Yeah somethings off tonight... Speedtests full speed but unable to load websites at any reasonable speed.

AfriRed working well though!

Z
:(

That's not good... How are things looking this morning?
 
Facebook slow,diablo3 latency is through the roof. Windows updates rocking it at sub 7kb/s. Definitely not 100%

Are you on a Capped, Uncapped or Business Uncapped account? Are you using the default DNS?
 
I hear what you are saying.

I just don't know how much more of this I can take. I was forced to buy a backup account today because this BS is having an impact on our business. I have defended Afrihost in the past and I have never left as a client. Been with them from the beginning. They were brilliant, then the whole MTN thing happened. It's been problematic since then.
I have looked at other service providers and I will definitely move if this new network does not work. There are good ISPs out there. I do not expect perfection but this is madness!

I am with you on this one - Signed up with AH way back in Jan 2011 and had the genuine "pure internet joy" experience for approximately 10 months. Learnt a very expensive lesson at the time, as AH ClientZone techie convinced my problems I had at the time was due to a faulty modem ...... bought a fairly expensive replacement unit, only to find that the fault was not with my modem :twisted:

Jumped ship a few times and returned to AH a few times, just to end up being seriously frustrated (I do relate how you feel, even though I am not relying on AH for my business ... my internet access is purely for leisure).

The problem I have is a case of "when we" :(

Because I really had an awesome time with Afrihost's service in early 2011 (and the odd few months after that when they were delivering the service one expects), I kinda expect it to continue indefinitely - sadly it is not happening and I suppose that is where some of the additional frustration creeps in. AH keeps laying claim to the "pure internet joy" experience, but at times fails to deliver.

As I sadi before, I will be here until the launch of the "miracle cure" and like yourself, if it fails to deliver, I shall also be seeking a new ISP (not sure who though).

Who knows maybe I am a masochists and this is why I keep returning :p
 
For some reason your line isn't consistent.

/snip

Yay! I am glad you see it too ...... this is what I am saying all along :(

Yet, when I connect via my WebAfrica account, it is totally different - why?
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X