Afrihost Uncapped DSL Feedback

What's with the slow internet when browsing fis and images in the evening? 400kbps on an 8mbps line? Throttling down to 5%, cool.
 
What is happening in the South? Terrible speed and many pages fail to load. 8Mb/s Uncapped Premium ADSL. Bellville, Western Cape.

ping www.afrihost.com

Pinging www.afrihost.com [104.20.31.244] with 32 bytes of data:
Reply from 104.20.31.244: bytes=32 time=2963ms TTL=58
Reply from 104.20.31.244: bytes=32 time=2965ms TTL=58
Reply from 104.20.31.244: bytes=32 time=2952ms TTL=58
Reply from 104.20.31.244: bytes=32 time=3039ms TTL=58

Ping statistics for 104.20.31.244:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2952ms, Maximum = 3039ms, Average = 2979ms

C:\>tracert www.afrihost.com

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

1 1 ms 2 ms 3 ms 192.168.1.1
2 * * * Request timed out.
3 2801 ms 2796 ms 2797 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
4 2832 ms 2882 ms 2834 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 2852 ms 2860 ms 2860 ms cloudflare.ixp.capetown [196.10.140.198]
6 2834 ms 2851 ms 2869 ms 104.20.30.244

Trace complete.

C:\>ping www.facebook.com

Pinging star-mini.c10r.facebook.com [185.60.219.35] with 32 bytes of data:
Reply from 185.60.219.35: bytes=32 time=2925ms TTL=55
Reply from 185.60.219.35: bytes=32 time=2916ms TTL=55
Reply from 185.60.219.35: bytes=32 time=2935ms TTL=55
Reply from 185.60.219.35: bytes=32 time=2986ms TTL=55

Ping statistics for 185.60.219.35:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2916ms, Maximum = 2986ms, Average = 2940ms

C:\>tracert www.facebook.com

Tracing route to star-mini.c10r.facebook.com [185.60.219.35]
over a maximum of 30 hops:

1 18 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * 3468 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 41 ms 42 ms 42 ms 169-1-21-80.ip.afrihost.co.za [169.1.21.80]
6 41 ms 44 ms 44 ms ae7.br02.jnb1.tfbnw.net [157.240.64.196]
7 42 ms 41 ms 43 ms po102.psw03.jnb1.tfbnw.net [157.240.41.251]
8 40 ms 41 ms 41 ms 173.252.67.115
9 41 ms 42 ms 40 ms 185.60.219.35

Trace complete.
 
What is happening in the South? Terrible speed and many pages fail to load. 8Mb/s Uncapped Premium ADSL. Bellville, Western Cape.

ping www.afrihost.com

Pinging www.afrihost.com [104.20.31.244] with 32 bytes of data:
Reply from 104.20.31.244: bytes=32 time=2963ms TTL=58
Reply from 104.20.31.244: bytes=32 time=2965ms TTL=58
Reply from 104.20.31.244: bytes=32 time=2952ms TTL=58
Reply from 104.20.31.244: bytes=32 time=3039ms TTL=58

Ping statistics for 104.20.31.244:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2952ms, Maximum = 3039ms, Average = 2979ms

C:\>tracert www.afrihost.com

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

1 1 ms 2 ms 3 ms 192.168.1.1
2 * * * Request timed out.
3 2801 ms 2796 ms 2797 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
4 2832 ms 2882 ms 2834 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 2852 ms 2860 ms 2860 ms cloudflare.ixp.capetown [196.10.140.198]
6 2834 ms 2851 ms 2869 ms 104.20.30.244

Trace complete.

C:\>ping www.facebook.com

Pinging star-mini.c10r.facebook.com [185.60.219.35] with 32 bytes of data:
Reply from 185.60.219.35: bytes=32 time=2925ms TTL=55
Reply from 185.60.219.35: bytes=32 time=2916ms TTL=55
Reply from 185.60.219.35: bytes=32 time=2935ms TTL=55
Reply from 185.60.219.35: bytes=32 time=2986ms TTL=55

Ping statistics for 185.60.219.35:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2916ms, Maximum = 2986ms, Average = 2940ms

C:\>tracert www.facebook.com

Tracing route to star-mini.c10r.facebook.com [185.60.219.35]
over a maximum of 30 hops:

1 18 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * 3468 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 41 ms 42 ms 42 ms 169-1-21-80.ip.afrihost.co.za [169.1.21.80]
6 41 ms 44 ms 44 ms ae7.br02.jnb1.tfbnw.net [157.240.64.196]
7 42 ms 41 ms 43 ms po102.psw03.jnb1.tfbnw.net [157.240.41.251]
8 40 ms 41 ms 41 ms 173.252.67.115
9 41 ms 42 ms 40 ms 185.60.219.35

Trace complete.

Not a general issue as far as I am aware. Can you please ping bras.afrihost.com so we can see the response from the exchange?
 
Not a general issue as far as I am aware. Can you please ping bras.afrihost.com so we can see the response from the exchange?

There has been a big improvement since last night, but it still not back to normal.

ping bras.afrihost.com

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=1493ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2167ms TTL=63
Request timed out.
Request timed out.

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 1493ms, Maximum = 2167ms, Average = 1830ms
 
Last edited:
There has been a big improvement since last night, but it still not back to normal.

ping bras.afrihost.com

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=1493ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2167ms TTL=63
Request timed out.
Request timed out.

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 1493ms, Maximum = 2167ms, Average = 1830ms

These seems to indicate the there is congestion on your local exchange. Latency that high is bound to create some poor experiences :(
 
Is there anything Afrihost can do to help improve the situation? This is something that has only cropped up recently.

Exchange congestion is tricky and unfortunate. :( A fix relies heavily on exchange infrastructure upgrades conducted by Openserve that no ISP really has any control over. With that being said, when congestion is detected a fix is generally planned by Openserve. This can be super frustrating, though, and sometimes the wait can sometimes be excruciating. Have you checked if you have any Fibre or Fixed Wireless coverage in your area?
 
Exchange congestion is tricky and unfortunate. :( A fix relies heavily on exchange infrastructure upgrades conducted by Openserve that no ISP really has any control over. With that being said, when congestion is detected a fix is generally planned by Openserve. This can be super frustrating, though, and sometimes the wait can sometimes be excruciating. Have you checked if you have any Fibre or Fixed Wireless coverage in your area?

The only fixed wireless is LTE. Our suburb has reached it's qualifying interested parties target for VUMATEL to lay fibre, and I believe it is planned that they will be doing it hopefully in the near future. The strange thing is that I am basically right next to a major telkom building where the Openserve vehicles operate from... :)
 
The only fixed wireless is LTE. Our suburb has reached it's qualifying interested parties target for VUMATEL to lay fibre, and I believe it is planned that they will be doing it hopefully in the near future. The strange thing is that I am basically right next to a major telkom building where the Openserve vehicles operate from... :)

Openserve does generally keep a close eye on the performance levels, and do plan upgrades on Exchanges to ensure that everyone on the Exchange has the best connection possible.
 
Openserve does generally keep a close eye on the performance levels, and do plan upgrades on Exchanges to ensure that everyone on the Exchange has the best connection possible.

I am happy that this evening everything seems back to normal :)

ping bras.afrihost.com

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=26ms 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 = 23ms, Maximum = 26ms, Average = 24ms
 
I am happy that this evening everything seems back to normal :)

ping bras.afrihost.com

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=26ms 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 = 23ms, Maximum = 26ms, Average = 24ms

Awesome! :D I'm really happy to hear that! :) If there is any change, please let me know!
 
Why is it that MechWarrior Online always has an issue connecting only at night and only when using Afrihost Uncapped account?
 
Why is it that MechWarrior Online always has an issue connecting only at night and only when using Afrihost Uncapped account?

That's the first I am hearing about it - though I'm also not familiar with the game.

Have you run any general tests we can look at?
 
I'll try run some tonight. Like what though? What about process of elimination? Example: If it doesn't work properly on Afrihost Uncapped but works on Afrihost Free 1GB or WebAfrica, is that fine or do you want ping tests too?

When I Have issue at night with MechWarrior, I don't notice and internet slowness or anything, like YouTube and websites loading is all fine and good. It's just that during the day MechWarrior will connect fine but at night around 6PM onwards, connecting will be extremely slow or just buggy and there will be lag in matches. The funny thing is that a friend I play with who is on Afrihost Capped does not have this issue at all.
 
I'll try run some tonight. Like what though? What about process of elimination? Example: If it doesn't work properly on Afrihost Uncapped but works on Afrihost Free 1GB or WebAfrica, is that fine or do you want ping tests too?

When I Have issue at night with MechWarrior, I don't notice and internet slowness or anything, like YouTube and websites loading is all fine and good. It's just that during the day MechWarrior will connect fine but at night around 6PM onwards, connecting will be extremely slow or just buggy and there will be lag in matches. The funny thing is that a friend I play with who is on Afrihost Capped does not have this issue at all.

I think a traceroute to a relevant server is definitely needed, so we can see where the traffic is going and how it's performing.
 
I think a traceroute to a relevant server is definitely needed, so we can see where the traffic is going and how it's performing.

I can't seem to be able to isolate an IP address for any of the servers I'm connecting to. Using Microsoft's TCPView, it gives me an IP but that's only for when the game connects initially. When in a match, it just seems to list UDP with a port number that's open to any IP. No IP listing.

Also, is it normal for an Uncapped Premium 8MB to be shaped this much, even when I've only used around 185GB so far? For some reason, all day yesterday I couldn't download anything off the Play Store it would takes ages just to download a 10MB app but now this morning it's fine? Was there an issue with the Play Store yesterday or...? It's so weird because if I went on my PC and tried to download something like Nvidia drivers, then it would be full speed.

Also, in ClientZone it says that I'm currently on 8Mbps Uncapped DSL. Doesn't say anything about Premium but when I go to the Edit Package window, 8Mbps under the Premium Uncapped section is missing. So I assume I am on Uncapped Premium?

EDIT: Never mind, as of 9:38AM Play Store download speed is basically zero.
 
Last edited:
Top
Sign up to the MyBroadband newsletter
X