Afrihost Business Uncapped Feedback

wingnut771 · May 4, 2014

Kayoss said:
Quick question..

Are the contention ratios the same for the business uncapped and the capped accounts? I would like to sign up but i'm not sure what's better as I would probably spend the same amount on capped data as I would for a business uncapped account..

This is the million dollar question.

AfriMan · May 5, 2014

TEXTILE GUY said:
Any comment with respect to pricing as repoerted in feb this year

http://mybroadband.co.za/vb/showthread.php/614180-Where-are-Afrihost-s-price-cuts

We're always revising our pricing structures, but for the moment Uncapped prices are going to remain the same. We redeploying what clients would have received in savings to buying substantial capacity from Telkom for our national DSL network. We're still waiting for this to be delivered by Telkom, over and above what we already ordered last year.

AfriMan · May 5, 2014

RoMark said:
Watching the MotoGP via SuperSport and the uncapped account is not great.
Buffers for 15 -30 seconds every minute or so.
AH capped account buffers for less than a second every 2 -3 minutes.
IS capped account almost the same AH capped account, but buffers a bit longer for me.

Both capped accounts at 4Mbps speeds and Business uncapped at 2Mbps.

I know there have been problems with Supersport, I don't know if any progress was made on this. From the client's I've chatted, it seems that some popular streams seem to have issues, cos other streams seem to be fine.

AfriMan · May 5, 2014

Kayoss said:
Quick question..

Are the contention ratios the same for the business uncapped and the capped accounts? I would like to sign up but i'm not sure what's better as I would probably spend the same amount on capped data as I would for a business uncapped account..

Business and Capped are essentially the same accounts - drawn from the same data pool. Although we try not to work with contention ratios, cos they fluctuate from minute to minute, they would be the same in that instance.

Bursty-dude · May 5, 2014

Still no feedback from Telkom or Afrihost and ticket on Telkom website is closed as they obviously decided again that the fault has been rectified.....

This is not what I am paying over a grand a month for. End of May this issue is fixed, or I cancel my ADSL, Mifi and web hosting and go look elsewhere. Case closed.

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=57 time=15 ms
Request timeout for icmp_seq 2
64 bytes from 197.242.144.102: icmp_req=3 ttl=57 time=15 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=57 time=15 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=57 time=15 ms

ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=44 time=189 ms
Request timeout for icmp_seq 2
64 bytes from 8.8.8.8: icmp_req=3 ttl=44 time=189 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=44 time=240 ms
Request timeout for icmp_seq 5

Trace Test:

traceroute -n 197.242.144.102

1 192.168.0.1 1 ms 1 ms 1 ms
2 105.236.11.1 10 ms 10 ms 10 ms
3 41.181.178.7 15 ms 14 ms 15 ms
4 196.44.0.1 16 ms 14 ms 16 ms
5 196.44.31.9 15 ms 15 ms 15 ms
6 41.181.165.1 14 ms 13 ms
196.44.31.9 16 ms
7 196.44.31.9 16 ms
196.31.220.6 16 ms 15 ms
8 196.31.220.6 16 ms
196.31.220.2 15 ms 15 ms
9 196.31.220.2 16 ms
196.31.63.2 13 ms 14 ms
10 196.31.63.2 15 ms
196.30.42.1 14 ms 15 ms
11 196.30.42.1 14 ms
197.242.144.1 16 ms 15 ms
12 197.242.144.1 15 ms

traceroute -n 8.8.8.8

1 192.168.0.1 1 ms 1 ms 1 ms
2 105.236.11.1 9 ms 10 ms 11 ms
3 41.181.178.8 13 ms 14 ms 14 ms
4 41.181.165.1 13 ms
196.44.31.9 48 ms 14 ms
5 72.14.194.7 18 ms
41.181.165.1 28 ms 13 ms
6 72.14.194.7 33 ms 18 ms

DNS Test:

nslookup www.afrihost.com

Name: www.afrihost.com
Address: 197.242.144.102

nslookup www.google.com

Name: www.google.com
Address: 173.194.34.114
Name: www.google.com
Address: 173.194.34.112
Name: www.google.com
Address: 173.194.34.116
Name: www.google.com
Address: 173.194.34.113
Name: www.google.com
Address: 173.194.34.115

nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN

Zertop's "Is it my Line" Results
Basic Report:

Your average ping was 24ms
Your maximum ping was 294ms

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 serious intermittent fault on the line. This could be a cause of an issue. Please post the results (at the end of the program) into the forum for advice.

Detailed Report

Code:

Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 105.236.11.193 with 32 bytes of data:
Reply from 105.236.11.193: bytes=32 time=14ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=14ms TTL=254
Reply from 105.236.11.193: bytes=32 time=14ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=14ms TTL=254
Reply from 105.236.11.193: bytes=32 time=14ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=42ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=294ms TTL=254
Reply from 105.236.11.193: bytes=32 time=36ms TTL=254
Reply from 105.236.11.193: bytes=32 time=14ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=14ms TTL=254
Reply from 105.236.11.193: bytes=32 time=14ms TTL=254

Ping statistics for 105.236.11.193:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 13ms, Maximum = 294ms, Average = 24ms
 
2014/05/05 13:41:31.85

AfriMan · May 5, 2014

Bursty-dude said:
Still no feedback from Telkom or Afrihost and ticket on Telkom website is closed as they obviously decided again that the fault has been rectified.....

This is not what I am paying over a grand a month for. End of May this issue is fixed, or I cancel my ADSL, Mifi and web hosting and go look elsewhere. Case closed.

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=57 time=15 ms
Request timeout for icmp_seq 2
64 bytes from 197.242.144.102: icmp_req=3 ttl=57 time=15 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=57 time=15 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=57 time=15 ms

ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=44 time=189 ms
Request timeout for icmp_seq 2
64 bytes from 8.8.8.8: icmp_req=3 ttl=44 time=189 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=44 time=240 ms
Request timeout for icmp_seq 5

Trace Test:

traceroute -n 197.242.144.102

1 192.168.0.1 1 ms 1 ms 1 ms
2 105.236.11.1 10 ms 10 ms 10 ms
3 41.181.178.7 15 ms 14 ms 15 ms
4 196.44.0.1 16 ms 14 ms 16 ms
5 196.44.31.9 15 ms 15 ms 15 ms
6 41.181.165.1 14 ms 13 ms
196.44.31.9 16 ms
7 196.44.31.9 16 ms
196.31.220.6 16 ms 15 ms
8 196.31.220.6 16 ms
196.31.220.2 15 ms 15 ms
9 196.31.220.2 16 ms
196.31.63.2 13 ms 14 ms
10 196.31.63.2 15 ms
196.30.42.1 14 ms 15 ms
11 196.30.42.1 14 ms
197.242.144.1 16 ms 15 ms
12 197.242.144.1 15 ms

traceroute -n 8.8.8.8

1 192.168.0.1 1 ms 1 ms 1 ms
2 105.236.11.1 9 ms 10 ms 11 ms
3 41.181.178.8 13 ms 14 ms 14 ms
4 41.181.165.1 13 ms
196.44.31.9 48 ms 14 ms
5 72.14.194.7 18 ms
41.181.165.1 28 ms 13 ms
6 72.14.194.7 33 ms 18 ms

DNS Test:

nslookup www.afrihost.com

Name: www.afrihost.com
Address: 197.242.144.102

nslookup www.google.com

Name: www.google.com
Address: 173.194.34.114
Name: www.google.com
Address: 173.194.34.112
Name: www.google.com
Address: 173.194.34.116
Name: www.google.com
Address: 173.194.34.113
Name: www.google.com
Address: 173.194.34.115

nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN

View attachment 116582

View attachment 116584

Zertop's "Is it my Line" Results
Basic Report:

Your average ping was 24ms
Your maximum ping was 294ms

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 serious intermittent fault on the line. This could be a cause of an issue. Please post the results (at the end of the program) into the forum for advice.

Detailed Report

Code:

Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) Pinging 105.236.11.193 with 32 bytes of data: Reply from 105.236.11.193: bytes=32 time=14ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=14ms TTL=254 Reply from 105.236.11.193: bytes=32 time=14ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=14ms TTL=254 Reply from 105.236.11.193: bytes=32 time=14ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=42ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=294ms TTL=254 Reply from 105.236.11.193: bytes=32 time=36ms TTL=254 Reply from 105.236.11.193: bytes=32 time=14ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=14ms TTL=254 Reply from 105.236.11.193: bytes=32 time=14ms TTL=254 Ping statistics for 105.236.11.193: Packets: Sent = 30, Received = 30, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 13ms, Maximum = 294ms, Average = 24ms 2014/05/05 13:41:31.85

I feel that you're frustrated, this line issue has been very difficult to try and resolve on your behalf. I think to be fair we've really worked pretty hard to get some progress for you. I'm sorry that you don't agree - which I'm guessing is why you're saying you're going to cancel Mobile and Hosting services. I'd hate to see that happen, but I totally respect where you are coming from.

TEXTILE GUY · May 5, 2014

AfriMan said:
We're always revising our pricing structures, but for the moment Uncapped prices are going to remain the same. We redeploying what clients would have received in savings to buying substantial capacity from Telkom for our national DSL network. We're still waiting for this to be delivered by Telkom, over and above what we already ordered last year.

Thank you for the clarification.

For the record - the performance of this account over the past week - albeit fraught with holidays - has been absolutely stellar.

bullzeye.za · May 5, 2014

This is why I am happy to pay Telkom the extra money for line rental - I don't have to go through a middleman to get my line sorted out if it's having issues. I know the quickest way to escalate a fault and make sure it reaches the right people, and how to get them to hop to when they close a fault badly.

AFAIK all 3rd party line suppliers can log faults, but they are only even looked at the following day by Telkom. I think this is intentional on Telkom's side ( for obvious reasons )

I've not had a day's issue with my Afrihost Business account - Though my downloads are queued in the background and I never really have to worry about *when* something will be done. Sometimes I only get 60kb/s on my downloads, but that's okay because it's all automatic, so it's done by the time I need it.

Bursty-dude said:
Still no feedback from Telkom or Afrihost and ticket on Telkom website is closed as they obviously decided again that the fault has been rectified.....

This is not what I am paying over a grand a month for. End of May this issue is fixed, or I cancel my ADSL, Mifi and web hosting and go look elsewhere. Case closed.

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=57 time=15 ms
Request timeout for icmp_seq 2
64 bytes from 197.242.144.102: icmp_req=3 ttl=57 time=15 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=57 time=15 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=57 time=15 ms

ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=44 time=189 ms
Request timeout for icmp_seq 2
64 bytes from 8.8.8.8: icmp_req=3 ttl=44 time=189 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=44 time=240 ms
Request timeout for icmp_seq 5

Trace Test:

traceroute -n 197.242.144.102

1 192.168.0.1 1 ms 1 ms 1 ms
2 105.236.11.1 10 ms 10 ms 10 ms
3 41.181.178.7 15 ms 14 ms 15 ms
4 196.44.0.1 16 ms 14 ms 16 ms
5 196.44.31.9 15 ms 15 ms 15 ms
6 41.181.165.1 14 ms 13 ms
196.44.31.9 16 ms
7 196.44.31.9 16 ms
196.31.220.6 16 ms 15 ms
8 196.31.220.6 16 ms
196.31.220.2 15 ms 15 ms
9 196.31.220.2 16 ms
196.31.63.2 13 ms 14 ms
10 196.31.63.2 15 ms
196.30.42.1 14 ms 15 ms
11 196.30.42.1 14 ms
197.242.144.1 16 ms 15 ms
12 197.242.144.1 15 ms

traceroute -n 8.8.8.8

1 192.168.0.1 1 ms 1 ms 1 ms
2 105.236.11.1 9 ms 10 ms 11 ms
3 41.181.178.8 13 ms 14 ms 14 ms
4 41.181.165.1 13 ms
196.44.31.9 48 ms 14 ms
5 72.14.194.7 18 ms
41.181.165.1 28 ms 13 ms
6 72.14.194.7 33 ms 18 ms

DNS Test:

nslookup www.afrihost.com

Name: www.afrihost.com
Address: 197.242.144.102

nslookup www.google.com

Name: www.google.com
Address: 173.194.34.114
Name: www.google.com
Address: 173.194.34.112
Name: www.google.com
Address: 173.194.34.116
Name: www.google.com
Address: 173.194.34.113
Name: www.google.com
Address: 173.194.34.115

nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN

View attachment 116582

View attachment 116584

Zertop's "Is it my Line" Results
Basic Report:

Your average ping was 24ms
Your maximum ping was 294ms

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 serious intermittent fault on the line. This could be a cause of an issue. Please post the results (at the end of the program) into the forum for advice.

Detailed Report

Code:

Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) Pinging 105.236.11.193 with 32 bytes of data: Reply from 105.236.11.193: bytes=32 time=14ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=14ms TTL=254 Reply from 105.236.11.193: bytes=32 time=14ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=14ms TTL=254 Reply from 105.236.11.193: bytes=32 time=14ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=42ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=294ms TTL=254 Reply from 105.236.11.193: bytes=32 time=36ms TTL=254 Reply from 105.236.11.193: bytes=32 time=14ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=14ms TTL=254 Reply from 105.236.11.193: bytes=32 time=14ms TTL=254 Ping statistics for 105.236.11.193: Packets: Sent = 30, Received = 30, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 13ms, Maximum = 294ms, Average = 24ms 2014/05/05 13:41:31.85

Bursty-dude · May 5, 2014

Now synced down to 2Mb for no reason at all after having a random disconnect that lasted about 20 minutes....

Seriously now, this is getting beyond being ticked off. Afriman, I know you are all trying your best, but put yourself in my shoes and think what it would be like to sit with this nonsense for the last 14 months.

I am sure something constructive from Telkom's side could have been done in that time. End of May 2014. Tick tock.

wingnut771 · May 5, 2014

Bursty-dude said:
Now synced down to 2Mb for no reason at all after having a random disconnect that lasted about 20 minutes....

View attachment 116682

View attachment 116684

Seriously now, this is getting beyond being ticked off. Afriman, I know you are all trying your best, but put yourself in my shoes and think what it would be like to sit with this nonsense for the last 14 months.

I am sure something constructive from Telkom's side could have been done in that time. End of May 2014. Tick tock.

Try forcing G.dmt mode when your router connects instead of adsl2+. Might give you more stability on your shaky line but i don't think you'll get 6mb tho, maybe 4mb

PurSpyk!! · May 5, 2014

AfriMan said:
I know there have been problems with Supersport, I don't know if any progress was made on this. From the client's I've chatted, it seems that some popular streams seem to have issues, cos other streams seem to be fine.

This issue never seems to get resolved, same with TwitchTV, never wants to play videos. My only issues with Afrihost at the moment.

Rickster · May 5, 2014

This is good, for a 1Meg, too good.

Afriman, Explain please.

AfriMan · May 6, 2014

TEXTILE GUY said:
Thank you for the clarification.

For the record - the performance of this account over the past week - albeit fraught with holidays - has been absolutely stellar.

That's awesome - thanks for putting that on the record

Bursty-dude · May 6, 2014

So...... Hellscum has moved me to a 2Mb profile without any form of feedback or even asking if they can do that. They obviously decided that dropping to a lower speed was better than actually getting a tech out to fix the damn line.
Afrihost has now them for me to be moved back to the 10Mb profile.

I have no words.....

AfriMan · May 6, 2014

bullzeye.za said:
This is why I am happy to pay Telkom the extra money for line rental - I don't have to go through a middleman to get my line sorted out if it's having issues. I know the quickest way to escalate a fault and make sure it reaches the right people, and how to get them to hop to when they close a fault badly.

AFAIK all 3rd party line suppliers can log faults, but they are only even looked at the following day by Telkom. I think this is intentional on Telkom's side ( for obvious reasons )

I've not had a day's issue with my Afrihost Business account - Though my downloads are queued in the background and I never really have to worry about *when* something will be done. Sometimes I only get 60kb/s on my downloads, but that's okay because it's all automatic, so it's done by the time I need it.

I hear what you're saying about lines, but I think most people would rather have the admin of reporting line faults handled elsewhere. I know I don't miss being on hold for ages (I'm particularly averse to pan flutes, I won't lie). Also, if you don't have contacts in Telkom, we're all pretty much in the same boat, so it helps to at least know that someone is doing the heavy lifting for you

AfriMan · May 6, 2014

Bursty-dude said:
Now synced down to 2Mb for no reason at all after having a random disconnect that lasted about 20 minutes....

View attachment 116682

View attachment 116684

Seriously now, this is getting beyond being ticked off. Afriman, I know you are all trying your best, but put yourself in my shoes and think what it would be like to sit with this nonsense for the last 14 months.

I am sure something constructive from Telkom's side could have been done in that time. End of May 2014. Tick tock.

Like I said in my previous post, we have been working with you over that entire time, and we have managed to get some traction for you with Telkom to where it seemed like the issue was resolved. We will keep working on this for you, but I get the feeling that you're saying we're dragging our feet on this, which I think is a little unfair. I know that our Critical Care team especially worked really hard on getting the line working again the last time.

I understand that it's much worse on your end, and that is must be very frustrating, but I always say that we need to trust each other and work together. It's how we've managed to get some success in the past and I hope we'll continue to work together in the same way going forward.

AfriMan · May 6, 2014

PurSpyk!! said:
This issue never seems to get resolved, same with TwitchTV, never wants to play videos. My only issues with Afrihost at the moment.

As far as we can tell, everything possible has been done on the network side, we've gone step by step through the routing to ensure that there is no unnecessary latency introduced. We've also logged with Twitch to get their assistance.

AfriMan · May 6, 2014

Rickster said:
This is good, for a 1Meg, too good.

Afriman, Explain please.

Can't explain that. Is your data 1Mbps but your line is 2Mbps. Maybe a slight wobble in the rate limiting policy

Bursty-dude · May 6, 2014

No. No. No. You guys are definately not dragging your feet at all.
Afrihost has been doing an outstanding job trying to sort this out.

Telkom on the other hand.... This whole bad experience is 100% their fault.

AfriMan · May 6, 2014

Bursty-dude said:
No. No. No. You guys are definately not dragging your feet at all.
Afrihost has been doing an outstanding job trying to sort this out.

Telkom on the other hand.... This whole bad experience is 100% their fault.

Who are you talking to regarding this? Can you drop me a PM so I can make sure our Critical Care team to can jump in on this?

Join the MyBroadband community

Get started

Afrihost Business Uncapped Feedback

Honorary Master

Afrihost Representative

Afrihost Representative

Afrihost Representative

Expert Member

Afrihost Representative

Honorary Master

Expert Member

Expert Member

Honorary Master

Expert Member

EVGA Fanatic

Afrihost Representative

Expert Member

Afrihost Representative

Afrihost Representative

Afrihost Representative

Afrihost Representative

Expert Member

Afrihost Representative