Afrihost Business Uncapped Feedback

Status
Not open for further replies.
Peps said:
Thank you all.

so if I signup anytime during the month, I'll only get charged R1 as long as I cancel before the 25th - correct?

That won't leave me enough time to test it as I'm away this weekend but will mostly do so next month.

Thanks again.
Click to expand...

You are correct; just note that this R1 special is only for March and does not apply in April
 
HTTP downloading still running between 380KB/s and 420KB/s
 
Peps said:
Thank you all.

so if I signup anytime during the month, I'll only get charged R1 as long as I cancel before the 25th - correct?

That won't leave me enough time to test it as I'm away this weekend but will mostly do so next month.

Thanks again.
Click to expand...

You'll pay R1 for March, whether you cancel or continue onwards to April.
 
Still running without a hitch :D

Thanks Guys
 
Unhappy438 said:
Im pretty sure Afrihost dont use Seacom.
Click to expand...

No they don't, but the EASSY cable Afrihost makes use of was also affected.
All traffic was re-routed onto WACS automatically, but there will be slower throughput because of the extra load, they using QoS Shaping to manage the throughput, so you will at times feel when certain protocols get a lower priority and speed slows down.

But in general the levels are acceptable, Afrihost did not have the dilemma Mweb faced when there SEACOM link went down.

In fact we hardly noticed when the EASSY cable was lost, and you must know that all Afrihost customers was switch over to WACS and many of the effected SEACOM customers bought or took up the Afrihost and Axxess bandwidth to tie them over, so that extra load Afrihost is also managing.

So with the over all picture it isn't to bad.

Local runs at full speed.

International runs near line speed:

MYBB International
Test conducted on 24 March 2013 08:54:03

Download Speed: 5241 kbps (655.1 KB/sec transfer rate)
Upload Speed: 816 kbps (102 KB/sec transfer rate)
Latency: 166 ms


OOKLA Amsterdam
 
Last edited:
Running at 0.30MBs on a 4mb line? I am guessing it is because you are running on mostly WACS and probably have a lot of Seacom refugees but still, eish!
 
We had several reports of slow throughput on Business over the weekend and our team have been monitoring this 24/7 to pin this down.

At this stage we don't believe it's contention, we're still looking into what could have caused issues, it seems to be affecting only certain clients.

We'll be watching closely today and in the coming week to make sure Business clients get the premium unshaped experience they should.
 
Just sorted my 6Mbps Afrihost Business account! So glorious having proper internet access again. Busy downloading a file at 360KB/s, which isn't exactly unshaped, but other factors could be at play. Will update as I use it. It is definitely working well though.

Edit: Torrent improved from 60KB/s to 270KB/s. I won't judge until the Afrihost home page has a green status light though. For all practical purposes the account is working great.
 
Last edited:
AfriMan said:
We had several reports of slow throughput on Business over the weekend and our team have been monitoring this 24/7 to pin this down.

At this stage we don't believe it's contention, we're still looking into what could have caused issues, it seems to be affecting only certain clients.

We'll be watching closely today and in the coming week to make sure Business clients get the premium unshaped experience they should.
Click to expand...

Thank you Afriman, I will continue to provide updated feedback
 
It seems the move to a new DSLAM has solved my congested problem I had with my Exchange.
Still running perfect.

PS C:\Users\Jannie> ping -t 105.236.8.193

Pinging 105.236.8.193 with 32 bytes of data:
Reply from 105.236.8.193: bytes=32 time=7ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=7ms TTL=254
Reply from 105.236.8.193: bytes=32 time=7ms TTL=254
Reply from 105.236.8.193: bytes=32 time=7ms TTL=254
Reply from 105.236.8.193: bytes=32 time=7ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=7ms TTL=254
Reply from 105.236.8.193: bytes=32 time=7ms TTL=254

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



 
Hi Guys

My 4MB uncapped line is now running at barely 1mb again?

Please advise (was fine during working hours)
 
How did you manage to do that? Rather, who/what department did you speak to @ Telkom that had a clue what you were talking about?


jannier said:
It seems the move to a new DSLAM has solved my congested problem I had with my Exchange.
Still running perfect.

PS C:\Users\Jannie> ping -t 105.236.8.193

Pinging 105.236.8.193 with 32 bytes of data:
Reply from 105.236.8.193: bytes=32 time=7ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=7ms TTL=254
Reply from 105.236.8.193: bytes=32 time=7ms TTL=254
Reply from 105.236.8.193: bytes=32 time=7ms TTL=254
Reply from 105.236.8.193: bytes=32 time=7ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=6ms TTL=254
Reply from 105.236.8.193: bytes=32 time=7ms TTL=254
Reply from 105.236.8.193: bytes=32 time=7ms TTL=254

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



Click to expand...
 
C:\Users\lino>ping 8.8.8.8 -t

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=683ms TTL=44
Reply from 8.8.8.8: bytes=32 time=196ms TTL=44
Reply from 8.8.8.8: bytes=32 time=165ms TTL=44
Reply from 8.8.8.8: bytes=32 time=180ms TTL=44
Reply from 8.8.8.8: bytes=32 time=302ms TTL=44
Reply from 8.8.8.8: bytes=32 time=240ms TTL=44
Reply from 8.8.8.8: bytes=32 time=256ms TTL=44
Reply from 8.8.8.8: bytes=32 time=375ms TTL=44
Reply from 8.8.8.8: bytes=32 time=299ms TTL=44
Reply from 8.8.8.8: bytes=32 time=243ms TTL=44
Reply from 8.8.8.8: bytes=32 time=251ms TTL=44
Reply from 8.8.8.8: bytes=32 time=228ms TTL=44
Reply from 8.8.8.8: bytes=32 time=281ms TTL=44
Reply from 8.8.8.8: bytes=32 time=261ms TTL=44
Reply from 8.8.8.8: bytes=32 time=362ms TTL=44
Reply from 8.8.8.8: bytes=32 time=346ms TTL=44
Reply from 8.8.8.8: bytes=32 time=334ms TTL=44
Reply from 8.8.8.8: bytes=32 time=307ms TTL=44
Reply from 8.8.8.8: bytes=32 time=215ms TTL=44
Reply from 8.8.8.8: bytes=32 time=384ms TTL=44



C:\Users\linor>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Billion.810VGTX [192.168.0.2]
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 780 ms 773 ms 656 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.
 
Test conducted on 25/3/2013 21:05:10

Download Speed: 440 kbps (55 KB/sec transfer rate)
Upload Speed: 242 kbps (30.3 KB/sec transfer rate)
Latency: 625 ms
 
Lino said:
What is going on?
Click to expand...

My account is working fine. Not exactly 5+Mbps, but it's acceptable for a period of reduced capacity. Other members of my household could be using bandwidth too.

2599443855.png


The Clientzone tells me I'm receiving '100% realtime speed' with 'no shaping applied'.
 
My line is running still full spead.
Lino you might have exchange congestion, doing a ping to where every does not help.
Do a trace route to see wher the problem lies.

@blunt, i opened a support ticket with telkom asking for a technician.
I kept a log for a week long with random times of the day showing the exchange congestion.
Tracert, speedtests and exchange/gateway pings
The technician passed the info to a specialist who investigated my line at dslam and then moved it to a less congested one.

I knew what was going on, how to keep the logs as proof and what to say, the rest just happend.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X