Afrihost New Network Feedback

Status
Not open for further replies.
That's odd though, because by 10pm the load on the network is usually dramatically tapering off.

Are you talking about seconds or milliseconds here? If you're talking about seconds, then it sounds like it's a problem either way and we need to see where this latency is coming from :(

We are talking seconds not milliseconds

I spend most of my data cap on streaming, so from my POV it's really frustrating.:(
Even after many trace routes and ping tests that never truly reflect throughput, in actual fact it only causes more head scratching and frustration.

I really do hope you guys get your network at a place where everyone can have a great internet experience :)
 
We are talking seconds not milliseconds

I spend most of my data cap on streaming, so from my POV it's really frustrating.:(
Even after many trace routes and ping tests that never truly reflect throughput, in actual fact it only causes more head scratching and frustration.

I really do hope you guys get your network at a place where everyone can have a great internet experience :)

We've definitely come to realize that a network isn't something that you just setup once and leave, there is a lot of tweaking and optimization that takes place.

Would you mind testing tonight and letting me know how it goes.
 
I've give up. Internet not usable between 20:00 and 22:00.
Well I am trying to Skype to the UK at the moment and it is just pathetic, Teamviewer shows it can not connect.
PSN also showing no connection.
I gave up a few threads back, its a joke really.
Torrents also blazing fast at 2.5KB/s
 
Facebook, gmail, twitter SO SLOW that it might as well not be working. Also unable to connect to a remote mysql database. Come 22:00, everything is back to normal and fast.
Zertop's LineTool Results
Date/Time: Mon May 16 21:11:53 CAT 2016


Basic Report:


Your packet loss was 3%.
Your average ping was 25ms.
Your maximum ping was 42ms.

You seem to have some packet loss. This indicates an issue on the line.
Looking at your average ping, your line seems to be running perfectly.
Looking at your maximum ping, however, it seems as though there could be a slight intermittent issue on the line. If required, please post the results to a forum post.

Detailed Report:
Code:
Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
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=26ms TTL=63
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
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=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=27ms TTL=63
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
Reply from 155.239.255.250: bytes=32 time=27ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=28ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=42ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=27ms TTL=63
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63

Ping statistics for 155.239.255.250:
    Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
    Minimum = 23ms, Maximum = 42ms, Average = 25ms

Speedtest is fine.


Streaming is fine:
Video ID:T7Jr0u4xxM0
Dimensions:1280 x 720
Resolution:1280 x 720@25
Volume:100%
Stream Host:r1---sn-hfxc-j2ul
Stream Type:https
CPN:U1inevKDyETc6kz9
Mime Type:video/webm; codecs="vp9"
DASH:yes (247/251)
Connection Speed:3585 Kbps
Buffer Health:56.0 s
Dropped Frames:
 
Facebook, gmail, twitter SO SLOW that it might as well not be working. Also unable to connect to a remote mysql database. Come 22:00, everything is back to normal and fast.
Zertop's LineTool Results
Date/Time: Mon May 16 21:11:53 CAT 2016


Basic Report:


Your packet loss was 3%.
Your average ping was 25ms.
Your maximum ping was 42ms.

You seem to have some packet loss. This indicates an issue on the line.
Looking at your average ping, your line seems to be running perfectly.
Looking at your maximum ping, however, it seems as though there could be a slight intermittent issue on the line. If required, please post the results to a forum post.

Detailed Report:
Code:
Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
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=26ms TTL=63
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
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=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Reply from 155.239.255.250: bytes=32 time=27ms TTL=63
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
Reply from 155.239.255.250: bytes=32 time=27ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=28ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=42ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=27ms TTL=63
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63

Ping statistics for 155.239.255.250:
    Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
    Minimum = 23ms, Maximum = 42ms, Average = 25ms

Speedtest is fine.


Streaming is fine:
Video ID:T7Jr0u4xxM0
Dimensions:1280 x 720
Resolution:1280 x 720@25
Volume:100%
Stream Host:r1---sn-hfxc-j2ul
Stream Type:https
CPN:U1inevKDyETc6kz9
Mime Type:video/webm; codecs="vp9"
DASH:yes (247/251)
Connection Speed:3585 Kbps
Buffer Health:56.0 s
Dropped Frames:
YouTube is pulled from Mweb's local Google Cache cluster. So it should not be affected, Afrihost and international traffic are a no go in general lately. Local traffic never has problems.
 
YouTube is pulled from Mweb's local Google Cache cluster. So it should not be affected, Afrihost and international traffic are a no go in general lately. Local traffic never has problems.

International speedtest.


and to add insult to injury, the adverts on the speedtest page does not even load.
 
International speedtest.


and to add insult to injury, the adverts on the speedtest page does not even load.
I also get great latency and speedtest results to the UK and US, but most international services are slow or non existent. So I am hesitant to cancel everything and move to IS ignite. But what a mission to move all my lines back to Telkom. Its the only thing stopping me at the moment.
 
International speedtest.


and to add insult to injury, the adverts on the speedtest page does not even load.

Going to speedtest the same city.

EDIT: using beta.speedtest.net
ping.png

Considering I am in cape Town, that's a ~20ms increase in normal ping, I am also the only one in the household using my net, so should be getting ~8.4Mbps down and 0.8Mbps up.
 
Last edited:
Tested to Rotterdam. :)

5330209122.png
 
Tested to Rotterdam. :)

5330209122.png

Ha, no 8.4Mbps for you or 0.8Mbps!
Though how is your ping lower than mine considering you have to go through Cape Town to go international.

LaraC posted a non-perfect speedtest. I am screenshotting this.
 
Going to speedtest the same city.

EDIT: using beta.speedtest.net
View attachment 362302

Considering I am in cape Town, that's a ~20ms increase in normal ping, I am also the only one in the household using my net, so should be getting ~8.4Mbps down and 0.8Mbps up.

Tried again. I'm also the only one in the household currently using the net. On a 4meg line.
afrihost..jpg
 
Last edited:
Ha, no 8.4Mbps for you or 0.8Mbps!
Though how is your ping lower than mine considering you have to go through Cape Town to go international.

LaraC posted a non-perfect speedtest. I am screenshotting this.
I'm willing to test to another international site. :)
 
Gosh it was difficult to locate until I realized I could drag the map. :p

5330254823.png

How?
5330266320.png
I even got 3 sixes in mine, devil's taunting me. I am going to have to wake up at 4am and do a speedtest, just have to make sure to plug in a LAN cable as well.
 
Mine really bad in Durban. a ping from my Afrihost ADSL to an Afrihost hosted server not reliable:

64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=8 ttl=52 time=94.9 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=9 ttl=52 time=62.7 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=10 ttl=53 time=38.7 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=11 ttl=52 time=85.8 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=12 ttl=52 time=39.0 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=13 ttl=53 time=75.2 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=14 ttl=53 time=39.7 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=15 ttl=53 time=38.0 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=16 ttl=53 time=89.7 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=17 ttl=53 time=74.9 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=18 ttl=52 time=36.2 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=19 ttl=53 time=35.8 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=20 ttl=52 time=40.6 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=21 ttl=53 time=36.4 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=22 ttl=53 time=36.7 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=23 ttl=53 time=64.8 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=24 ttl=53 time=107 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=25 ttl=53 time=35.5 ms
64 bytes from omhhyfmhibns.hosted.co.za (154.0.166.18): icmp_seq=26 ttl=52 time=36.6 ms

Can't even watch Youtube
 
10pm and now everything has turned into a pumpkin.
Oh the joy.
Sites timeout and some open but slowly.
This feels like the MTN network all over again.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X