Afrihost Business Uncapped Feedback - 2

Status
Not open for further replies.
And so it unfolds that Business Uncapped (Unshaped) accounts / users across the country are experiencing erratic performance.

I have cancelled my account and at the end of this month I am with an ISP who doesn't use Telkom. I am experiencing the same issues mentioned by countless people in the post before mine. I cannot watch YouTube, Hulu or Netflix. I can barely browse...

I am on a 2Mbps Business Uncapped account. I gave up calling in and logging a ticket. I just increase my stress levels when I have to do a million tests repeatedly as requested by different support agents...having to repeat myself a million times...

NO AFRIHOST! YOUR INFRASTRUCTURE IS F**KED UP. SORT THIS ***** OUT!


The evidence is in these posts by so many people that your network infrastructure is gone for a ball of *****e! Stop blaming people's hardware, Telkom and other parties.
Its like saying: "Oh look your area is experiencing load shedding according to our schedule, when I clearly have power to make this post"

Get proper engineers who can fix the problem even if you have to fly them in from Cisco.

Sorry to hear you're leaving us, if there is something I can look into for you or any tickets I can have escalated I'll gladly do so.
 
Cancelling end of this month. Speeds remind me of 1mbps where I used to have to sit and wait for a 480p Youtube video to buffer (which was expected of 1mbps). I can't remember when I was last able to stream a Youtube video at 480p on my 10mbps Business. Its infuriating. And no its not Telkom, no its not my line, its not some "infastructure" problem either, its purely my ISP (so Afrihost) who are over capacity and shaping.

International routing to Google cache servers and the such make Youtube make streaming even more atrocious. Wife isn't very happy either. And you know what they say. Happy wife = Happy life. Well leaves me no choice but to move.

C:\Users\4saken>tracert youtube.com

Tracing route to youtube.com [74.125.233.96]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 192.168.1.1
2 8 ms 7 ms 7 ms 105-236-11-193-esr-lo.mtnbusiness.co.za [105.236
.11.193]
3 13 ms 13 ms 11 ms ipc-recieve-rb-1a.za.mtnbusiness.net [41.181.178
.53]
4 14 ms 18 ms 13 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
5 164 ms 31 ms 147 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95
]
6 109 ms 62 ms 13 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 200 ms 191 ms 193 ms google-peering-ls-pr-2.uk.mtnns.net [209.212.99. (INTERNATIONAL PEERING!!!)
13]
8 218 ms 541 ms 496 ms 209.85.255.76
9 392 ms 193 ms 197 ms 66.249.95.9
10 192 ms 191 ms 263 ms 72.14.239.129
11 196 ms 295 ms 247 ms jnb01s08-in-f0.1e100.net [74.125.233.96]

Trace complete.

Sorry to hear you're having issues streaming content :(
Upgrades have already been implemented so there shouldn't be any issues there. Do you have any ref#'s that I can look into for you?
 
Oscar .... Dont know who this guy is at AH, but he seems to be the guy who gets things done .... give credit where its due.
Impressed with Oscar

Lets hope he sorts my issue out.

He's a champ, I'm sure he'll have things sorted out for you!
 
Thank you.
As you can see from the speedtests i posted this morning, nothing has changed as of yet.
So i hope they come back with a solution yet to be implemented...
 
Thank you.
As you can see from the speedtests i posted this morning, nothing has changed as of yet.
So i hope they come back with a solution yet to be implemented...

I'm confident our guys will get to the bottom of this. As soon as there's feedback the ticket will be updated.
 
This is very odd, do you have comparison traceroutes that I can look at?
The 105 IP is definitely ours, if I run a reverse dig on the 196 IP it doesn't resolve to us - are you using our DNS servers?
Here is the full tracert from my business account:

Tracing route to afrihost.co.za [197.242.144.102]
over a maximum of 30 hops:

1 <1 ms * <1 ms fluxtmg.fluxonline.net [192.168.10.1]
2 1 ms <1 ms <1 ms 0129976483.fluxonline.net [10.0.0.1]
3 11 ms 11 ms 10 ms 196.7.106.11
4 * * * Request timed out.
5 12 ms 11 ms 11 ms 196.30.1.39
6 10 ms 11 ms 10 ms 196.31.220.23
7 10 ms 10 ms 10 ms 196.31.63.206
8 36 ms 19 ms 11 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
9 10 ms 10 ms 10 ms cms-gm.afrihost.com [197.242.144.102]

Please make sure the routes are correct and its using the correct gateways etc.

Yes the router obtains automatic DNS 196.7.7.7
 
This is very odd, do you have comparison traceroutes that I can look at?
The 105 IP is definitely ours, if I run a reverse dig on the 196 IP it doesn't resolve to us - are you using our DNS servers?
Here is the full tracert from my business account:

Tracing route to afrihost.co.za [197.242.144.102]
over a maximum of 30 hops:

1 <1 ms * <1 ms fluxtmg.fluxonline.net [192.168.10.1]
2 1 ms <1 ms <1 ms 0129976483.fluxonline.net [10.0.0.1]
3 11 ms 11 ms 10 ms 196.7.106.11
4 * * * Request timed out.
5 12 ms 11 ms 11 ms 196.30.1.39
6 10 ms 11 ms 10 ms 196.31.220.23
7 10 ms 10 ms 10 ms 196.31.63.206
8 36 ms 19 ms 11 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
9 10 ms 10 ms 10 ms cms-gm.afrihost.com [197.242.144.102]

Please make sure the routes are correct and its using the correct gateways etc.

Yes the router obtains automatic DNS 196.7.7.7

Are you 100% sure you're using our DSL details here? All of these IPs link to servers I pasted earlier in my dig.
 
My Speed is very slow
Afrihost test Account

Ping Test:

ping 197.242.144.102

Request timeout for icmp_seq 1
64 bytes from 197.242.144.102: icmp_req=2 ttl=58 time=50 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=58 time=49 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=58 time=49 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=58 time=49 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=45 time=170 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=45 time=176 ms
Request timeout for icmp_seq 3
64 bytes from 8.8.8.8: icmp_req=4 ttl=45 time=170 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=45 time=171 ms


Trace Test:

traceroute -n 197.242.144.102

1192.168.178.1 * * *
2105.236.10.65 7.963 ms 7.78 ms 8.85 ms
341.181.54.86 33.001 ms 32.707 ms 32.587 ms
441.181.198.188 52.677 ms 26.408 ms 26.162 ms
5196.44.18.2 34.232 ms 34.489 ms 34.141 ms
6196.44.31.134 34.817 ms 34.702 ms 34.832 ms
7196.44.31.69 48.921 ms 49.26 ms 49.909 ms
8196.44.0.221 56.146 ms
196.44.31.97 48.522 ms 48.548 ms
9196.31.220.10 48.584 ms
196.31.220.12 55.61 ms 85.903 ms
10196.31.220.25 55.676 ms
196.31.220.21 49.334 ms 48.71 ms
11196.31.63.206 48.745 ms 49.102 ms
196.31.63.202 56.703 ms
12196.30.42.133 48.683 ms 47.492 ms 47.957 ms
13197.242.144.102 49.917 ms 49.416 ms 49.769 ms


traceroute -n 8.8.8.8

1192.168.178.1 * * *
2105.236.10.65 8.076 ms 7.752 ms 8.291 ms
341.181.53.214 18.65 ms 18.584 ms 19.626 ms
441.181.184.28 18.446 ms 18.706 ms 18.709 ms
5196.44.18.2 26.426 ms 55.336 ms 26.189 ms
6196.44.31.113 171.041 ms177.352 ms173.195 ms
7209.212.111.187 169.35 ms 170.048 ms169.173 ms
8209.212.99.13 170.07 ms
Request timed out * *
9209.85.255.76 182.274 ms178.374 ms180.966 ms
10209.85.244.240 163.769 ms
216.239.51.5 172.567 ms
209.85.245.2 163.763 ms
1164.233.174.82 176.723 ms
209.85.249.211 180.657 ms
72.14.242.220 183.109 ms
12216.239.47.87 183.926 ms185.078 ms186.756 ms
13Request timed out * * *
148.8.8.8 170.14 ms 171.053 ms180.094 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: 74.125.233.100


nslookup thishouldfail.afrihost.com

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

View attachment 164177



Afrihost Buisines account


Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=58 time=49 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=58 time=48 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=58 time=49 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=58 time=49 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=58 time=48 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=45 time=178 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=45 time=195 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=45 time=188 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=45 time=178 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=45 time=188 ms


Trace Test:

traceroute -n 197.242.144.102

1192.168.178.1 * * *
2105.236.10.65 8.537 ms 8.279 ms 8.306 ms
341.181.54.86 26.944 ms 25.143 ms 25.585 ms
441.181.198.188 32.905 ms 32.255 ms 32.449 ms
5196.44.18.2 26.407 ms 26.305 ms 26.412 ms
6196.44.31.134 27.33 ms 26.866 ms 27.385 ms
7196.44.31.69 55.975 ms 56.867 ms 56.997 ms
8196.44.0.221 55.031 ms
196.44.31.97 55.933 ms 56.082 ms
9196.31.220.10 56.351 ms 54.858 ms
196.30.1.53 49.225 ms
10196.31.220.25 55.461 ms 55.778 ms
196.31.220.21 55.685 ms
11196.31.63.206 56.358 ms
196.31.63.202 49.525 ms 48.662 ms
12196.30.42.133 56.432 ms 75.647 ms 59.868 ms
13197.242.144.102 49.378 ms 48.899 ms 48.936 ms


traceroute -n 8.8.8.8

1192.168.178.1 * * *
2105.236.10.65 7.609 ms 8.423 ms 7.891 ms
341.181.51.182 18.716 ms 18.074 ms 17.85 ms
4Request timed out * *
41.181.184.28 25.778 ms
5196.44.18.2 19.034 ms 18.964 ms 18.469 ms
6196.44.31.113 183.934 ms169.538 ms166.54 ms
7209.212.111.187 182.755 ms166.758 ms196.432 ms
8209.212.99.13 174.217 ms167.457 ms164.867 ms
9Request timed out *
209.85.255.76 174.371 ms171.31 ms
10209.85.253.94 176.747 ms163.697 ms
216.239.51.5 162.986 ms
11209.85.249.211 177.387 ms177.448 ms
72.14.236.130 169.215 ms
1272.14.239.248 168.946 ms
216.239.51.155 169.271 ms
209.85.248.101 179.569 ms
13Request timed out * * *
14Request timed out *
8.8.8.8 176.99 ms 176.55 ms
158.8.8.8 175.937 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: 74.125.230.244
Name:www.google.com
Address: 74.125.230.240
Name:www.google.com
Address: 74.125.230.241
Name:www.google.com
Address: 74.125.230.242
Name:www.google.com
Address: 74.125.230.243


nslookup thishouldfail.afrihost.com

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










View attachment 164179





Webafrica


Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=54 time=54 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=54 time=54 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=54 time=53 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=54 time=54 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=54 time=64 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=44 time=185 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=44 time=185 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=44 time=224 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=44 time=185 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=44 time=185 ms


Trace Test:

traceroute -n 197.242.144.102

1192.168.178.1 * * *
2196.215.43.1 8.067 ms 8.045 ms
undefined NaN ms
3196.38.72.193 33.206 ms 33.234 ms
196.215.43.1 8.104 ms
4196.35.115.136 25.913 ms 26.183 ms
196.38.72.193 33.424 ms
5168.209.6.13 34.078 ms 33.589 ms
196.35.115.136 26.195 ms
6168.209.2.131 32.75 ms 35.897 ms
168.209.6.13 35.846 ms
7196.223.22.31 29.483 ms
168.209.6.131 50.906 ms
41.208.29.210 88.614 ms
8196.44.0.75 26.111 ms 26.734 ms
196.223.22.31 26.775 ms
9196.44.31.69 53.617 ms 75.659 ms
196.44.0.75 27.048 ms
10196.44.0.221 46.194 ms
196.44.31.69 53.73 ms
196.44.31.97 85.064 ms
11196.31.220.12 46.342 ms 46.313 ms
196.44.0.221 46.537 ms
12196.31.220.25 46.355 ms 46.16 ms
196.31.220.10 54.891 ms
13196.31.63.202 68.132 ms
196.31.220.21 52.509 ms
196.31.63.206 79.111 ms
14196.30.42.133 46.616 ms 47.194 ms
196.31.63.202 46.337 ms
15197.242.144.102 54.499 ms 68.941 ms
196.30.42.133 46.571 ms
16197.242.144.102 82.043 ms


traceroute -n 8.8.8.8

1192.168.178.1 * * *
2196.215.43.1 15.176 ms 7.612 ms 7.86 ms
3196.38.72.193 40.09 ms 25.472 ms 25.215 ms
4196.35.115.136 37.363 ms 18.754 ms 18.438 ms
5168.209.2.13 19.479 ms 19.578 ms 18.858 ms
6168.209.6.12 20.162 ms 38.834 ms 19.426 ms
7168.209.100.101 42.128 ms 75.923 ms 42.01 ms
8168.209.1.179 41.004 ms 41.4 ms
196.26.0.130 66.45 ms
972.14.205.16 41.896 ms 79.637 ms 42.222 ms
1066.249.95.8 182.392 ms179.541 ms185.6 ms
11216.239.51.5 179.617 ms
209.85.253.196 204.346 ms
209.85.244.240 189.938 ms
1266.249.95.173 192.598 ms193.067 ms
209.85.249.209 185.273 ms
13216.239.47.87 235.504 ms
209.85.250.163 191.092 ms
216.239.51.151 191.871 ms
14Request timed out * * *
158.8.8.8 184.451 ms184.25 ms 187.835 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: 74.125.233.100


nslookup thishouldfail.afrihost.com

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


View attachment 164181

Telkom is the same as webafrica

Please fix your problem
 
This is very odd, do you have comparison traceroutes that I can look at?
The 105 IP is definitely ours, if I run a reverse dig on the 196 IP it doesn't resolve to us - are you using our DNS servers?

Are you 100% sure you're using our DSL details here? All of these IPs link to servers I pasted earlier in my dig.

Yes im 100% positive the the router is set to obtain automatic DNS configuration.

The router is using 196.7.7.7 as its default DNS server.
 
Sorry to hear you're having issues streaming content :(
Upgrades have already been implemented so there shouldn't be any issues there. Do you have any ref#'s that I can look into for you?

This is a ticket from like a month ago. Haven't tried to submit a new ticket because nothing can be fixed it seems. Only time I get a bit of reprieve is when I use another account from another ISP

SUQ-990-11692
 
This is a ticket from like a month ago. Haven't tried to submit a new ticket because nothing can be fixed it seems. Only time I get a bit of reprieve is when I use another account from another ISP

SUQ-990-11692

I see our team are still in touch with you here.
 
I've heard the new exchanges do this and is not a problem but normal for that particular type of exchange.

So pretty much ignore that, and focus on the ISP.

Maybe Afrihost needs to made aware of this. I wasted a lot of my time with Telkom trying to get the exchange tested as Afrihost claimed it was an exchange problem. Telkom also charge if they send out someone and the problem is not on their side. I wonder if I can charge Afrihost my hourly rate for wasting my time? I really don't have time to continually do tests, etc, when the problem is clearly on Afrihosts side, other ISP accounts work 100%
 
I see our team are still in touch with you here.

All they wanted to do was give me a refund (and I know that means being cut me from coming back to Afrihost ever again). But thats not what I wanted and clearly shows me that something is wrong with the network.

I would never offer a refund to someone if I wasn't "guilty" in some sense.

All I want is some transparency. Please can we be told if you are running at full capacity. Its actually better to just tell the truth, then have a bunch of angry customers leave because nothing ever gets communicated to them. There is clearly something wrong with DNS, capacity, etc when there are so many users throughout South Africa complaining. Why cant we just be told the truth? :/
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X