Afrihost Business Uncapped Feedback

blaaislaai · Mar 18, 2014

TheGrove said:
@Afriguy, my downloads speeds are back to 50% again, looks like the earlier fix was temporary.

also 50% here, in CPT

Gatecrasher · Mar 18, 2014

Yes, 50% of line speed and a total inability to stream without start-stop-stutter. But I guess our usual line capacity has been taken away for the capped account freebies. So not only do we not get any benefit from the recent Telkom IPC price cuts, but our service has been hugely degraded too. Not impressed, AH.

DrJohnZoidberg · Mar 18, 2014

Packet loss is fixed but latency still high.

This is from our office:

Rickster · Mar 18, 2014

I know the website says only the southern regions are affected but up here in JHB pings are crazy.

Fudzy · Mar 18, 2014

The speeds in Durban are pants too, the one night I really need the internet and I now have to go in via my phone.

Hunted · Mar 18, 2014

Hi all,

Just my 2 cents.. Also appears that my test download via news servers is not even reaching half my 10Mbps speed.

Speed test shows a slighty better result, but about 300 to 400 kB/s slower than normal. Latency seems fine.

Did Afrihost stabilize the latency possibly by "throttling" download speeds?

Here is my speedtest result

Gatecrasher · Mar 18, 2014

8Mb/s business uncapped. Just appalling.

8-BALL · Mar 18, 2014

initroot · Mar 19, 2014

My speeds seem to be back to normal now. Will test during the day. Hope im not premature..

patrick123 · Mar 19, 2014

wingnut771 said:
Some packet loss?

Can you ping -n 100 105.236.1.65 and post the results?

Code:

Pinging 105.236.1.65 with 32 bytes of data:
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=10ms TTL=254
Reply from 105.236.1.65: bytes=32 time=10ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=7ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=9ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=9ms TTL=254
Reply from 105.236.1.65: bytes=32 time=9ms TTL=254
Reply from 105.236.1.65: bytes=32 time=10ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=12ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=17ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=9ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=9ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=9ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=10ms TTL=254
Reply from 105.236.1.65: bytes=32 time=9ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=9ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=10ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=9ms TTL=254
Reply from 105.236.1.65: bytes=32 time=9ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=10ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=9ms TTL=254
Reply from 105.236.1.65: bytes=32 time=10ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254

Ping statistics for 105.236.1.65:
    Packets: Sent = 59, Received = 59, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 7ms, Maximum = 17ms, Average = 8ms

wingnut771 · Mar 19, 2014

Nothing wrong there.

patrick123 said:

Code:

Pinging 105.236.1.65 with 32 bytes of data:
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=10ms TTL=254
Reply from 105.236.1.65: bytes=32 time=10ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=7ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=9ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=9ms TTL=254
Reply from 105.236.1.65: bytes=32 time=9ms TTL=254
Reply from 105.236.1.65: bytes=32 time=10ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=12ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=17ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=9ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=9ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=9ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=10ms TTL=254
Reply from 105.236.1.65: bytes=32 time=9ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=9ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=10ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=9ms TTL=254
Reply from 105.236.1.65: bytes=32 time=9ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=10ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254
Reply from 105.236.1.65: bytes=32 time=9ms TTL=254
Reply from 105.236.1.65: bytes=32 time=10ms TTL=254
Reply from 105.236.1.65: bytes=32 time=8ms TTL=254

Ping statistics for 105.236.1.65:
    Packets: Sent = 59, Received = 59, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 7ms, Maximum = 17ms, Average = 8ms

hammell · Mar 19, 2014

Still bad:

Tracing route to www.iol.co.za [196.38.8.254]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.0.1
2 318 ms 248 ms 264 ms 105-236-9-65-esr-lo.mtnbusiness.co.za [105.236.9
.65]
3 265 ms 241 ms 206 ms 41.181.221.254
4 326 ms 347 ms 343 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
5 346 ms 563 ms 611 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 310 ms 241 ms 152 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]

7 416 ms 446 ms 468 ms 196.44.0.74
8 301 ms 192 ms 141 ms 41-208-29-209.mtnns.net [41.208.29.209]
9 84 ms 49 ms 77 ms 168.209.6.13
10 68 ms 35 ms 36 ms 168.209.100.213
11 300 ms 69 ms 50 ms csw5-pkl-tg2-7.ip.isnet.net [168.209.1.188]
12 81 ms 73 ms 57 ms 196.38.8.254
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.

Taranis · Mar 19, 2014

'LIVE' 24/7 support is actually dead.

savage · Mar 19, 2014

Taranis said:
'LIVE' 24/7 support is actually dead.

Must be their IPC capacity shortage in CPT

PurSpyk!! · Mar 19, 2014

Taranis said:
'LIVE' 24/7 support is actually dead.

Its never worked that well. Strange that once again no reps on these forums today, and we sit with speed issues.

TheGrove · Mar 19, 2014

PurSpyk!! said:
Its never worked that well. Strange that once again no reps on these forums today, and we sit with speed issues.

I can imagine they are being hammered with support calls.

I had a lol moment earlier, a chap at work that convinced me to use Afrihost was going on about how I am imagining things and his line with Afrhiost is rock solid and he'll prove it. Teamviews in to his machine and runs a speed test, notices it is a bit slow and then blip, connection lost, his adsl has been down all morning.

xrapidx · Mar 19, 2014

Apparently my account has been cancelled - no sign of refund yet.

i.got~issues · Mar 19, 2014

/sigh

Thank ye godz for backup accounts.

/bigger sigh

EDIT:

You need to revise the resolved part perhaps;

South Region Latency Resolved 18:59, 18 Mar 2014

Resolved

UPDATE 18 March 2014 19:12 We’re seeing the latency normalise. Our Engineers will continue to monitor the situation closely.

We have received reports of increased latency for clients in the South Region (Cape Town, Port Elizabeth and other areas routing though our South Network). Affected clients may receive slow response from internet services. Our network engineers are investigating urgently, and we will post further updates as soon as we receive feedback. We apologise for any inconvenience affected clients may be experiencing.

This is beginning to feel like I am back with OpenWeb.

GarethY · Mar 19, 2014

Why is my 4Mbps account behaving like a 1Mbps account???

GarethY · Mar 19, 2014

Now I can't even load this forum, the afrihost website and a bunch of other sites. Speedtest.net thinks I'm in Maputo and won't even complete a test. I'm using an openweb account to write this post.

Please AH, sort your s**t out. I can't work like this

Join the MyBroadband community

Get started

Afrihost Business Uncapped Feedback

Executive Member

Executive Member

Honorary Master

EVGA Fanatic

Fudzy

Guest

Expert Member

Attachments

Executive Member

Senior Member

Senior Member

Expert Member

Honorary Master

Senior Member

Banned

Expert Member

Expert Member

Expert Member

Honorary Master

Expert Member

Well-Known Member

Well-Known Member