Afrihost Uncapped ADSL Feedback (Pt3)

Status
Not open for further replies.
In the 3 years or so that I was on Afrihost uncapped, the unshaped speed for a few hours every night was more than enough for me to get my anime fix. That doesn't happen anymore, not even a little. I am looking at other packages.

+1

I used to be able to get the stuff I needed in a few hours. Now if I takes 2-3 days to get the same amount downloaded. (Hell I have some torrents that should have finished in about a week that still haven't finished downloading after more than a month)
Previously I was able run my torrents for about 5 hours or so. Now I run them about 18 hours a day and still can't get anything done.

Thats the main reason I cancelled my account. That and the intermittent packet loss on teamspeak, which Afrihost keep saying isn't on their side.
This month is crawling by so slowly. Can't wait to get another ISP.
 
+1

I used to be able[...]

Thats the main reason I cancelled my account. That and the intermittent packet loss on teamspeak, which Afrihost keep saying isn't on their side.
This month is crawling by so slowly. Can't wait to get another ISP.

Yea I'm waiting on feedback from their support. They seem unable to give me answers, ETAs, and solutions. A tracert clearly shows that the problem is on their network and not an exchange. I think I'll be migrating soon as well lest there is a drastic turn around in their services.
 
No service at all for over an hour. I'm missing my live stream that I stayed up for. Somebody please fix this.
 
So wonderful how Afrihost is screwing up one thing after another.
No shaping applied, yet I can't get more than 30kb/s on torrents, and on Direct Dll I can't get past 90kb/s (this is from a site that I can easily get 420kb/s on other ISP's)

Lets try getting Drivers from AMD, o look, maxing out at 26kb/s, why am I not surprised anymore...
 
Yea I'm waiting on feedback from their support. They seem unable to give me answers, ETAs, and solutions. A tracert clearly shows that the problem is on their network and not an exchange. I think I'll be migrating soon as well lest there is a drastic turn around in their services.

So they get back to me and claim its Telekom's fault not their own EVEN THOUGH THE LAG IS ON THE THIRD HOP. my word how incompetent can you get. I'm canceling, its obvious since their mtn marriage they have gone down the drain as a company that can offer meaning full support.
 
So they get back to me and claim its Telekom's fault not their own EVEN THOUGH THE LAG IS ON THE THIRD HOP. my word how incompetent can you get. I'm canceling, its obvious since their mtn marriage they have gone down the drain as a company that can offer meaning full support.

Vote with the $$$
 
So they get back to me and claim its Telekom's fault not their own EVEN THOUGH THE LAG IS ON THE THIRD HOP. my word how incompetent can you get. I'm canceling, its obvious since their mtn marriage they have gone down the drain as a company that can offer meaning full support.

They did the same thing with me. Testing with a Telkom account and a Webafrica account that has no packet loss, and then going back to Afrihost, where my packet loss comes back, and all they can tell me is that its either the TS server or my route, line or exchange.
 
+1

I used to be able to get the stuff I needed in a few hours. Now if I takes 2-3 days to get the same amount downloaded. (Hell I have some torrents that should have finished in about a week that still haven't finished downloading after more than a month)
Previously I was able run my torrents for about 5 hours or so. Now I run them about 18 hours a day and still can't get anything done.

Thats the main reason I cancelled my account. That and the intermittent packet loss on teamspeak, which Afrihost keep saying isn't on their side.
This month is crawling by so slowly. Can't wait to get another ISP.

Torrents are a very problematic yardstick for broadband performance. It depends on the file you are requesting, how well seeded it is and whether the seed has the complete file (or is limiting torrents). I've had a 200MB file download for over a week, while other 1-2GB files download in a matter of hours. I don't think it can really show anything conclusive :(
 
Yea I'm waiting on feedback from their support. They seem unable to give me answers, ETAs, and solutions. A tracert clearly shows that the problem is on their network and not an exchange. I think I'll be migrating soon as well lest there is a drastic turn around in their services.

What are you waiting for feedback on specifically? If you can PM me a ticket reference, I'd be happy to chase that up for you :(
 
No service at all for over an hour. I'm missing my live stream that I stayed up for. Somebody please fix this.

Sorry to hear that. We didn't have any known outages on our network, but could have been an Telkom issue.

If you're still down, please PM me :(
 
They did the same thing with me. Testing with a Telkom account and a Webafrica account that has no packet loss, and then going back to Afrihost, where my packet loss comes back, and all they can tell me is that its either the TS server or my route, line or exchange.

Each network uses their own method for shaping. We shape by DPI, but if a server uses a non-standard port and P2P aspects, we can't whitelist it or something similar to ensure that it is never shaped. When we test TS on port 9987 it works 100% of the time, even on a 2Mbps Uncapped while running CSGO or LoL, etc.
 
GZR-358-71829 / HOA-842-69189
I want the issue resolved. Saying "it's out of our hands" is not an answer. As demonstrated in this thread: http://mybroadband.co.za/vb/showthr...Feedback-2?p=15422904&viewfull=1#post15422904 the issue is specific to Afrihost and its supporting network provider.

I see our team have marked things to be followed up on as soon as there's feedback.
We are making good strides forward, unfortunately a resolution is taking longer than expected though.
 
I am about to toss in the towel with Afrihost.
Trying to download now on uncapped - getting throttled to death. No problem, switch to a capped Afrihost account. Still throttled (not much difference, 15kB/s).

Switch to a CyberSmart account and I am up to 600kB/s. So Afrihost capped and uncapped equally hopeless.
 
Getting almost 320ms to EU servers in War Thunder whereas used to be 220ms.

Managed to catch the game server IP and trace route it. Very bad.

Afrihost:
Code:
Tracing route to 37.48.71.136 over a maximum of 30 hops

  1     1 ms    <1 ms    <1 ms  home.gateway.home.gateway [192.168.1.254]
  2     *        *        *     Request timed out.
  3    87 ms    88 ms   100 ms  41.181.221.217
  4   108 ms   109 ms   116 ms  41.181.221.218
  5   108 ms   108 ms   104 ms  rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.118]
  6   309 ms   302 ms   295 ms  rb-cr-2.za--rb-dca-2.za-b.mtnns.net [196.44.0.155]
  7   321 ms   315 ms   316 ms  jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
  8   309 ms   293 ms   298 ms  ls-cr-2.uk--rb-cr-1.za-g.mtnns.net [196.44.31.114]
  9   299 ms   306 ms   308 ms  ls-pr-1.uk--ls-cr-2.uk-a.mtn.net [209.212.111.201]
 10   313 ms   311 ms   314 ms  peering.thn.lon.leaseweb.net [195.66.225.56]
 11   306 ms   310 ms   313 ms  tengige0-13-0-2.crs-evo.leaseweb.net [31.31.32.73]
 12   303 ms   302 ms   315 ms  85.17.100.241
 13   301 ms   297 ms   296 ms  po1004.ngn-ams1-cs1-new.leaseweb.net [37.48.95.199]
 14   297 ms   301 ms   301 ms  37.48.71.136

Trace complete.

100ms on the 3rd hope. C'mon. This is now the 3rd time in 3 weeks you guys have had this issue. This is starting to become annoying.

WebAfrica:
Code:
Tracing route to 37.48.71.136 over a maximum of 30 hops

  1     1 ms    <1 ms    <1 ms  home.gateway.home.gateway [192.168.1.254]
  2     *        *        *     Request timed out.
  3     9 ms     9 ms    10 ms  196.38.74.246
  4     7 ms     8 ms     7 ms  cdsl1-umh-gi0-0-0-3102.ip.isnet.net [196.38.74.245]
  5     7 ms     9 ms     8 ms  196.26.210.200
  6     9 ms     9 ms     8 ms  mi-za-umh-p8-ten-0-0-0-1.ip.isnet.net [168.209.93.240]
  7   198 ms   199 ms   195 ms  168.209.246.66
  8   195 ms   194 ms   190 ms  168.209.246.65
  9   195 ms   196 ms   195 ms  peering.thn.lon.leaseweb.net [195.66.225.56]
 10   202 ms   203 ms   206 ms  tengige0-9-0-2.crs-evo.leaseweb.net [31.31.32.69]
 11   204 ms   204 ms   204 ms  tengige0-6-0-5.ngn-ams1-cr2-new.leaseweb.net [85.17.100.187]
 12   199 ms   198 ms   204 ms  po1004.ngn-ams1-cs1-new.leaseweb.net [37.48.95.199]
 13   203 ms   202 ms   203 ms  37.48.71.136

Trace complete.
 
Last edited:
I see our team have marked things to be followed up on as soon as there's feedback.
We are making good strides forward, unfortunately a resolution is taking longer than expected though.

HOA-842-69189 / GZR-358-71829
Please liaise with AfriGenie. I want this ticket taken away from whoever the incompetent was that decided that the way to "solve" this was to enable shaping. See last response on HOA-842-69189 ticket for name etc.

I am asked to run tracerts and do debugging on the account all day long and this incompetent responds 2am in the morning to me with and I quote:
Thank you for your mail, I trust you are well.
[...]
I have taken a look into your account and have now activated your Business optimization, this will slow down your downloads but real time protocols should speed up.
[...etc other bull]

No I am not well. Is this the kind of support you offer your clients on business accounts? I had been debugging with one technical person that "appeared" to know whats going on only to out of the blue get some junior grad school techie thumb suck a answer 2am in the morning and decide that I would prefer shaping on my account?

Now, I want you to tell me when you are going to fix this routing/congestion problem in CT, and I want to know by this afternoon (3pm - mail me I will be in meetings most of the day). I will either know the time frame or I will no longer be your client, everyone I know will no longer be your client, and every person I meet or talk to will no longer and never be your client. As you can tell probably this is the end of the road between me and you, either you deliver service, or I will find myself a provider who can actually deliver.

Here are all the stats again.
DATA:
3am
=Afrihost=
Tracing route to www.afrihost.com [41.181.185.18]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 12 ms 11 ms 11 ms 105-236-5-193-esr-lo.mtnbusiness.co.za [105.236.5.193]
3 12 ms 13 ms 13 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]

4 12 ms 12 ms 12 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 13 ms 13 ms 13 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 33 ms 33 ms 33 ms pe-cr-2.za--el-mse-1.za.mtnns.net [196.44.31.66]

7 31 ms 32 ms 33 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
8 34 ms 32 ms 33 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]
good.

11:45am
=Afrihost=
Tracing route to www.afrihost.com [41.181.185.18]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 11 ms 10 ms 10 ms 105-236-5-193-esr-lo.mtnbusiness.co.za [105.236.5.193]
3 115 ms 113 ms 111 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]

4 123 ms 117 ms 115 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 114 ms 115 ms 120 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 118 ms 124 ms 122 ms jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
7 181 ms 176 ms 161 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
8 137 ms 126 ms 123 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.
bad.

=Web Africa=

Tracing route to www.afrihost.com [41.181.185.18]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms 192.168.0.1
2 12 ms 11 ms 11 ms 196-210-150-129.dynamic.isadsl.co.za [196.210.150.129]
3 13 ms 13 ms 12 ms cdsl2-ctn-vl2276.ip.isnet.net [196.38.72.125]
4 12 ms 13 ms 12 ms 196.35.115.136
5 13 ms 13 ms 13 ms mi-za-cpt-p8-te0-0-0-0.ip.isnet.net [168.209.6.13]
6 12 ms 12 ms 12 ms 168.209.6.130

7 12 ms 12 ms 12 ms 41-208-29-210.mtnns.net [41.208.29.210]
8 13 ms 16 ms 13 ms rb-cr-1.za.nl-ha-2.za-a.mtnns.net [196.44.0.120]
9 14 ms 14 ms 14 ms tb-cr-2.za--ct-cr-1.za-a.mtnns.net [196.44.31.107]
10 32 ms 32 ms 32 ms jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
11 34 ms 35 ms 35 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
12 34 ms 34 ms 35 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.
good.

=5pm=
=Afrihost=

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

1 1 ms 1 ms 1 ms 192.168.0.1
2 11 ms 11 ms 11 ms 105-236-5-193-esr-lo.mtnbusiness.co.za [105.236.5.193]
3 356 ms 341 ms 340 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]

4 392 ms 367 ms 363 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 334 ms 335 ms 333 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 387 ms 374 ms 379 ms pe-cr-2.za--el-mse-1.za.mtnns.net [196.44.31.66]
7 397 ms 368 ms 384 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
8 366 ms 370 ms 373 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.
bad.


=WebAfrica=

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

1 <1 ms 1 ms 1 ms 192.168.0.1
2 12 ms 11 ms 11 ms 196-210-150-129.dynamic.isadsl.co.za [196.210.150.129]
3 12 ms 12 ms 12 ms cdsl1-ctn-vl2173.ip.isnet.net [196.38.72.113]
4 12 ms 13 ms 13 ms 196.35.115.128
5 13 ms 13 ms 14 ms mi-za-cpt-p8-te0-7-0-0.ip.isnet.net [168.209.2.13]
6 13 ms 12 ms 12 ms 168.209.6.131

7 13 ms 14 ms 13 ms mtnns-2.cinx.net.za [196.223.22.31]
8 14 ms 13 ms 13 ms rb-cr-1.za.nl-ha-2.za-a.mtnns.net [196.44.0.120]
9 13 ms 14 ms 13 ms tb-cr-2.za--ct-cr-1.za-a.mtnns.net [196.44.31.107]
10 35 ms 35 ms 35 ms pe-cr-2.za--el-mse-1.za.mtnns.net [196.44.31.66]
11 31 ms 31 ms 31 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
12 31 ms 32 ms 32 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.
good.

=8:50pm=
=Afrihost=

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

1 <1 ms 1 ms 1 ms 192.168.0.1
2 11 ms 11 ms 11 ms 105-236-5-193-esr-lo.mtnbusiness.co.za [105.236.5.193]
3 400 ms 390 ms 387 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]

4 404 ms 415 ms 421 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 403 ms 395 ms 397 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 396 ms 397 ms 401 ms jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
7 411 ms 451 ms 420 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
8 412 ms 418 ms 422 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.
bad.
=Web Africa=
Tracing route to www.afrihost.co.za [41.181.185.18]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms 192.168.0.1
2 11 ms 11 ms 11 ms 196-210-150-129.dynamic.isadsl.co.za [196.210.150.129]
3 12 ms 13 ms 12 ms cdsl2-ctn-vl2276.ip.isnet.net [196.38.72.125]
4 13 ms 12 ms 12 ms 196.35.115.136
5 14 ms 14 ms 13 ms mi-za-cpt-p8-te0-7-0-0.ip.isnet.net [168.209.2.13]

6 13 ms 13 ms 13 ms 168.209.2.130
7 12 ms 46 ms 13 ms 41-208-29-210.mtnns.net [41.208.29.210]
8 13 ms 14 ms 14 ms rb-cr-1.za.nl-ha-2.za-a.mtnns.net [196.44.0.120]
9 15 ms 14 ms 14 ms tb-cr-2.za--ct-cr-1.za-a.mtnns.net [196.44.31.107]
10 35 ms 36 ms 35 ms jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
11 35 ms 35 ms 35 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
12 31 ms 32 ms 32 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.

good.
 
I am about to toss in the towel with Afrihost.
Trying to download now on uncapped - getting throttled to death. No problem, switch to a capped Afrihost account. Still throttled (not much difference, 15kB/s).

Switch to a CyberSmart account and I am up to 600kB/s. So Afrihost capped and uncapped equally hopeless.

We definitely don't throttle Capped accounts (or Uncapped accounts) so I would need to know more about the specific example you are looking at.

My downloads were pretty decent (not amazing, but definitely within expected range) so I don't think there was a throughput issue in the North yesterday :(
 
Getting almost 320ms to EU servers in War Thunder whereas used to be 220ms.

Managed to catch the game server IP and trace route it. Very bad.

Afrihost:
Code:
Tracing route to 37.48.71.136 over a maximum of 30 hops

  1     1 ms    <1 ms    <1 ms  home.gateway.home.gateway [192.168.1.254]
  2     *        *        *     Request timed out.
  3    87 ms    88 ms   100 ms  41.181.221.217
  4   108 ms   109 ms   116 ms  41.181.221.218
  5   108 ms   108 ms   104 ms  rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.118]
  6   309 ms   302 ms   295 ms  rb-cr-2.za--rb-dca-2.za-b.mtnns.net [196.44.0.155]
  7   321 ms   315 ms   316 ms  jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
  8   309 ms   293 ms   298 ms  ls-cr-2.uk--rb-cr-1.za-g.mtnns.net [196.44.31.114]
  9   299 ms   306 ms   308 ms  ls-pr-1.uk--ls-cr-2.uk-a.mtn.net [209.212.111.201]
 10   313 ms   311 ms   314 ms  peering.thn.lon.leaseweb.net [195.66.225.56]
 11   306 ms   310 ms   313 ms  tengige0-13-0-2.crs-evo.leaseweb.net [31.31.32.73]
 12   303 ms   302 ms   315 ms  85.17.100.241
 13   301 ms   297 ms   296 ms  po1004.ngn-ams1-cs1-new.leaseweb.net [37.48.95.199]
 14   297 ms   301 ms   301 ms  37.48.71.136

Trace complete.

100ms on the 3rd hope. C'mon. This is now the 3rd time in 3 weeks you guys have had this issue. This is starting to become annoying.

WebAfrica:
Code:
Tracing route to 37.48.71.136 over a maximum of 30 hops

  1     1 ms    <1 ms    <1 ms  home.gateway.home.gateway [192.168.1.254]
  2     *        *        *     Request timed out.
  3     9 ms     9 ms    10 ms  196.38.74.246
  4     7 ms     8 ms     7 ms  cdsl1-umh-gi0-0-0-3102.ip.isnet.net [196.38.74.245]
  5     7 ms     9 ms     8 ms  196.26.210.200
  6     9 ms     9 ms     8 ms  mi-za-umh-p8-ten-0-0-0-1.ip.isnet.net [168.209.93.240]
  7   198 ms   199 ms   195 ms  168.209.246.66
  8   195 ms   194 ms   190 ms  168.209.246.65
  9   195 ms   196 ms   195 ms  peering.thn.lon.leaseweb.net [195.66.225.56]
 10   202 ms   203 ms   206 ms  tengige0-9-0-2.crs-evo.leaseweb.net [31.31.32.69]
 11   204 ms   204 ms   204 ms  tengige0-6-0-5.ngn-ams1-cr2-new.leaseweb.net [85.17.100.187]
 12   199 ms   198 ms   204 ms  po1004.ngn-ams1-cs1-new.leaseweb.net [37.48.95.199]
 13   203 ms   202 ms   203 ms  37.48.71.136

Trace complete.

From the two traces definitely looks like latency on our side. My reports show that there was high demand in the South and East over the public holiday and we definitely saw intermittent latency mostly in the afternoon to early evening. We have reported this to the network team :(
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X