Afrihost Business Uncapped Feedback - 2

Status
Not open for further replies.
AfriGenie said:
Much appreciated!
Click to expand...

Rebooted rooter, and speeds are slower

Last Result:
Download Speed: 4462 kbps (557.8 KB/sec transfer rate)
Upload Speed: 649 kbps (81.1 KB/sec transfer rate)
Latency: 40 ms
Tuesday, 07 April 2015 18:06

This is a local speed test, look at the results, everything way below what thye should be. The piong uised to be around 15ms. Seriously this is becoming very irritating, as we pay for a service which is clearly not performing as advertised.

Speedtest to JHB

Last Result:
Download Speed: 5672 kbps (709 KB/sec transfer rate)
Upload Speed: 711 kbps (88.9 KB/sec transfer rate)
Latency: 177 ms
Tuesday, 07 April 2015 18:10

Latecy of 177ms, madness!
 
Last edited:
PurSpyk!! said:
Rebooted rooter, and speeds are slower

Last Result:
Download Speed: 4462 kbps (557.8 KB/sec transfer rate)
Upload Speed: 649 kbps (81.1 KB/sec transfer rate)
Latency: 40 ms
Tuesday, 07 April 2015 18:06

This is a local speed test, look at the results, everything way below what thye should be. The piong uised to be around 15ms. Seriously this is becoming very irritating, as we pay for a service which is clearly not performing as advertised.

Speedtest to JHB

Last Result:
Download Speed: 5672 kbps (709 KB/sec transfer rate)
Upload Speed: 711 kbps (88.9 KB/sec transfer rate)
Latency: 177 ms
Tuesday, 07 April 2015 18:10

Latecy of 177ms, madness!
Click to expand...

It could be that your line simply isn't stable enough at the high sync?
 
Connection performing 100% at the moment. First time in months I could watch a short Wistia 4min video without buffering... Holding thumbs this lasts.
 
AfriGuy said:
It could be that your line simply isn't stable enough at the high sync?
Click to expand...

I doubt it, my line has been syncing at 10Mbps for a long time already, why would the speed nbow be less than when i was on a 8Mbps account. I see I am not the only one complaining, so it cannot be an issue on my side.
 
PurSpyk!! said:
I doubt it, my line has been syncing at 10Mbps for a long time already, why would the speed nbow be less than when i was on a 8Mbps account. I see I am not the only one complaining, so it cannot be an issue on my side.
Click to expand...

I remember asking about threaded downloads, not sure if you've managed to test that yet?
In any case, the sync profile may be stable for 10Mbps but throughput could be an issue through to the DP/ DSLAM.
 
AfriGenie said:
:(

That latency and speed is definitely not good. My apologies, but the screenshot is a bit small, but is the latency starting on the second hop already? Are you consistently getting those latencies and speeds in the evenings?
Click to expand...
Pretty much all day, nzbs were running at half speed all day.
 
Rickster said:
Try this:


1)Use Saix.net for speedtests.
2)Use the telkom guest account then speedtest.

Post findings here.
Click to expand...

This is on the Afrihost Account:
Last Result:
Download Speed: 8698 kbps (1087.3 KB/sec transfer rate)
Upload Speed: 821 kbps (102.6 KB/sec transfer rate)
Latency: 11 ms
Tuesday, 07 April 2015 19:41

Windows Updates refuse to download
 
PurSpyk!! said:
This is on the Afrihost Account:
Last Result:
Download Speed: 8698 kbps (1087.3 KB/sec transfer rate)
Upload Speed: 821 kbps (102.6 KB/sec transfer rate)
Latency: 11 ms
Tuesday, 07 April 2015 19:41

Windows Updates refuse to download
Click to expand...

These results are normal for a 10Mbps line, are other downloads working?
 
I've downgraded my 20MB business it to a capped account. Will try out other ISPs next month to see if the grass is greener.
 
Pings are a bit jumpy atm:

Pinging ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150] with 32 bytes of data:

Reply from 41.181.53.150: bytes=32 time=20ms TTL=59
Reply from 41.181.53.150: bytes=32 time=14ms TTL=59
Reply from 41.181.53.150: bytes=32 time=15ms TTL=59
Reply from 41.181.53.150: bytes=32 time=32ms TTL=59
Reply from 41.181.53.150: bytes=32 time=27ms TTL=59
Reply from 41.181.53.150: bytes=32 time=22ms TTL=59
Reply from 41.181.53.150: bytes=32 time=22ms TTL=59
Reply from 41.181.53.150: bytes=32 time=30ms TTL=59
Reply from 41.181.53.150: bytes=32 time=60ms TTL=59
Reply from 41.181.53.150: bytes=32 time=28ms TTL=59
Reply from 41.181.53.150: bytes=32 time=27ms TTL=59
Reply from 41.181.53.150: bytes=32 time=24ms TTL=59
Reply from 41.181.53.150: bytes=32 time=23ms TTL=59
Reply from 41.181.53.150: bytes=32 time=30ms TTL=59
Reply from 41.181.53.150: bytes=32 time=33ms TTL=59
Reply from 41.181.53.150: bytes=32 time=30ms TTL=59
Reply from 41.181.53.150: bytes=32 time=42ms TTL=59
Reply from 41.181.53.150: bytes=32 time=39ms TTL=59
Reply from 41.181.53.150: bytes=32 time=26ms TTL=59
Reply from 41.181.53.150: bytes=32 time=39ms TTL=59

Pinging webafrica.co.za [41.185.61.34] with 32 bytes of data:
Reply from 41.185.61.34: bytes=32 time=63ms TTL=52
Reply from 41.185.61.34: bytes=32 time=32ms TTL=52
Reply from 41.185.61.34: bytes=32 time=32ms TTL=52
Reply from 41.185.61.34: bytes=32 time=43ms TTL=52
Reply from 41.185.61.34: bytes=32 time=33ms TTL=52
Reply from 41.185.61.34: bytes=32 time=29ms TTL=52
Reply from 41.185.61.34: bytes=32 time=28ms TTL=52
Reply from 41.185.61.34: bytes=32 time=13ms TTL=52
Reply from 41.185.61.34: bytes=32 time=22ms TTL=52
Reply from 41.185.61.34: bytes=32 time=13ms TTL=52
Reply from 41.185.61.34: bytes=32 time=16ms TTL=52
Reply from 41.185.61.34: bytes=32 time=17ms TTL=52
Reply from 41.185.61.34: bytes=32 time=28ms TTL=52
Reply from 41.185.61.34: bytes=32 time=43ms TTL=52
Reply from 41.185.61.34: bytes=32 time=37ms TTL=52
Reply from 41.185.61.34: bytes=32 time=37ms TTL=52

Tracing route to ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms dsldevice.domain.name [192.168.0.2]
2 10 ms 8 ms 9 ms 105-236-10-129-esr-lo.mtnbusiness.co.za [105.236.10.129]
3 31 ms 31 ms 32 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]


Tracing route to webafrica.co.za [41.185.61.34]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms dsldevice.domain.name [192.168.0.2]
2 9 ms 9 ms 9 ms 105-236-10-129-esr-lo.mtnbusiness.co.za [105.236.10.129]
3 33 ms 29 ms 32 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
4 73 ms 45 ms 45 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 17 ms 17 ms 18 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 25 ms 27 ms 27 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
7 15 ms 17 ms 21 ms 196.44.0.74
8 32 ms 32 ms 32 ms 41-208-29-209.mtnns.net [41.208.29.209]
9 49 ms 48 ms 47 ms css2-ctn-gi0-1.ip.isnet.net [168.209.2.15]
10 20 ms 22 ms 25 ms mi-za-cpt-br1-gi0-3-108.ip.isnet.net [168.209.28.42]
11 15 ms 13 ms 14 ms 197.96.154.190
12 44 ms 39 ms 42 ms 197.96.154.191
13 18 ms 19 ms 22 ms wnls-whmcs-web01.wadns.net [41.185.61.34]
 
Loppas said:
Pings are a bit jumpy atm:

Pinging ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150] with 32 bytes of data:

Reply from 41.181.53.150: bytes=32 time=20ms TTL=59
Reply from 41.181.53.150: bytes=32 time=14ms TTL=59
Reply from 41.181.53.150: bytes=32 time=15ms TTL=59
Reply from 41.181.53.150: bytes=32 time=32ms TTL=59
Reply from 41.181.53.150: bytes=32 time=27ms TTL=59
Reply from 41.181.53.150: bytes=32 time=22ms TTL=59
Reply from 41.181.53.150: bytes=32 time=22ms TTL=59
Reply from 41.181.53.150: bytes=32 time=30ms TTL=59
Reply from 41.181.53.150: bytes=32 time=60ms TTL=59
Reply from 41.181.53.150: bytes=32 time=28ms TTL=59
Reply from 41.181.53.150: bytes=32 time=27ms TTL=59
Reply from 41.181.53.150: bytes=32 time=24ms TTL=59
Reply from 41.181.53.150: bytes=32 time=23ms TTL=59
Reply from 41.181.53.150: bytes=32 time=30ms TTL=59
Reply from 41.181.53.150: bytes=32 time=33ms TTL=59
Reply from 41.181.53.150: bytes=32 time=30ms TTL=59
Reply from 41.181.53.150: bytes=32 time=42ms TTL=59
Reply from 41.181.53.150: bytes=32 time=39ms TTL=59
Reply from 41.181.53.150: bytes=32 time=26ms TTL=59
Reply from 41.181.53.150: bytes=32 time=39ms TTL=59

Pinging webafrica.co.za [41.185.61.34] with 32 bytes of data:
Reply from 41.185.61.34: bytes=32 time=63ms TTL=52
Reply from 41.185.61.34: bytes=32 time=32ms TTL=52
Reply from 41.185.61.34: bytes=32 time=32ms TTL=52
Reply from 41.185.61.34: bytes=32 time=43ms TTL=52
Reply from 41.185.61.34: bytes=32 time=33ms TTL=52
Reply from 41.185.61.34: bytes=32 time=29ms TTL=52
Reply from 41.185.61.34: bytes=32 time=28ms TTL=52
Reply from 41.185.61.34: bytes=32 time=13ms TTL=52
Reply from 41.185.61.34: bytes=32 time=22ms TTL=52
Reply from 41.185.61.34: bytes=32 time=13ms TTL=52
Reply from 41.185.61.34: bytes=32 time=16ms TTL=52
Reply from 41.185.61.34: bytes=32 time=17ms TTL=52
Reply from 41.185.61.34: bytes=32 time=28ms TTL=52
Reply from 41.185.61.34: bytes=32 time=43ms TTL=52
Reply from 41.185.61.34: bytes=32 time=37ms TTL=52
Reply from 41.185.61.34: bytes=32 time=37ms TTL=52

Tracing route to ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms dsldevice.domain.name [192.168.0.2]
2 10 ms 8 ms 9 ms 105-236-10-129-esr-lo.mtnbusiness.co.za [105.236.10.129]
3 31 ms 31 ms 32 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]


Tracing route to webafrica.co.za [41.185.61.34]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms dsldevice.domain.name [192.168.0.2]
2 9 ms 9 ms 9 ms 105-236-10-129-esr-lo.mtnbusiness.co.za [105.236.10.129]
3 33 ms 29 ms 32 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
4 73 ms 45 ms 45 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 17 ms 17 ms 18 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 25 ms 27 ms 27 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
7 15 ms 17 ms 21 ms 196.44.0.74
8 32 ms 32 ms 32 ms 41-208-29-209.mtnns.net [41.208.29.209]
9 49 ms 48 ms 47 ms css2-ctn-gi0-1.ip.isnet.net [168.209.2.15]
10 20 ms 22 ms 25 ms mi-za-cpt-br1-gi0-3-108.ip.isnet.net [168.209.28.42]
11 15 ms 13 ms 14 ms 197.96.154.190
12 44 ms 39 ms 42 ms 197.96.154.191
13 18 ms 19 ms 22 ms wnls-whmcs-web01.wadns.net [41.185.61.34]
Click to expand...


Ping is definitely inconsistent there. Since our team are making some major changes over the next few days, I think it would be best to monitor for now and see how their changes impact your experience.
 
Quad! said:
With Business Optimization Active...
http://i.imgur.com/AIZDyJR.jpg


With Business Optimization Deactivated...
http://i.imgur.com/LqeqLO1.jpg


And my Current Recent Business Optimization Deactivated...
http://i.imgur.com/6vcPsBm.jpg


Have been waiting the hole day now and even at night time I still get Major Packet Loss!!
This is Ridiculous:mad:
Click to expand...

Seems like the packet loss is consistent whether you have the setting on or off, so I don't think it's the shaping rules on Optimisation causing the packet loss (and they should not affect a realtime traceroute).

I know that we are rolling our changes (which have already started) over the next few days. I'm not sure at what time these are being rolled out but it may affect the overall performance while they are being pushed to the devices/hardware.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X