Yip. Afrihost network upgrade seems to be working well now.
Glad to hear it
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Yip. Afrihost network upgrade seems to be working well now.
Yaaaaaay, just home for a change of clothes before work after the weekend and no sync AGAIN!
I have just logged a fault, AfriPeople please chase up immediately with whomever you have contacts with, also request a refund for time down as this is day 6 of no sync this month.
Fault No:83CRK190115
Yaaaaaay, just home for a change of clothes before work after the weekend and no sync AGAIN!
I have just logged a fault, AfriPeople please chase up immediately with whomever you have contacts with, also request a refund for time down as this is day 6 of no sync this month.
Fault No:83CRK190115
What's up with AH capped today? Terribly slow. Is it just me?
AH capped: 70 Kbps
Axxess capped: 430 kbps
FNB (IS): 1.7 Mbps
WA capped: 3.97 Mbps
Here it has been a little "spotty" this afternoon as well.
Seems to dip and audio streams buffer, internet slows down, sputters for about 10 minutes or so, then goes back to fast and all OK again.
Kid at home keeps having XBox server disconnects... so might be related. Destiny he says has not been able to connect to server all afternoon on Afrihost.
Not seeing any general trends towards this across the network, would you be able to paste up any diagnostic results here?
I will keep an eye here... it is fine and flying now... but was all "dippy" earlier.
Actually, it has been perfect all during the hols!
No connection for 35% of this month(likely more but wasn't home to notice)... Great job "managing" my line Afrihost, considering I've been +-90min on the line with Telkom.
My line rental better be refunded after this.
We do our absolute best to get the best turnaround time for faults, but there are some line problems that take time to get resolved.
As long as there is a fault open, we can dispute your line rental billing directly with Telkom and they will credit your billing directly with them for the period that the fault was open.
Once it's fixed I'll do that.
Still nothing please escalate, twitter AfriMan added a fault on your system for me as well.
Fault reference AH20150120-174617 has been created for service ID. Regards, Afrihost.
I still have an open fault with Afrihost from 31 December! REF: BVZ-653-74907. The last feedback was on the 14th of January, saying they will give me feedback. What a joke!
That's not cool at all. Can you drop me a PM so we can try and get this sorted out for you?![]()
Just rejoined Afrihost since the beginning of January. So far so good. The only troublesome issue I've noticed is that at times, when joining JHB servers in CS:GO I get a ping of around 200. I'm in CPT and my ping to the CPT servers is always normal.
Is there any obvious reason for this occurring? CS:GO Intoxicated Casual JHB 1 (41.0.11.164) tracert and ping below.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\XYZ>tracert 41.0.11.164
Tracing route to 41.0.11.164 over a maximum of 30 hops
1 <1 ms <1 ms 1 ms 10.0.0.2
2 7 ms 6 ms 7 ms 105-236-249-65-esr-lo.mtnbusiness.co.za [105.236
.249.65]
3 9 ms 8 ms 20 ms 41.181.201.94
4 9 ms 8 ms 8 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
5 9 ms 8 ms 8 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 78 ms 45 ms 125 ms tb-pr-1.za--tb-cr-2.za-a.mtnns.net [196.44.18.14
3]
7 * * * Request timed out.
8 154 ms 154 ms 152 ms 196.43.25.205
9 180 ms 177 ms 176 ms 196.43.39.18
10 177 ms 177 ms 177 ms vodacom-gw.telkom-ipnet.co.za [196.25.253.110]
11 181 ms 181 ms 188 ms 41.0.0.33
12 180 ms 180 ms 180 ms 41.0.0.33
13 181 ms 184 ms 199 ms 41.0.11.164
Trace complete.
C:\Users\XYZ>ping 41.0.11.164
Pinging 41.0.11.164 with 32 bytes of data:
Reply from 41.0.11.164: bytes=32 time=179ms TTL=51
Reply from 41.0.11.164: bytes=32 time=179ms TTL=51
Reply from 41.0.11.164: bytes=32 time=179ms TTL=51
Reply from 41.0.11.164: bytes=32 time=179ms TTL=51
Ping statistics for 41.0.11.164:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 179ms, Maximum = 179ms, Average = 179ms
Hmmm, that looks like the peering between our network and the network that the server is hosted on may be off, I have asked our Team to look into this.
Thanks for the full traceroute.