Afrihost Uncapped ADSL Feedback (Pt3)

Status
Not open for further replies.
That's horrible :(
I'll need to check some ping and traceroute results though, have you run any of these?

Code:
Tracing route to afrihost.com [197.242.144.102]
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   323 ms   312 ms   315 ms  41.181.221.217
  4   335 ms   333 ms   327 ms  41.181.221.218
  5   294 ms   288 ms   293 ms  rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.118]
  6   305 ms   306 ms   328 ms  rb-dca-2.za--rb-cr-1.mtnns.net [196.44.31.122]
  7   298 ms   298 ms   294 ms  jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.22
1]
  8   312 ms   319 ms   316 ms  196.31.220.12
  9   317 ms   312 ms   315 ms  196.31.220.27
 10   316 ms   308 ms   308 ms  196.31.63.202
 11   296 ms   294 ms   293 ms  vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
 12   303 ms   298 ms   296 ms  cms-gm.afrihost.com [197.242.144.102]

Trace complete.
 
Code:
Tracing route to afrihost.com [197.242.144.102]
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   323 ms   312 ms   315 ms  41.181.221.217
  4   335 ms   333 ms   327 ms  41.181.221.218
  5   294 ms   288 ms   293 ms  rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.118]
  6   305 ms   306 ms   328 ms  rb-dca-2.za--rb-cr-1.mtnns.net [196.44.31.122]
  7   298 ms   298 ms   294 ms  jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.22
1]
  8   312 ms   319 ms   316 ms  196.31.220.12
  9   317 ms   312 ms   315 ms  196.31.220.27
 10   316 ms   308 ms   308 ms  196.31.63.202
 11   296 ms   294 ms   293 ms  vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
 12   303 ms   298 ms   296 ms  cms-gm.afrihost.com [197.242.144.102]

Trace complete.

Some high latency here, but hard to pinpoint where exactly it's coming in.
What happens when you ping 41.181.221.217? Also, have you tried another account to replicate the issues?
 
Some high latency here, but hard to pinpoint where exactly it's coming in.
What happens when you ping 41.181.221.217? Also, have you tried another account to replicate the issues?

Post and a half incoming.

Afrihost uncapped:
Code:
Tracing route to 41.181.221.217 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   284 ms   281 ms   286 ms  41.181.221.217

Afrihost 1GB Free:
Code:
Tracing route to 41.181.221.217 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   284 ms   281 ms   286 ms  41.181.221.217

WebAfrica 1GB:
Code:
Tracing route to 41.181.221.217 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    10 ms    10 ms     9 ms  196.38.74.246
  4     9 ms     9 ms     8 ms  cdsl1-umh-gi0-0-0-3102.ip.isnet.net [196.38.74.245]
  5    10 ms     9 ms     8 ms  196.26.210.200
  6    11 ms    10 ms     9 ms  mi-za-umh-p8-ten-0-0-0-1.ip.isnet.net [168.209.93.240]
  7    25 ms    22 ms    22 ms  168.209.0.178
  8    21 ms    21 ms    21 ms  core1a-bry-gi1-0-0.ip.isnet.net [168.209.218.1]

  9    22 ms    22 ms    22 ms  core1a-pkl-te-0-0-0-1.ip.isnet.net [168.209.100.77]
 10    63 ms    26 ms    26 ms  196.26.0.10
 11    24 ms    24 ms    24 ms  mtnns-2.jinx.net.za [196.223.14.31]
 12    38 ms    25 ms    24 ms  jh-cr-2.za--jh-pr-1.za.mtnns.net [196.44.0.223]

 13    26 ms    24 ms    24 ms  rb-cr-1.za--jh-cr-2.za-a.mtnns.net [196.44.31.94]
 14    24 ms    24 ms    24 ms  rb-cr-2.za--rb-dca-1.za-a.mtnns.net [196.44.31.1
23]
 15     *       24 ms    24 ms  qux--rb-dca-2.za-a.za.mtnbusiness.net [41.181.165.117]
 16    33 ms    32 ms    33 ms  41.181.221.217

Trace complete.



=======================================
Pings to Afrihost.com

WebAfrica free 1GB:
Code:
Pinging afrihost.com [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=25ms TTL=54
Reply from 197.242.144.102: bytes=32 time=25ms TTL=54
Reply from 197.242.144.102: bytes=32 time=24ms TTL=54
Reply from 197.242.144.102: bytes=32 time=25ms TTL=54

Ping statistics for 197.242.144.102:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 24ms, Maximum = 25ms, Average = 24ms

Afrihost Uncapped:
Code:
Pinging afrihost.com [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=275ms TTL=58
Reply from 197.242.144.102: bytes=32 time=276ms TTL=58
Reply from 197.242.144.102: bytes=32 time=278ms TTL=58
Reply from 197.242.144.102: bytes=32 time=275ms TTL=58

Ping statistics for 197.242.144.102:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 275ms, Maximum = 278ms, Average = 276ms

Afrihost 1GB:
Code:
Pinging afrihost.com [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=296ms TTL=58
Reply from 197.242.144.102: bytes=32 time=280ms TTL=58
Reply from 197.242.144.102: bytes=32 time=269ms TTL=58
Reply from 197.242.144.102: bytes=32 time=285ms TTL=58

Ping statistics for 197.242.144.102:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 269ms, Maximum = 296ms, Average = 282ms
 
Post and a half incoming.

Afrihost uncapped:
Code:
Tracing route to 41.181.221.217 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   284 ms   281 ms   286 ms  41.181.221.217

Afrihost 1GB Free:
Code:
Tracing route to 41.181.221.217 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   284 ms   281 ms   286 ms  41.181.221.217

WebAfrica 1GB:
Code:
Tracing route to 41.181.221.217 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    10 ms    10 ms     9 ms  196.38.74.246
  4     9 ms     9 ms     8 ms  cdsl1-umh-gi0-0-0-3102.ip.isnet.net [196.38.74.245]
  5    10 ms     9 ms     8 ms  196.26.210.200
  6    11 ms    10 ms     9 ms  mi-za-umh-p8-ten-0-0-0-1.ip.isnet.net [168.209.93.240]
  7    25 ms    22 ms    22 ms  168.209.0.178
  8    21 ms    21 ms    21 ms  core1a-bry-gi1-0-0.ip.isnet.net [168.209.218.1]

  9    22 ms    22 ms    22 ms  core1a-pkl-te-0-0-0-1.ip.isnet.net [168.209.100.77]
 10    63 ms    26 ms    26 ms  196.26.0.10
 11    24 ms    24 ms    24 ms  mtnns-2.jinx.net.za [196.223.14.31]
 12    38 ms    25 ms    24 ms  jh-cr-2.za--jh-pr-1.za.mtnns.net [196.44.0.223]

 13    26 ms    24 ms    24 ms  rb-cr-1.za--jh-cr-2.za-a.mtnns.net [196.44.31.94]
 14    24 ms    24 ms    24 ms  rb-cr-2.za--rb-dca-1.za-a.mtnns.net [196.44.31.1
23]
 15     *       24 ms    24 ms  qux--rb-dca-2.za-a.za.mtnbusiness.net [41.181.165.117]
 16    33 ms    32 ms    33 ms  41.181.221.217

Trace complete.



=======================================
Pings to Afrihost.com

WebAfrica free 1GB:
Code:
Pinging afrihost.com [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=25ms TTL=54
Reply from 197.242.144.102: bytes=32 time=25ms TTL=54
Reply from 197.242.144.102: bytes=32 time=24ms TTL=54
Reply from 197.242.144.102: bytes=32 time=25ms TTL=54

Ping statistics for 197.242.144.102:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 24ms, Maximum = 25ms, Average = 24ms

Afrihost Uncapped:
Code:
Pinging afrihost.com [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=275ms TTL=58
Reply from 197.242.144.102: bytes=32 time=276ms TTL=58
Reply from 197.242.144.102: bytes=32 time=278ms TTL=58
Reply from 197.242.144.102: bytes=32 time=275ms TTL=58

Ping statistics for 197.242.144.102:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 275ms, Maximum = 278ms, Average = 276ms

Afrihost 1GB:
Code:
Pinging afrihost.com [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=296ms TTL=58
Reply from 197.242.144.102: bytes=32 time=280ms TTL=58
Reply from 197.242.144.102: bytes=32 time=269ms TTL=58
Reply from 197.242.144.102: bytes=32 time=285ms TTL=58

Ping statistics for 197.242.144.102:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 269ms, Maximum = 296ms, Average = 282ms

Happens when IPC is an issue.
 
Their network capacity is maxed and they are now trying to over manage it. Your traceroutes prove that.

Afrihost 275ms
Web Africa 10ms
 
Post and a half incoming.

Afrihost uncapped:
Code:
Tracing route to 41.181.221.217 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   284 ms   281 ms   286 ms  41.181.221.217

Afrihost 1GB Free:
Code:
Tracing route to 41.181.221.217 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   284 ms   281 ms   286 ms  41.181.221.217

WebAfrica 1GB:
Code:
Tracing route to 41.181.221.217 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    10 ms    10 ms     9 ms  196.38.74.246
  4     9 ms     9 ms     8 ms  cdsl1-umh-gi0-0-0-3102.ip.isnet.net [196.38.74.245]
  5    10 ms     9 ms     8 ms  196.26.210.200
  6    11 ms    10 ms     9 ms  mi-za-umh-p8-ten-0-0-0-1.ip.isnet.net [168.209.93.240]
  7    25 ms    22 ms    22 ms  168.209.0.178
  8    21 ms    21 ms    21 ms  core1a-bry-gi1-0-0.ip.isnet.net [168.209.218.1]

  9    22 ms    22 ms    22 ms  core1a-pkl-te-0-0-0-1.ip.isnet.net [168.209.100.77]
 10    63 ms    26 ms    26 ms  196.26.0.10
 11    24 ms    24 ms    24 ms  mtnns-2.jinx.net.za [196.223.14.31]
 12    38 ms    25 ms    24 ms  jh-cr-2.za--jh-pr-1.za.mtnns.net [196.44.0.223]

 13    26 ms    24 ms    24 ms  rb-cr-1.za--jh-cr-2.za-a.mtnns.net [196.44.31.94]
 14    24 ms    24 ms    24 ms  rb-cr-2.za--rb-dca-1.za-a.mtnns.net [196.44.31.1
23]
 15     *       24 ms    24 ms  qux--rb-dca-2.za-a.za.mtnbusiness.net [41.181.165.117]
 16    33 ms    32 ms    33 ms  41.181.221.217

Trace complete.



=======================================
Pings to Afrihost.com

WebAfrica free 1GB:
Code:
Pinging afrihost.com [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=25ms TTL=54
Reply from 197.242.144.102: bytes=32 time=25ms TTL=54
Reply from 197.242.144.102: bytes=32 time=24ms TTL=54
Reply from 197.242.144.102: bytes=32 time=25ms TTL=54

Ping statistics for 197.242.144.102:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 24ms, Maximum = 25ms, Average = 24ms

Afrihost Uncapped:
Code:
Pinging afrihost.com [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=275ms TTL=58
Reply from 197.242.144.102: bytes=32 time=276ms TTL=58
Reply from 197.242.144.102: bytes=32 time=278ms TTL=58
Reply from 197.242.144.102: bytes=32 time=275ms TTL=58

Ping statistics for 197.242.144.102:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 275ms, Maximum = 278ms, Average = 276ms

Afrihost 1GB:
Code:
Pinging afrihost.com [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=296ms TTL=58
Reply from 197.242.144.102: bytes=32 time=280ms TTL=58
Reply from 197.242.144.102: bytes=32 time=269ms TTL=58
Reply from 197.242.144.102: bytes=32 time=285ms TTL=58

Ping statistics for 197.242.144.102:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 269ms, Maximum = 296ms, Average = 282ms

Hhhmm, this isn't great at all :(
I know we saw higher latency yesterday, but it shouldn't be repeated again today. Drop me a PM with your DSL username and I'll see if I can get anything sorted out for you.
 
Hhhmm, this isn't great at all :(
I know we saw higher latency yesterday, but it shouldn't be repeated again today. Drop me a PM with your DSL username and I'll see if I can get anything sorted out for you.

Maybe explain why you are seeing high latency and poor throughput on your network nearly everyday. After a month of support thickets that I have not a single explanation just more excuses, tests, apologies and emojis.
 
Hi Afriguy,

I upgraded my line to 20Mbps VDSL and my Package to 20Mbps VDSL uncapped at the end of last month via the Afrihost Clientzone. Been billed accordingly from the start of this month.
My max line speed is still 10Mbps. I'm still syncing ADSL, not VDSL. I logged a ticket with your support desk last week, and they have been USELESS. Now they have stopped responding to my ticket updates altogether. Telkom coverage confirms i'm in a VDSL area, and checker shows that my line speed should be 20Mbps.

Can you please help? Ticket number -Ticket: UKB-597-81850
 
Hi Afriguy,

I upgraded my line to 20Mbps VDSL and my Package to 20Mbps VDSL uncapped at the end of last month via the Afrihost Clientzone. Been billed accordingly from the start of this month.
My max line speed is still 10Mbps. I'm still syncing ADSL, not VDSL. I logged a ticket with your support desk last week, and they have been USELESS. Now they have stopped responding to my ticket updates altogether. Telkom coverage confirms i'm in a VDSL area, and checker shows that my line speed should be 20Mbps.

Can you please help? Ticket number -Ticket: UKB-597-81850

Hi!

I've just checked on your line from my side, and it is definitely running at 20Mbps, I cannot however tell from my side if it is on VDSL or ADSL2+.

Can you please check which modulation your modem is picking at the moment, if it is on ADSL2+, let me know and I will ask our Telkom Service Manager if it is possible to switch you to VDSL mode.
 
Thanks AfriGenie,

I might be syncing to Telkom at 20Mbps, but i'm definately only getting 10Mbps from Afrihost. ADSL, not VDSL.

sync2.jpg


sync5.jpg


sync3.jpg
 
Last edited:
Thanks AfriGenie,

I might be syncing to Telkom at 20Mbps, but i'm definately only getting 10Mbps from Afrihost. ADSL, not VDSL.

sync2.jpg


sync5.jpg


sync3.jpg

The ClientZone line readings can take some time to update, so it is best to go by the readings on your ADSL modem.

I've reset the speed profile on your Uncapped account, can you please restart your modem and check if there is any change.
 
Hmmm, it's still maxing out at 9Mbps. But i hear what you say about the clientzone thing, though doesn't make that the "test" meaningless?

Ok, so just please speak to your Telkom guy to get me switched to VDSL. Would be nice to get it sorted before the weekend.
 
Last edited:
Hmmm, it's still maxing out at 9Mbps. But i hear what you say about the clientzone thing, though doesn't make that the "test" meaningless?

Ok, so just please speak to your Telkom guy to get me switched to VDSL. Would be nice to get it sorted before the weekend.

I think I'll differ with AfriGenie here, but it's a matter of experience and opinion. I always trust the results directly from the exchange over router stats. Becuase different routers report differently, what is actual throughput on one router might report at sync profile on another. The line test does read from the exchange itself, however there is a bug in Telkom's API that misreports lines over 10Mbps as all being 10Mbps.

I'd be more confident if I run the line test directly from the exchange and give you those results to work with.
 
Second night where shaping only relaxed after 2am and streaming and gaming was almost impossible. I really feel for anyone staying, something is very wrong
 
Second night where shaping only relaxed after 2am and streaming and gaming was almost impossible. I really feel for anyone staying, something is very wrong

I'm still very puzzled by why you're experiencing this, definitely not the general case. Aside from peak latency, gaming should be unaffected shaped or not during other hours. We've tested internally and with a few members from the competitive gaming community and we're definitely not seeing this on Shaped or Unshaped accounts.
 
If I was not experiencing it across two different addresses, I may buy into the hype of it being my exchange/line/whatever but having this happen in Durban and have it happen now on the South Coast ........ yeah, it's an irritation of note. Wouldn't be leaving AH if not for those issues to be honest.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X