Afrihost CAPPED ADSL Feedback (MTN)

Status
Not open for further replies.
Ah, didn't see that option until now. It's been reported before by me and some other people. Will file a bug report from the Clientzone though.

Coolios.
AfriMan might be aware of this already, would you mind dropping me a PM with a bit more info on the bug you've picked up? I'd like to see if I can replicate and escalate where possible :)
 
It seems there is something wrong with AH tonight.

Account is running at just over 1/2 speed. :mad:

My AH 50GB capped unshaped account:

3529032746.png


3529035199.png



And on my OW 20Mbps Uncapped shaped account:

3529037391.png


3529039982.png


Why is AH always so inconsistent, as this isn't the first time I see results like this? I'm moving to capped data next month but from this I'm definitely not going to invest in any more bandwidth from AH. I already have 50GB with my bundle so I'll keep that as a supplementary account.

How can AH not compete with the most hated ISP on MyBB? :D

Any idea why my experience with AH is so inconsistent? I'm in Cape Town, Blouberg area.

Here is a traceroute for good measure:

Code:
traceroute to afrihost.co.za (197.242.144.102), 64 hops max, 52 byte packets
 1  105-236-240-129-esr-lo.mtnbusiness.co.za (105.236.240.129)  8.493 ms  8.397 ms  8.221 ms
 2  41.181.201.94 (41.181.201.94)  13.032 ms  9.694 ms  10.045 ms
 3  tb-dca-2.za--qux-c.za.mtnbusiness.net (41.181.198.188)  9.616 ms  10.434 ms  10.522 ms
 4  compj-cpt-1.mtnns.net (196.44.18.2)  10.544 ms  10.296 ms  10.125 ms
 5  ct-cr-2.za--tb-cr-1.za.mtnns.net (196.44.31.134)  11.372 ms  10.814 ms  10.470 ms
 6  rb-cr-1.za--ct-cr-2.za.mtnns.net (196.44.31.69)  32.501 ms  33.432 ms  32.473 ms
 7  196.44.31.97 (196.44.31.97)  31.988 ms
    jh-dca-2.za--jh-cr-1.za-a.mtnns.net (196.44.0.221)  32.152 ms  32.359 ms
 8  196.31.220.10 (196.31.220.10)  33.172 ms
    196.30.1.39 (196.30.1.39)  32.723 ms
    196.31.220.12 (196.31.220.12)  33.423 ms
 9  196.31.220.21 (196.31.220.21)  33.458 ms  33.072 ms  32.587 ms
10  196.31.63.202 (196.31.63.202)  33.143 ms
    196.31.63.206 (196.31.63.206)  31.926 ms  32.093 ms
11  196.30.42.133 (196.30.42.133)  33.046 ms  33.225 ms  32.781 ms
12  cms-gm.afrihost.com (197.242.144.102)  34.454 ms !Z  34.310 ms !Z  34.557 ms !Z
 

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

Your average ping was 8ms
Your maximum ping was 10ms

Looking at your average ping, your line seems to be running perfectly :-)
It seems that your maximum ping is also good. If there are any issues, they most probably lie with your ISP :-(


Detailed Report

Code:
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=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=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=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=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

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/05/28 23:17:07.35

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    10 ms     7 ms     8 ms  ipc-send-tb-3a.mtnbusiness.net [41.181.53.214] 
  4     8 ms     8 ms     8 ms  tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188] 
  5     9 ms     9 ms     9 ms  compj-cpt-1.mtnns.net [196.44.18.2] 
  6     9 ms     9 ms     9 ms  ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134] 
  7     8 ms     9 ms     8 ms  196.44.0.74 
  8     9 ms     9 ms     9 ms  196-28-178-141.adsl.mweb.co.za [196.28.178.141] 
  9    12 ms    11 ms    11 ms  tengig-0-7-0-3-cpt-p-2.mweb.co.za [197.84.7.2] 
 10    10 ms     9 ms     9 ms  vl-12-cpt-hscore-2.mweb.co.za [197.84.5.254] 
 11    10 ms     9 ms     9 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70] 
 12    10 ms    10 ms    10 ms  gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166] 
 13    14 ms    10 ms    14 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    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    13 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     8 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   151 ms   151 ms   151 ms  am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.221] 
  8   152 ms   151 ms   161 ms  ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83] 
  9   152 ms   151 ms   151 ms  linx-gw1.thn.ncuk.net [195.66.224.240] 
 10   153 ms   152 ms   152 ms  te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17] 
 11   154 ms   152 ms   155 ms  te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85] 
 12   152 ms   151 ms   152 ms  www.thinkbroadband.com [80.249.99.130] 

Trace complete.

Unfortunately, this doesnt show anything.... this is an ISP problem, probably due to the lack of IPC (once again).
Throughput and consistency is non-existent... even though the line stats are good :(
 

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

Your average ping was 8ms
Your maximum ping was 10ms

Looking at your average ping, your line seems to be running perfectly :-)
It seems that your maximum ping is also good. If there are any issues, they most probably lie with your ISP :-(


Detailed Report

Code:
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=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=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=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=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

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/05/28 23:17:07.35

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    10 ms     7 ms     8 ms  ipc-send-tb-3a.mtnbusiness.net [41.181.53.214] 
  4     8 ms     8 ms     8 ms  tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188] 
  5     9 ms     9 ms     9 ms  compj-cpt-1.mtnns.net [196.44.18.2] 
  6     9 ms     9 ms     9 ms  ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134] 
  7     8 ms     9 ms     8 ms  196.44.0.74 
  8     9 ms     9 ms     9 ms  196-28-178-141.adsl.mweb.co.za [196.28.178.141] 
  9    12 ms    11 ms    11 ms  tengig-0-7-0-3-cpt-p-2.mweb.co.za [197.84.7.2] 
 10    10 ms     9 ms     9 ms  vl-12-cpt-hscore-2.mweb.co.za [197.84.5.254] 
 11    10 ms     9 ms     9 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70] 
 12    10 ms    10 ms    10 ms  gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166] 
 13    14 ms    10 ms    14 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    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    13 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     8 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   151 ms   151 ms   151 ms  am-cr-1.am--lt-cr-1.uk-a.mtnns.net [196.44.31.221] 
  8   152 ms   151 ms   161 ms  ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83] 
  9   152 ms   151 ms   151 ms  linx-gw1.thn.ncuk.net [195.66.224.240] 
 10   153 ms   152 ms   152 ms  te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17] 
 11   154 ms   152 ms   155 ms  te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85] 
 12   152 ms   151 ms   152 ms  www.thinkbroadband.com [80.249.99.130] 

Trace complete.

Unfortunately, this doesnt show anything.... this is an ISP problem, probably due to the lack of IPC (once again).
Throughput and consistency is non-existent... even though the line stats are good :(

Cool thanks, just wanted to check but I see your route is different to mine. I'm guessing that means IPC issues then.
 
if its a IPC shortage again

will all mtn networks be slow , AH,OW,axxess? that runs on mtn

or does each have there own capacity so AH may be slow in that time but axxess and ow will run fine? or any way around
 
if its a IPC shortage again

will all mtn networks be slow , AH,OW,axxess? that runs on mtn

or does each have there own capacity so AH may be slow in that time but axxess and ow will run fine? or any way around

If it's demand related (i.e. contention) then it would affect Axxess. Not sure about OpenWeb, but as far as I know they resell Axxess bandwidth for some of their products.

Remember that we have an upgrade on the way, we're just waiting for confirmation on the date from Telkom.
 
i know,its just something i have been wondering :)
as all use the same network

didnt know OW resell axxess bandwidth
3 more days!!!
 
I had the exact same problem yesterday evening which lasted until 11pm last night. Was getting less than half speed fluctuating speed test results. This started on Tuesday night for me...starts at about 6pm and fixes itself by around 11pm. During this time I got 20ms latency increase to local Counter Strike games with a few spikes over 100ms. Other accounts tested during that time ran perfectly.

Really not ideal :(
 
I had the exact same problem yesterday evening which lasted until 11pm last night. Was getting less than half speed fluctuating speed test results. This started on Tuesday night for me...starts at about 6pm and fixes itself by around 11pm. During this time I got 20ms latency increase to local Counter Strike games with a few spikes over 100ms. Other accounts tested during that time ran perfectly.

Really not ideal :(

Definitely not great. Seems to coincide with periods of high demand. I'm pretty sure that when we upgrade these should be resolved fully.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X