Afrihost Capped DSL Feedback

standerr said:
Are we getting any closer to solutions? You guys promised improvements before the end of January, but for me it's stayed the same. And as we've shown it's much worse than early January.

Can we get some feedback? Not just the info is being passed on. Some of us are actually technical people that can handle some more info.
Click to expand...

Our Team is definitely making some progress, but they haven't stopped working yet. I'm not sure myself about the exact changes that have been made, I'll try to find out for you.
 
And the clock strikes 6:00 PM

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 11ms, Average = 11ms
Click to expand...

AH_AHLocal_5-59PM.PNG

AH_CSGO_6-01PM.PNG

AH_News24_5-53PM.PNG

AH_YouTube_5-53PM.PNG

I'm actually so tired of these endless ridiculous issues. If this isn't fixed very soon I'm going to find another ISP - actually looking around at the moment.
 
AfriFella said:
Your latency results do seem a little bit up and down here... Not seeing any major spikes though. What kind of throughput are you experiencing?
Click to expand...

Not seeing any major spikes, okay, have you actually looked at my traces? Do you seriously consider 200ms+ spikes en route to local sites NORMAL?

Have you tried playing any online game after 6:00 PM in the evening? Impossible, too many spikes. What a terrible experience. Luckily I have a Vox account to connect to EVERY night that actually allows me to play stuff online. This constant spiking and pa

Why does this only occur when I'm connected to my Afrihost account? I've been following this thread and clearly I'm not the only one with issues. standerr's tests perfectly demonstrates what is going on and where on the network.

Here are more tests, because why the hell not.

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 11ms, Average = 11ms
Click to expand...

AH_AHSiteLocal_7-44PM.PNG

AH_CSGO_7-43PM.PNG

AH_YouTube_7-48PM.PNG

AH_TTVLHR_7-56PM.PNG
 
DeatheCore said:
Not seeing any major spikes, okay, have you actually looked at my traces? Do you seriously consider 200ms+ spikes en route to local sites NORMAL?

Have you tried playing any online game after 6:00 PM in the evening? Impossible, too many spikes. What a terrible experience. Luckily I have a Vox account to connect to EVERY night that actually allows me to play stuff online. This constant spiking and pa

Why does this only occur when I'm connected to my Afrihost account? I've been following this thread and clearly I'm not the only one with issues. standerr's tests perfectly demonstrates what is going on and where on the network.

Here are more tests, because why the hell not.



View attachment 416681

View attachment 416683

View attachment 416685

View attachment 416687
Click to expand...

As I mentioned, I do see these spikes, but there are no 200ms spikes on average. :) We're doing our best to improve the experience for everyone on our network and I immediately passed your results onto our network team to investigate - we really appreciate your feedback. :)
 
AfriFella said:
As I mentioned, I do see these spikes, but there are no 200ms spikes on average. :) We're doing our best to improve the experience for everyone on our network and I immediately passed your results onto our network team to investigate - we really appreciate your feedback. :)
Click to expand...

Yes. By prioritizing ICMP, and deprioritizing everything else, you make it IMPOSSIBLE for us to show "constant" latency - at least not with ICMP. Yet, you are constantly just asking for more and more and more. Always the same ****. Round and round we go in circles...

It doesn't change jack. Took me 5 minutes, and 10 refreshes, JUST to load this very page! Your "Critical Care" and "NOC" aren't the only ones that knows how networks work...

PS: Take your condescending smiley faces and do something else with them. This isn't the place, nor the time for them.
 
AfriFella said:
As I mentioned, I do see these spikes, but there are no 200ms spikes on average. :) We're doing our best to improve the experience for everyone on our network and I immediately passed your results onto our network team to investigate - we really appreciate your feedback. :)
Click to expand...

Okay, so not 200ms on average, but at least 130ms on average.

Yes, I understand that you guys are trying to improve your network, but this has been going on for months now with almost no feedback. I'm not sure why I'm still submitting tests results after all this time in hopes of change and haven't just moved to another ISP...
 
DeatheCore said:
I assume you're using Chrome - try refresh the page a few times, seems to help me occasionally.

Edit: nevermind, buffer health seems to drop off intermittently.
Click to expand...

I'm using Chrome, that was taken after the 3rd refresh. I guess 15 more couldn't hurt :crylaugh:
 
Not looking to good tonight…4mb line Cape Town



http://netgauge.ookla.com/share/619500022.png
http://netgauge.ookla.com/share/619501235.png

Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\Windows\system32>tracert afrihost.com

Tracing route to afrihost.com [104.20.30.244]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 1203 ms 1175 ms 1236 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 1181 ms 1186 ms 1236 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 * 769 ms 811 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 854 ms 884 ms 868 ms 41.164.52.40
7 65 ms 65 ms 70 ms 172.18.1.164
8 928 ms 950 ms 979 ms cloudflare.ixp.joburg [196.46.25.198]
9 986 ms 1001 ms 1008 ms 104.20.30.244

Trace complete.

C:\Windows\system32>ping bras.afrihost.com

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=660ms TTL=63
Reply from 155.239.255.250: bytes=32 time=695ms TTL=63
Reply from 155.239.255.250: bytes=32 time=777ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 660ms, Maximum = 777ms, Average = 710ms

C:\Windows\system32>
 
I disagree about only having one thread for capped, seeing that there are 2 capped products.
 
Test Result
Last Result:
Download Speed: 1719 kbps (214.9 KB/sec transfer rate)
Upload Speed: 440 kbps (55 KB/sec transfer rate)
Latency: 25 ms
Jitter: 5 ms
2017/02/08, 8:45:23 AM
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X