No throughput for the last 2 days at exactly 11pm. It seems to work after 15 minutes or so and a reboot or 2.
Could this be something faulty seeing as it co-incides with the "Free Time" thing that starts at 11pm?
Doesn't that start at 12?
I doubt we will get anything of value coming from Afrihost on the matter, i lost faith in this company sometime ago.
No throughput for the last 2 days at exactly 11pm. It seems to work after 15 minutes or so and a reboot or 2.
Could this be something faulty seeing as it co-incides with the "Free Time" thing that starts at 11pm?
Hmmm naaah I never had any huge issues with those chaps. Quite the contrary in fact - they are always helpful. I do wish the latency was a bit better to London though... on the Telkom account that came with the landline I get around 182-190ms. With Afrihost it usually sits around 200-230ms.
Very strange. I doubt that it's tied to Free-Time, otherwise many other would have similar problems. Are you seeing high latency during these periods
Thanks for the kudos.What DNS settings are you using?
The usual one from PPPoe.
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=18ms TTL=62
Reply from 155.239.255.250: bytes=32 time=18ms TTL=62
Reply from 155.239.255.250: bytes=32 time=17ms TTL=62
Reply from 155.239.255.250: bytes=32 time=18ms TTL=62
Reply from 155.239.255.250: bytes=32 time=17ms TTL=62
Reply from 155.239.255.250: bytes=32 time=17ms TTL=62
Reply from 155.239.255.250: bytes=32 time=17ms TTL=62
Reply from 155.239.255.250: bytes=32 time=17ms TTL=62
Reply from 155.239.255.250: bytes=32 time=17ms TTL=62
Reply from 155.239.255.250: bytes=32 time=18ms TTL=62
Reply from 155.239.255.250: bytes=32 time=17ms TTL=62
Reply from 155.239.255.250: bytes=32 time=17ms TTL=62
Reply from 155.239.255.250: bytes=32 time=17ms TTL=62
Reply from 155.239.255.250: bytes=32 time=17ms TTL=62
Reply from 155.239.255.250: bytes=32 time=18ms TTL=62
Reply from 155.239.255.250: bytes=32 time=17ms TTL=62
Reply from 155.239.255.250: bytes=32 time=18ms TTL=62
Reply from 155.239.255.250: bytes=32 time=17ms TTL=62
Reply from 155.239.255.250: bytes=32 time=17ms TTL=62
Reply from 155.239.255.250: bytes=32 time=17ms TTL=62
Ping statistics for 155.239.255.250:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 18ms, Average = 17ms
Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.1.0.254
2 <1 ms <1 ms <1 ms 10.100.0.1
3 * * * Request timed out.
4 118 ms 119 ms 119 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
5 237 ms 81 ms 64 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 19 ms 19 ms 20 ms optinet.ixp.capetown [196.10.140.145]
7 134 ms 136 ms * 101.te0-0-2-0.cpt-tr-1.optinet.net [197.84.7.4]
8 149 ms 144 ms 143 ms 197-84-247-89.cpt.mweb.co.za [197.84.247.89]
9 146 ms 148 ms 146 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
10 93 ms 65 ms 53 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
11 19 ms 19 ms 19 ms 41-86-110-200.mweb.co.za [41.86.110.200]
Trace complete.
Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.1.0.254
2 <1 ms <1 ms <1 ms 10.100.0.1
3 * * * Request timed out.
4 20 ms 18 ms 18 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
5 18 ms 18 ms 19 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 20 ms 19 ms 20 ms optinet.ixp.capetown [196.10.140.145]
7 20 ms 20 ms 19 ms 101.te0-0-2-0.cpt-tr-1.optinet.net [197.84.7.4]
8 19 ms 19 ms 19 ms 197-84-247-89.cpt.mweb.co.za [197.84.247.89]
9 20 ms 19 ms 19 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
10 30 ms 26 ms 21 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
11 21 ms 19 ms 19 ms 41-86-110-200.mweb.co.za [41.86.110.200]
Trace complete.
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=17ms TTL=62
Reply from 155.239.255.250: bytes=32 time=18ms TTL=62
Reply from 155.239.255.250: bytes=32 time=18ms TTL=62
Reply from 155.239.255.250: bytes=32 time=17ms TTL=62
Reply from 155.239.255.250: bytes=32 time=19ms TTL=62
Reply from 155.239.255.250: bytes=32 time=17ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=17ms TTL=62
Reply from 155.239.255.250: bytes=32 time=18ms TTL=62
Reply from 155.239.255.250: bytes=32 time=18ms TTL=62
I have a downgrade from 2M to 1M, pls help afrihost.
For the life of me not sure what happened to Afrihost support. Still no response on my ticket #WWQ-158-59736. I've sent a few mails with more info, but nothing from their side. Also not having much luck here it seems. Did they maybe fire all their support staff?
Currently again experiencing slow http downloads. YouTube is running at full speed though. So this must be a routing/prioritization issue. The weird part is that a friend also on Afrihost, but about 15km away does not have the same issue.
Download at home
View attachment 454996
Download at office
View attachment 454998
Bras also looking normal
Code:Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data: Reply from 155.239.255.250: bytes=32 time=17ms TTL=62 Reply from 155.239.255.250: bytes=32 time=18ms TTL=62 Reply from 155.239.255.250: bytes=32 time=18ms TTL=62 Reply from 155.239.255.250: bytes=32 time=17ms TTL=62 Reply from 155.239.255.250: bytes=32 time=19ms TTL=62 Reply from 155.239.255.250: bytes=32 time=17ms TTL=62 Reply from 155.239.255.250: bytes=32 time=21ms TTL=62 Reply from 155.239.255.250: bytes=32 time=17ms TTL=62 Reply from 155.239.255.250: bytes=32 time=18ms TTL=62 Reply from 155.239.255.250: bytes=32 time=18ms TTL=62
![]()
There is definitely something going on with your connection. I am going to ask our Critical Care Team to take-over your query, we definitely need to get to the bottom of this!
At this stage I don't really care who looks at it, but just that somebody gives me feedback. I've not received a single word from anybody at Afrihost since it was logged on the 8th.
I've been sending mail after mail with more info, but nothing. Really really bad service.
International connection from CPT East drops to between 170 to 190ms after 41.206.164.253 (if-ae-2-2.tcore1.KLT-Cape-Town.as6453.net) is this an acceptable norm for AH capped accounts?
Pings to this IP between the router and it is maximum of 18ms.
The problem is from this specific IP 41.206.164.253 onward in the Cape Town area.
Is this due to congestion / number of users connection via that IP server to the rest of the world?
And I just want to add that an average ping of 170ms per hop to international servers in a multiplayer gaming environment will get you kicked off the international server because YOU (due to your ISPs routing) will be the cause of lag in the game.
So I cant see that this is an acceptable international standard.
Morning!
Do you mean you have requested a downgrade from 2Mbps to 1Mbps?