Afrihost Business Uncapped Feedback

wingnut771 · Mar 28, 2014

AfriGuy said:
Have you brought this up with our team?

This was a while back, I have since moved my line back to Telkom.

As I'm still paying the 10mb price for my 4mb line, I tried to transfer it back through client zone (anything not to phone 10210

) but it gave me some "number already exists" error, so I went through my old WA clientzone (I also didn't want to phone your support and sit in the queue).

WA charge R300 tho, so when that's complete I will move it back (I am a patient man

). Hopefully by then your support crisis will be over as I'm interested in moving bacl to you as you're R250

AfriGuy · Mar 28, 2014

wingnut771 said:
This was a while back, I have since moved my line back to Telkom.

As I'm still paying the 10mb price for my 4mb line, I tried to transfer it back through client zone (anything not to phone 10210 ) but it gave me some "number already exists" error, so I went through my old WA clientzone (I also didn't want to phone your support and sit in the queue).

WA charge R300 tho, so when that's complete I will move it back (I am a patient man ). Hopefully by then your support crisis will be over as I'm interested in moving bacl to you as you're R250

Drop me a PM if you'd like to move your line back to us, I'll check out your account.

wingnut771 · Mar 28, 2014

AfriGuy said:
Drop me a PM if you'd like to move your line back to us, I'll check out your account.

The WA process is already pending. Once it's back with telkom I'll do that.

Hunted · Mar 28, 2014

Heya all

Just another random speed test result.

Speed looks much better

The last test that was better than the above was on 01-03-2014. I did 17 test in between then and now.

Hoping the additional capacity "arrived" to give me this result.

Zertop · Mar 28, 2014

Hunted said:
Heya all

Just another random speed test result.

Speed looks much better

The last test that was better than the above was on 01-03-2014. I did 17 test in between then and now.

Hoping the additional capacity "arrived" to give me this result.

What is your upload sync?? I only get 1Mbps upload on my 10Meg account

(Or are you on a 20Mbps line?)

Z

i.got~issues · Mar 28, 2014

Here are a couple of random tests:

1st Afrihost Business;

2nd Obviously not an Afrihost Business account;

Zertop's Line test tool results;

Code:

Your average ping was 13ms!

Your line seems to be running perfectly! If there are any issues, they most prob
ably lie with your ISP :-(


------------------------------------
A text file will now open with the complete results from the test. Please attach
 this to a forum post for advice if needed!
 ______         _
|___  /        | |
   / / ___ _ __| |_ ___  _ __
  / / / _ \ '__| __/ _ \| '_ \
 / /_|  __/ |  | || (_) | |_) |
/_____\___|_|   \__\___/| .__/
                        | |
                        |_|
Press any key to continue . . .

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

Pinging 196.38.72.125 with 32 bytes of data:
Reply from 196.38.72.125: bytes=32 time=10ms TTL=250
Reply from 196.38.72.125: bytes=32 time=11ms TTL=250
Reply from 196.38.72.125: bytes=32 time=12ms TTL=250
Reply from 196.38.72.125: bytes=32 time=15ms TTL=250
Reply from 196.38.72.125: bytes=32 time=14ms TTL=250
Reply from 196.38.72.125: bytes=32 time=13ms TTL=250
Reply from 196.38.72.125: bytes=32 time=15ms TTL=250
Reply from 196.38.72.125: bytes=32 time=20ms TTL=250
Reply from 196.38.72.125: bytes=32 time=10ms TTL=250
Reply from 196.38.72.125: bytes=32 time=21ms TTL=250
Reply from 196.38.72.125: bytes=32 time=11ms TTL=250
Reply from 196.38.72.125: bytes=32 time=11ms TTL=250
Reply from 196.38.72.125: bytes=32 time=18ms TTL=250
Reply from 196.38.72.125: bytes=32 time=11ms TTL=250
Reply from 196.38.72.125: bytes=32 time=11ms TTL=250
Reply from 196.38.72.125: bytes=32 time=11ms TTL=250
Reply from 196.38.72.125: bytes=32 time=10ms TTL=250
Reply from 196.38.72.125: bytes=32 time=12ms TTL=250
Reply from 196.38.72.125: bytes=32 time=12ms TTL=250
Reply from 196.38.72.125: bytes=32 time=22ms TTL=250
Reply from 196.38.72.125: bytes=32 time=18ms TTL=250
Reply from 196.38.72.125: bytes=32 time=12ms TTL=250
Reply from 196.38.72.125: bytes=32 time=12ms TTL=250
Reply from 196.38.72.125: bytes=32 time=13ms TTL=250
Reply from 196.38.72.125: bytes=32 time=13ms TTL=250
Reply from 196.38.72.125: bytes=32 time=13ms TTL=250
Reply from 196.38.72.125: bytes=32 time=13ms TTL=250
Reply from 196.38.72.125: bytes=32 time=13ms TTL=250
Reply from 196.38.72.125: bytes=32 time=13ms TTL=250
Reply from 196.38.72.125: bytes=32 time=14ms TTL=250

Ping statistics for 196.38.72.125:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 10ms, Maximum = 22ms, Average = 13ms
 
2014/03/28 19:55:27.82

Oh well, I am out of here until the ordered capacity comes back online.
Flogging a dead horse here.

cortexenslaver · Mar 28, 2014

Zertop said:
What is your upload sync?? I only get 1Mbps upload on my 10Meg account (Or are you on a 20Mbps line?)

Z

Here are some results for this evening so far using Zertop's tools:

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

Pinging 105.236.13.129 with 32 bytes of data:
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=10ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=7ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=12ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=18ms TTL=254
Reply from 105.236.13.129: bytes=32 time=15ms TTL=254
Reply from 105.236.13.129: bytes=32 time=13ms TTL=254
Reply from 105.236.13.129: bytes=32 time=15ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=9ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=9ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=7ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=9ms TTL=254
Reply from 105.236.13.129: bytes=32 time=7ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=7ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=9ms TTL=254
Reply from 105.236.13.129: bytes=32 time=9ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254

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

2014/03/28 19:32:10.89

Local Tracert

Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway.pace.net [192.168.1.254]
2 7 ms 7 ms 7 ms 105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129]
3 9 ms 8 ms 8 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 8 ms 7 ms 8 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 8 ms 9 ms 8 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 9 ms 8 ms 8 ms 196.44.31.106
7 9 ms 9 ms 8 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 10 ms 11 ms 11 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 13 ms 10 ms 11 ms 197-84-7-1.cpt.mweb.co.za [197.84.7.1]
10 9 ms 9 ms 9 ms 197-84-5-254.cpt.mweb.co.za [197.84.5.254]
11 10 ms 11 ms 10 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
12 10 ms 9 ms 10 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]
13 10 ms 10 ms 9 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
14 11 ms 10 ms 10 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
15 10 ms 11 ms 11 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.

International Tracert

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway.pace.net [192.168.1.254]
2 7 ms 7 ms 7 ms 105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129]
3 8 ms 8 ms 7 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 12 ms 10 ms 12 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 8 ms 9 ms 8 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 9 ms 9 ms 10 ms 196.44.31.106
7 152 ms 158 ms 153 ms am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.221]
8 152 ms 152 ms 152 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
9 152 ms 152 ms 152 ms linx-gw1.thn.ncuk.net [195.66.224.240]
10 163 ms 152 ms 153 ms gi1-24-10-star1.core-rs2.thdo.ncuk.net [80.249.97.9]
11 152 ms 152 ms 151 ms www.thinkbroadband.com [80.249.99.130]

Trace complete.

International Speedtest
Downloaded 20.0 megabytes in 36 seconds. (558.97 KB/s)

Local Speedtest
Downloaded 15.6 megabytes in 18 seconds. (847.73 KB/s)

So far so good.... this morning, and most of the day the line was quite fast.
.... will wait till 22:00 to post again

Zertop · Mar 28, 2014

Results looking solid

cortexenslaver · Mar 28, 2014

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

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

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

2014/03/28 20:54:08.14

Local Tracert

Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway.pace.net [192.168.1.254]
2 7 ms 7 ms 6 ms 105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129]
3 8 ms 9 ms 9 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 8 ms 8 ms 9 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 8 ms 8 ms 9 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 9 ms 8 ms 9 ms 196.44.31.106
7 8 ms 8 ms 9 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 11 ms 11 ms 9 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 12 ms 10 ms 12 ms 197-84-7-1.cpt.mweb.co.za [197.84.7.1]
10 10 ms 10 ms 9 ms 197-84-5-254.cpt.mweb.co.za [197.84.5.254]
11 10 ms 10 ms 9 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
12 10 ms 10 ms 9 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]
13 10 ms 10 ms 10 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
14 10 ms 10 ms 10 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
15 10 ms 10 ms 10 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.

International Tracert

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway.pace.net [192.168.1.254]
2 7 ms 7 ms 6 ms 105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129]
3 10 ms 8 ms 8 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 8 ms 43 ms 8 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 9 ms 9 ms 9 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 10 ms 9 ms 8 ms 196.44.31.106
7 152 ms 152 ms 152 ms am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.221]
8 152 ms 205 ms 180 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
9 309 ms 153 ms 152 ms linx-gw1.thn.ncuk.net [195.66.224.240]
10 154 ms 159 ms 161 ms gi1-24-10-star1.core-rs2.thdo.ncuk.net [80.249.97.9]
11 152 ms 152 ms 152 ms www.thinkbroadband.com [80.249.99.130]

Trace complete.

International Speedtest
Downloaded 20.0 megabytes in 34 seconds. (588.30 KB/s)

Local Speedtest
Downloaded 15.6 megabytes in 17 seconds. (890.42 KB/s)

Hunted · Mar 28, 2014

Zertop said:
What is your upload sync?? I only get 1Mbps upload on my 10Meg account (Or are you on a 20Mbps line?)

Z

My line is sync at 20Mbps, but I'm only on a 10Mbps Uncapped package..

A strategy I followed which cost me about R100 more, but gets me better download and upload speeds.

Zertop · Mar 28, 2014

Hunted said:
My line is sync at 20Mbps, but I'm only on a 10Mbps Uncapped package..

A strategy I followed which cost me about R100 more, but gets me better download and upload speeds.

Okay cool

I was about to say

Quite a good plan

cortexenslaver · Mar 29, 2014

Speeds a bit choppy this morning... things seem to be slipping

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

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

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

2014/03/29 10:11:36.68

Local Tracert

Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway.pace.net [192.168.1.254]
2 7 ms 6 ms 7 ms 105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129]
3 8 ms 8 ms 7 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 9 ms 12 ms 8 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 10 ms 9 ms 9 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 43 ms 8 ms 9 ms 196.44.31.106
7 9 ms 8 ms 8 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 10 ms 9 ms 9 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 10 ms 10 ms 12 ms 197-84-7-1.cpt.mweb.co.za [197.84.7.1]
10 9 ms 9 ms 9 ms 197-84-5-254.cpt.mweb.co.za [197.84.5.254]
11 10 ms 10 ms 9 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
12 10 ms 10 ms 9 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]
13 10 ms 9 ms 10 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
14 10 ms 10 ms 10 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
15 10 ms 10 ms 10 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.

International Tracert

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway.pace.net [192.168.1.254]
2 7 ms 7 ms 7 ms 105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129]
3 8 ms 7 ms 8 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 8 ms * 8 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 8 ms 8 ms 9 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 8 ms 8 ms 9 ms 196.44.31.106
7 152 ms 152 ms 151 ms am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.221]
8 152 ms 179 ms 151 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
9 152 ms 152 ms 152 ms linx-gw1.thn.ncuk.net [195.66.224.240]
10 153 ms 170 ms 153 ms gi1-24-10-star1.core-rs2.thdo.ncuk.net [80.249.97.9]
11 152 ms 151 ms 151 ms www.thinkbroadband.com [80.249.99.130]

Trace complete.

International Speedtest
Downloaded 20.0 megabytes in 34 seconds. (589.08 KB/s)

Local Speedtest
Downloaded 15.6 megabytes in 17 seconds. (901.71 KB/s)

Test End Timestamp
2014/03/29 10:14:57.79

Zertop · Mar 29, 2014

cortexenslaver said:
Speeds a bit choppy this morning... things seem to be slipping

Pings look fine. Local download looks perfect - International is a bit slow :/

isabelladol · Mar 29, 2014

Please help AfriMan

Issues started appearing around May last year, slow download speeds, high latency, major packetloss, all of those wonderful things.
I opened up a ticket with Afrihost, after 2 months nothing had been resolved and Telkom closed the ticket after not doing a thing for me.

Now I've been having the exact same issues again and they are just worsening. My 4mb uncapped ADSL is in terrible terrible shape and I'm just not getting anything remotely close to what I am paying for. I enjoy online gaming, but with the state of the internet lately it's just not possible to enjoy it without raging at the lag anymore.

I sent this ticket earlier this week.

-----------------------------------------------------

I am really concerned about the quality of ADSL I am receiving.
For the past year we have received very poor/slow internet access on our 4MB uncapped line. Last year in June I filed a support ticked with Afrihost due to extremely slow and intermittent line speed. It took 2 months of Telkom coming to the house and testing and nothing was done to resolve the issue. The last thing I was told was that the problem was due to my ADSL exchange being contested, and that there was not much that could be done until Telkom upgrades the exchange. This was back in August and after 7 or so months nothing has been done and I am still struggling with extremely slow line speed. ADSL isn’t cheap and I’d appreciate it if something could be done, I do not feel as if I am getting what I am paying for.

I attached the results from the Afrihost Network Tester below.

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=57 time=474 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=57 time=716 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=57 time=116 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=57 time=57 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=57 time=44 ms

ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=41 time=243 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=41 time=877 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=41 time=1055 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=41 time=1305 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=41 time=269 ms

Trace Test:

traceroute -n 197.242.144.102

1 192.168.0.1 16.588 ms * *
2 105.236.0.129 417.89 ms 62.759 ms 16.524 ms
3 41.181.222.42 345.495 ms 122.536 ms 19.533 ms
4 196.44.27.68 677.137 ms 54.346 ms 20.072 ms
5 196.44.31.176 310.196 ms 61.53 ms 19.954 ms
6 196.44.0.43 112.657 ms 20.317 ms
Request timed out *
7 41.181.165.119 70.427 ms 765.568 ms 115.569 ms
8 196.30.1.53 42.113 ms
196.30.1.39 995.626 ms
196.31.220.10 55.004 ms
9 196.31.220.21 53.891 ms 538.154 ms 136.284 ms
10 196.31.63.206 100.478 ms 20.018 ms
Request timed out *
11 196.30.42.133 74.366 ms 20.607 ms
Request timed out *
12 197.242.144.102 57.624 ms 24.656 ms 41.378 ms

traceroute -n 8.8.8.8

1 192.168.0.1 1.324 ms 1.1 ms 1.107 ms
2 105.236.0.129 9.616 ms 481.261 ms 9.567 ms
3 undefined NaN ms
41.181.201.14 476.641 ms 19.314 ms
4 41.181.201.14 35.651 ms
196.44.27.68 649.988 ms 23.108 ms
5 196.44.27.68 41.428 ms
196.44.31.176 511.278 ms 19.505 ms
6 196.44.31.176 25.255 ms
Request timed out * *
7 Request timed out *
41.181.165.119 842.62 ms 210.261 ms
8 41.181.165.119 148.324 ms
72.14.194.74 765.96 ms 307.161 ms
9 72.14.194.74 149.614 ms
66.249.95.8 667.592 ms 288.578 ms
10 66.249.95.8 240.6 ms
209.85.253.196 409.607 ms
209.85.244.240 738.657 ms
11 209.85.253.196 402.986 ms
72.14.242.220 307.087 ms 733.572 ms
12 66.249.95.173 283.816 ms
72.14.238.217 268.137 ms
209.85.252.83 594.946 ms
13 209.85.252.83 415.681 ms
Request timed out * *
14 Request timed out *
8.8.8.8 206.787 ms 240.3 ms
15 8.8.8.8 781.508 ms

DNS Test:

nslookup http://www.afrihost.com

Name: http://www.afrihost.com
Address: 197.242.144.102

nslookup http://www.google.com

Name: http://www.google.com
Address: 74.125.233.83
Name: http://www.google.com
Address: 74.125.233.80
Name: http://www.google.com
Address: 74.125.233.81
Name: http://www.google.com
Address: 74.125.233.84
Name: http://www.google.com
Address: 74.125.233.82

nslookup thishouldfail.afrihost.com

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

--------------------------------------------------------------

Also these are the kinds of results I'm getting

appalling.

Rickster · Mar 29, 2014

Wow, today my line is perfect, pings are low and stable.

What has been done?

1Meg

Zertop · Mar 29, 2014

isabelladol said:
Please help AfriMan

Issues started appearing around May last year, slow download speeds, high latency, major packetloss, all of those wonderful things.
I opened up a ticket with Afrihost, after 2 months nothing had been resolved and Telkom closed the ticket after not doing a thing for me.

Now I've been having the exact same issues again and they are just worsening. My 4mb uncapped ADSL is in terrible terrible shape and I'm just not getting anything remotely close to what I am paying for. I enjoy online gaming, but with the state of the internet lately it's just not possible to enjoy it without raging at the lag anymore.

I sent this ticket earlier this week.

-----------------------------------------------------

I am really concerned about the quality of ADSL I am receiving.
For the past year we have received very poor/slow internet access on our 4MB uncapped line. Last year in June I filed a support ticked with Afrihost due to extremely slow and intermittent line speed. It took 2 months of Telkom coming to the house and testing and nothing was done to resolve the issue. The last thing I was told was that the problem was due to my ADSL exchange being contested, and that there was not much that could be done until Telkom upgrades the exchange. This was back in August and after 7 or so months nothing has been done and I am still struggling with extremely slow line speed. ADSL isn’t cheap and I’d appreciate it if something could be done, I do not feel as if I am getting what I am paying for.

I attached the results from the Afrihost Network Tester below.

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=57 time=474 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=57 time=716 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=57 time=116 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=57 time=57 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=57 time=44 ms

ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=41 time=243 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=41 time=877 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=41 time=1055 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=41 time=1305 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=41 time=269 ms

Trace Test:

traceroute -n 197.242.144.102

1 192.168.0.1 16.588 ms * *
2 105.236.0.129 417.89 ms 62.759 ms 16.524 ms
3 41.181.222.42 345.495 ms 122.536 ms 19.533 ms
4 196.44.27.68 677.137 ms 54.346 ms 20.072 ms
5 196.44.31.176 310.196 ms 61.53 ms 19.954 ms
6 196.44.0.43 112.657 ms 20.317 ms
Request timed out *
7 41.181.165.119 70.427 ms 765.568 ms 115.569 ms
8 196.30.1.53 42.113 ms
196.30.1.39 995.626 ms
196.31.220.10 55.004 ms
9 196.31.220.21 53.891 ms 538.154 ms 136.284 ms
10 196.31.63.206 100.478 ms 20.018 ms
Request timed out *
11 196.30.42.133 74.366 ms 20.607 ms
Request timed out *
12 197.242.144.102 57.624 ms 24.656 ms 41.378 ms

traceroute -n 8.8.8.8

1 192.168.0.1 1.324 ms 1.1 ms 1.107 ms
2 105.236.0.129 9.616 ms 481.261 ms 9.567 ms
3 undefined NaN ms
41.181.201.14 476.641 ms 19.314 ms
4 41.181.201.14 35.651 ms
196.44.27.68 649.988 ms 23.108 ms
5 196.44.27.68 41.428 ms
196.44.31.176 511.278 ms 19.505 ms
6 196.44.31.176 25.255 ms
Request timed out * *
7 Request timed out *
41.181.165.119 842.62 ms 210.261 ms
8 41.181.165.119 148.324 ms
72.14.194.74 765.96 ms 307.161 ms
9 72.14.194.74 149.614 ms
66.249.95.8 667.592 ms 288.578 ms
10 66.249.95.8 240.6 ms
209.85.253.196 409.607 ms
209.85.244.240 738.657 ms
11 209.85.253.196 402.986 ms
72.14.242.220 307.087 ms 733.572 ms
12 66.249.95.173 283.816 ms
72.14.238.217 268.137 ms
209.85.252.83 594.946 ms
13 209.85.252.83 415.681 ms
Request timed out * *
14 Request timed out *
8.8.8.8 206.787 ms 240.3 ms
15 8.8.8.8 781.508 ms

DNS Test:

nslookup http://www.afrihost.com

Name: http://www.afrihost.com
Address: 197.242.144.102

nslookup http://www.google.com

Name: http://www.google.com
Address: 74.125.233.83
Name: http://www.google.com
Address: 74.125.233.80
Name: http://www.google.com
Address: 74.125.233.81
Name: http://www.google.com
Address: 74.125.233.84
Name: http://www.google.com
Address: 74.125.233.82

nslookup thishouldfail.afrihost.com

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

--------------------------------------------------------------

Also these are the kinds of results I'm getting appalling.

Sorry - on mobile, didn't read the entire post :-( I will when I get home

Looks like a line issue :-( please would you run the second tool in my sig

Z

isabelladol · Mar 29, 2014

Here are the results.

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

Pinging 105.236.0.129 with 32 bytes of data:
Reply from 105.236.0.129: bytes=32 time=207ms TTL=254
Reply from 105.236.0.129: bytes=32 time=55ms TTL=254
Reply from 105.236.0.129: bytes=32 time=146ms TTL=254
Reply from 105.236.0.129: bytes=32 time=113ms TTL=254
Reply from 105.236.0.129: bytes=32 time=80ms TTL=254
Reply from 105.236.0.129: bytes=32 time=59ms TTL=254
Reply from 105.236.0.129: bytes=32 time=291ms TTL=254
Reply from 105.236.0.129: bytes=32 time=98ms TTL=254
Reply from 105.236.0.129: bytes=32 time=54ms TTL=254
Reply from 105.236.0.129: bytes=32 time=130ms TTL=254
Reply from 105.236.0.129: bytes=32 time=119ms TTL=254
Reply from 105.236.0.129: bytes=32 time=120ms TTL=254
Reply from 105.236.0.129: bytes=32 time=116ms TTL=254
Reply from 105.236.0.129: bytes=32 time=61ms TTL=254
Reply from 105.236.0.129: bytes=32 time=72ms TTL=254
Reply from 105.236.0.129: bytes=32 time=221ms TTL=254
Reply from 105.236.0.129: bytes=32 time=163ms TTL=254
Reply from 105.236.0.129: bytes=32 time=89ms TTL=254
Reply from 105.236.0.129: bytes=32 time=117ms TTL=254
Reply from 105.236.0.129: bytes=32 time=19ms TTL=254
Reply from 105.236.0.129: bytes=32 time=88ms TTL=254
Reply from 105.236.0.129: bytes=32 time=107ms TTL=254
Reply from 105.236.0.129: bytes=32 time=25ms TTL=254
Reply from 105.236.0.129: bytes=32 time=297ms TTL=254
Reply from 105.236.0.129: bytes=32 time=265ms TTL=254
Reply from 105.236.0.129: bytes=32 time=92ms TTL=254
Reply from 105.236.0.129: bytes=32 time=56ms TTL=254
Reply from 105.236.0.129: bytes=32 time=137ms TTL=254
Reply from 105.236.0.129: bytes=32 time=85ms TTL=254
Reply from 105.236.0.129: bytes=32 time=212ms TTL=254

Ping statistics for 105.236.0.129:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 297ms, Average = 123ms

Sat 03/29/2014 17:19:50.88

Zertop · Mar 29, 2014

isabelladol said:
Here are the results.

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

Pinging 105.236.0.129 with 32 bytes of data:
Reply from 105.236.0.129: bytes=32 time=207ms TTL=254
Reply from 105.236.0.129: bytes=32 time=55ms TTL=254
Reply from 105.236.0.129: bytes=32 time=146ms TTL=254
Reply from 105.236.0.129: bytes=32 time=113ms TTL=254
Reply from 105.236.0.129: bytes=32 time=80ms TTL=254
Reply from 105.236.0.129: bytes=32 time=59ms TTL=254
Reply from 105.236.0.129: bytes=32 time=291ms TTL=254
Reply from 105.236.0.129: bytes=32 time=98ms TTL=254
Reply from 105.236.0.129: bytes=32 time=54ms TTL=254
Reply from 105.236.0.129: bytes=32 time=130ms TTL=254
Reply from 105.236.0.129: bytes=32 time=119ms TTL=254
Reply from 105.236.0.129: bytes=32 time=120ms TTL=254
Reply from 105.236.0.129: bytes=32 time=116ms TTL=254
Reply from 105.236.0.129: bytes=32 time=61ms TTL=254
Reply from 105.236.0.129: bytes=32 time=72ms TTL=254
Reply from 105.236.0.129: bytes=32 time=221ms TTL=254
Reply from 105.236.0.129: bytes=32 time=163ms TTL=254
Reply from 105.236.0.129: bytes=32 time=89ms TTL=254
Reply from 105.236.0.129: bytes=32 time=117ms TTL=254
Reply from 105.236.0.129: bytes=32 time=19ms TTL=254
Reply from 105.236.0.129: bytes=32 time=88ms TTL=254
Reply from 105.236.0.129: bytes=32 time=107ms TTL=254
Reply from 105.236.0.129: bytes=32 time=25ms TTL=254
Reply from 105.236.0.129: bytes=32 time=297ms TTL=254
Reply from 105.236.0.129: bytes=32 time=265ms TTL=254
Reply from 105.236.0.129: bytes=32 time=92ms TTL=254
Reply from 105.236.0.129: bytes=32 time=56ms TTL=254
Reply from 105.236.0.129: bytes=32 time=137ms TTL=254
Reply from 105.236.0.129: bytes=32 time=85ms TTL=254
Reply from 105.236.0.129: bytes=32 time=212ms TTL=254

Ping statistics for 105.236.0.129:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 297ms, Average = 123ms

Sat 03/29/2014 17:19:50.88

Definitely appears like a line issue :-(

Have you reported a fault directly to telkom, or only Afrihost?

cortexenslaver · Mar 29, 2014

http://speedtest.ookla.com/result/2553893785.png

http://speedtest.ookla.com/result/2553896245.png

http://speedtest.ookla.com/result/2553897034.png

cortexenslaver · Mar 29, 2014

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

Pinging 105.236.13.129 with 32 bytes of data:
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=7ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=10ms TTL=254
Reply from 105.236.13.129: bytes=32 time=11ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=7ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=7ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=7ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=7ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=10ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=8ms TTL=254
Reply from 105.236.13.129: bytes=32 time=7ms TTL=254

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

2014/03/29 18:45:47.23

Local Tracert

Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway.pace.net [192.168.1.254]
2 7 ms 7 ms 7 ms 105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129]
3 8 ms 25 ms 8 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 8 ms 8 ms 8 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 9 ms 8 ms 9 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 8 ms 9 ms 9 ms 196.44.31.106
7 8 ms 8 ms 8 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 10 ms 14 ms 10 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 10 ms 11 ms 11 ms 197-84-7-1.cpt.mweb.co.za [197.84.7.1]
10 10 ms 9 ms 9 ms 197-84-5-254.cpt.mweb.co.za [197.84.5.254]
11 10 ms 9 ms 10 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
12 10 ms 9 ms 10 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]
13 10 ms 9 ms 10 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
14 10 ms 10 ms 10 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
15 10 ms 10 ms 10 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.

International Tracert

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway.pace.net [192.168.1.254]
2 6 ms 7 ms 7 ms 105-236-13-129-esr-lo.mtnbusiness.co.za [105.236.13.129]
3 8 ms 8 ms 8 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 8 ms 8 ms 8 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 9 ms 9 ms 8 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 8 ms 8 ms 8 ms 196.44.31.106
7 152 ms 151 ms 151 ms am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.221]
8 152 ms 152 ms 152 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
9 152 ms 152 ms 151 ms linx-gw1.thn.ncuk.net [195.66.224.240]
10 173 ms 152 ms 152 ms gi1-24-10-star1.core-rs2.thdo.ncuk.net [80.249.97.9]
11 152 ms 152 ms 152 ms www.thinkbroadband.com [80.249.99.130]

Trace complete.

International Speedtest
Downloaded 20.0 megabytes in 34 seconds. (589.25 KB/s)

Local Speedtest
Downloaded 15.6 megabytes in 16 seconds. (969.64 KB/s)

Join the MyBroadband community

Get started

Afrihost Business Uncapped Feedback

Honorary Master

Afrihost

Honorary Master

Expert Member

Expert Member

Expert Member

Senior Member

Expert Member

Senior Member

Expert Member

Expert Member

Senior Member

Expert Member

Active Member

EVGA Fanatic

Expert Member

Active Member

Expert Member

Senior Member

Senior Member