Heisenborg
Honorary Master
- Joined
- Dec 15, 2006
- Messages
- 21,599
- Reaction score
- 14,309
P2P still crawling, bye bye AH
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Haha! everyones back from holiday and internet usage is up.
This past festive season pretty much confirmed fault is congestion on Afrihost network. Since 25 Dec pings was PERFECT!!! everything went pear shaped once we hit the 4 Jan.
Its also very clear if you run tests during day vs evening. Day pings in 20's, hit 6pm you are about 180's.
Not to mention if you ping bras.afrihost.com, any time of day, you consistently get >25ms.
If you ping afrihost.com, day time, pings are consistently 20's. As soon as you hit evenings, its becomes 180's
bras.afrihost.com is your exchange, if it gets really high in the evenings it's your exchange and not the Afrihost network. Should easily be able to confirm by using another ISP's trial account.
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 155.239.255.250: bytes=32 time=43ms TTL=62
Reply from 155.239.255.250: bytes=32 time=41ms TTL=62
Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 43ms, Average = 42ms
Pinging google.com [216.58.223.46] with 32 bytes of data:
Reply from 216.58.223.46: bytes=32 time=2952ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 216.58.223.46:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 2952ms, Maximum = 2952ms, Average = 2952ms
Pinging google.com [216.58.223.46] with 32 bytes of data:
Reply from 216.58.223.46: bytes=32 time=43ms TTL=54
Reply from 216.58.223.46: bytes=32 time=43ms TTL=54
Reply from 216.58.223.46: bytes=32 time=127ms TTL=54
Reply from 216.58.223.46: bytes=32 time=43ms TTL=54
Ping statistics for 216.58.223.46:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 43ms, Maximum = 127ms, Average = 64ms
Pinging google.com [216.58.223.46] with 32 bytes of data:
Reply from 216.58.223.46: bytes=32 time=44ms TTL=56
Reply from 216.58.223.46: bytes=32 time=43ms TTL=56
Reply from 216.58.223.46: bytes=32 time=43ms TTL=56
Reply from 216.58.223.46: bytes=32 time=43ms TTL=56
Ping statistics for 216.58.223.46:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 43ms, Maximum = 44ms, Average = 43ms
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Request timed out.
Reply from 155.239.255.250: bytes=32 time=2913ms TTL=62
Reply from 155.239.255.250: bytes=32 time=2549ms TTL=62
Reply from 155.239.255.250: bytes=32 time=2310ms TTL=62
Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 2310ms, Maximum = 2913ms, Average = 2590ms
Also having a lot of packet loss again.I know you're not AfriGenie, but I guess he will see this as well. Was playing Diablo 3 and my latency went up to 3k latency so I quit (again).
I pinged bras and then google (see below the first 2 pings).
I then swapped to another ISP account and it was fine (see 3rd quote).
I then swapped back to my AH account and it was fine (see 4th quote) but while typing this post it went belly up again (5th quote).
Swapped back to other ISP account again and it was fine and it is staying fine even after 10mins.
Edit: took 15mins to screw up. If it is indeed exchange congestion, what can be done about it? Or am I screwed and at the mercy of Telkom?
AfriGenie, it seems you resetting my line yesterday did not help.
Afrihost account:
Other ISP account:
Afrihost account again:
Afrihost account after about 4mins:
Also having a lot of packet loss again.
Got a message of this being escalated to NOC (4th Jan), then no nothing.
Any news with regards to this subject![]()

Is there something wrong tonight, torrent speeds are crawling? Capped shaped account
Haha! everyones back from holiday and internet usage is up.
This past festive season pretty much confirmed fault is congestion on Afrihost network. Since 25 Dec pings was PERFECT!!! everything went pear shaped once we hit the 4 Jan.
Its also very clear if you run tests during day vs evening. Day pings in 20's, hit 6pm you are about 180's.
Not to mention if you ping bras.afrihost.com, any time of day, you consistently get >25ms.
If you ping afrihost.com, day time, pings are consistently 20's. As soon as you hit evenings, its becomes 180's
Throughput on Twitch is bad. YT is fine
http://puu.sh/tdlE0/48a9464fcd.png
http://puu.sh/tdlxN/150191b9e3.png
I'm playing The Division and the lag is bad.
I am running a ping to 8.8.8.8 and notice alot of "Request Timed Out" happening ALOT as well as my times are sitting in the 300ms and now and again 30ms.
I tried to call Afrihost and I'm number like 30 in the queue.
Live chat is not working... I'm sick of having to sit in long queues... WTF guys.
Does anybody know if Free Time data is also unshaped if I selected the unshaped option?
According to support it is, but I've had some strange p2p behavior. No concrete evidence, but it feels like p2p is struggling until 6pm, when you start using your cap![]()