electrofreeze
Expert Member
we need more ipc!!!!
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.




We've been trying to tell you guys this for ages now.
I changed back to Afrihost and started it over. This is what it's currently at:
View attachment 200190
I can tell you as it gets closer to peak that value is going to keep going up.
I'll PM you now. The problem is you guys keep 'testing' my account from JHB where there is no issue. It's down here in the south. Either the South IPC or something else causing this but it's down here. It's incredibly frustrating.
@Afriguy
NNTP is screwd again........
View attachment 200192
well I suppose almost 15 hours for a 1 gig file does not seem too bad
^ ye I tried as well I was just blinked around. Switched to another ISP reconnected and was perfect
Ye cape town, has these packet loss issues on Afrihost every night now, the worst thing that happens is it just drops connection to TS and gaming clients like LoL/Dota/CS/WoW and it doesnt reconect then I switch to another ISP and poof problem is gone.
Are your other downloads slow too?





Pinging google.co.za [66.8.14.49] with 32 bytes of data:
Reply from 66.8.14.49: bytes=32 time=31ms TTL=56
Reply from 66.8.14.49: bytes=32 time=32ms TTL=56
Reply from 66.8.14.49: bytes=32 time=31ms TTL=56
Reply from 66.8.14.49: bytes=32 time=31ms TTL=56
Reply from 66.8.14.49: bytes=32 time=30ms TTL=56
Reply from 66.8.14.49: bytes=32 time=31ms TTL=56
Reply from 66.8.14.49: bytes=32 time=30ms TTL=56
Reply from 66.8.14.49: bytes=32 time=31ms TTL=56
Reply from 66.8.14.49: bytes=32 time=33ms TTL=56
Reply from 66.8.14.49: bytes=32 time=31ms TTL=56
Reply from 66.8.14.49: bytes=32 time=31ms TTL=56
Reply from 66.8.14.49: bytes=32 time=33ms TTL=56
Reply from 66.8.14.49: bytes=32 time=31ms TTL=56
Reply from 66.8.14.49: bytes=32 time=31ms TTL=56
Ping statistics for 66.8.14.49:
Packets: Sent = 14, Received = 14, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 33ms, Average = 31ms
Pinging google.co.za [216.58.223.3] with 32 bytes of data:
Reply from 216.58.223.3: bytes=32 time=26ms TTL=54
Reply from 216.58.223.3: bytes=32 time=25ms TTL=54
Reply from 216.58.223.3: bytes=32 time=26ms TTL=54
Reply from 216.58.223.3: bytes=32 time=25ms TTL=54
Reply from 216.58.223.3: bytes=32 time=26ms TTL=54
Reply from 216.58.223.3: bytes=32 time=25ms TTL=54
Reply from 216.58.223.3: bytes=32 time=24ms TTL=54
Reply from 216.58.223.3: bytes=32 time=27ms TTL=54
Reply from 216.58.223.3: bytes=32 time=26ms TTL=54
Reply from 216.58.223.3: bytes=32 time=24ms TTL=54
Reply from 216.58.223.3: bytes=32 time=27ms TTL=54
Reply from 216.58.223.3: bytes=32 time=24ms TTL=54
Reply from 216.58.223.3: bytes=32 time=25ms TTL=54
Reply from 216.58.223.3: bytes=32 time=25ms TTL=54
Reply from 216.58.223.3: bytes=32 time=25ms TTL=54
Ping statistics for 216.58.223.3:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 27ms, Average = 25ms


Gaming is terrible on BF4 with Afrihost.. LAG galore!!!
If you look at the below screenshot you see 30 MS pings with Afrihost.
Afrihost to MTN Server
When on the Webafrica account and doing a speedtest to the same MTN server it also shows 30ms. (See Below)
Webafrica to MTN
However, doing tests too other hosted server like Telkom & MWEB whilst connected to Webafrica, then the pings goes down to 10ms or 9ms. (See Below) Vodacom hosted servers being the BEST!!. Shame on you Afrihost/MTN.
Webafrica to Telkom
Webafrica to MWEB
Webafrica to Vodacom
Pings to Google.co.za, whilst on Afihost:
Code:Pinging google.co.za [66.8.14.49] with 32 bytes of data: Reply from 66.8.14.49: bytes=32 time=31ms TTL=56 Reply from 66.8.14.49: bytes=32 time=32ms TTL=56 Reply from 66.8.14.49: bytes=32 time=31ms TTL=56 Reply from 66.8.14.49: bytes=32 time=31ms TTL=56 Reply from 66.8.14.49: bytes=32 time=30ms TTL=56 Reply from 66.8.14.49: bytes=32 time=31ms TTL=56 Reply from 66.8.14.49: bytes=32 time=30ms TTL=56 Reply from 66.8.14.49: bytes=32 time=31ms TTL=56 Reply from 66.8.14.49: bytes=32 time=33ms TTL=56 Reply from 66.8.14.49: bytes=32 time=31ms TTL=56 Reply from 66.8.14.49: bytes=32 time=31ms TTL=56 Reply from 66.8.14.49: bytes=32 time=33ms TTL=56 Reply from 66.8.14.49: bytes=32 time=31ms TTL=56 Reply from 66.8.14.49: bytes=32 time=31ms TTL=56 Ping statistics for 66.8.14.49: Packets: Sent = 14, Received = 14, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 30ms, Maximum = 33ms, Average = 31ms
Pings from Webafrica to google.co.za
Code:Pinging google.co.za [216.58.223.3] with 32 bytes of data: Reply from 216.58.223.3: bytes=32 time=26ms TTL=54 Reply from 216.58.223.3: bytes=32 time=25ms TTL=54 Reply from 216.58.223.3: bytes=32 time=26ms TTL=54 Reply from 216.58.223.3: bytes=32 time=25ms TTL=54 Reply from 216.58.223.3: bytes=32 time=26ms TTL=54 Reply from 216.58.223.3: bytes=32 time=25ms TTL=54 Reply from 216.58.223.3: bytes=32 time=24ms TTL=54 Reply from 216.58.223.3: bytes=32 time=27ms TTL=54 Reply from 216.58.223.3: bytes=32 time=26ms TTL=54 Reply from 216.58.223.3: bytes=32 time=24ms TTL=54 Reply from 216.58.223.3: bytes=32 time=27ms TTL=54 Reply from 216.58.223.3: bytes=32 time=24ms TTL=54 Reply from 216.58.223.3: bytes=32 time=25ms TTL=54 Reply from 216.58.223.3: bytes=32 time=25ms TTL=54 Reply from 216.58.223.3: bytes=32 time=25ms TTL=54 Ping statistics for 216.58.223.3: Packets: Sent = 15, Received = 15, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 24ms, Maximum = 27ms, Average = 25ms
Jitter tests
On Afrihost
On WebAfrica
In the above test it shows very much the same, but I did notice the ping/jitter test was done to the same Webafrica hosted server. Does this mean that when going through Afihost/MTN hosted servers pings pick up and causes the lag we are experiencing on the games?
What I do know is that the common problem here is Afrihost.