Afrihost Capped DSL Feedback

AfriGenie

AfriGenie

Afrihost
Company Rep
Joined
Oct 9, 2014
Messages
7,266
bigboy529 said:
Who here is on Shaped Capped or recently moved from Unshaped to Shaped?
I'm thinking of moving from Unshaped to Shaped to get more data and wonder whether it will be worthit.
Is shaped fine or do they shape a lot or for no reason? Is it truly like advertised on the website that realtime services like browsing and streaming will never be shaped?

I don't torrent and don't download large files apart from software updates which doesn't happen that often. My main use is streaming Youtube, Netflix etc, then also general browsing email etc and quite a bit of cloud uploads and downloads, Google Drive, iCloud drive etc.
Click to expand...

I'm on a Shaped Capped account and I haven't noticed shaping affecting my Google Drive. Although I should point out that I mainly use it for Word Documents and PDFs so the file sizes aren't more than a few MBs.

The only thing that is shaped on a the Shape Capped accounts is the P2P and HTTP downloads so it's definitely worth a try if you are mainly going to be streaming.
 
S

standerr

Well-Known Member
Joined
Feb 14, 2012
Messages
390
AfriGenie said:
Hi!

There has been no change to our activity on the MyBB forums.

If there are any issues or problems that you are experiencing we definitely need to look into that for you.
Click to expand...

I tend to have the latency increases that we've become so accustomed too in the evenings. It happens every evening without skipping a beat. Bras pings are normally fine. Sometimes you feel it while browsing, while others it's less noticeable. It's always visible in PRTG sensors though.
news24.png
Normally downloads are not adversely affected, but the latency can get quite annoying.

Last night was a different story though. I tried two international sources and both were stuck at 30Kb/s. It took me 2 hours to download 250Mb. Latency wise it was not the worse evening though. So only http downloads were massively affected for me.

I'm supposed to be on an unshaped account. It would be good if you can check that my account is actually in the correct bandwidth pool on your side.
If it is then it can only be one of two things. Exchange or Afrihost capacity. While I was with Crystalweb I did find the latency spikes were not as big as with Afrihost, for what it's worth. They had other issues though ;)
 
B

Bl1zz4rd

Senior Member
Joined
Jul 2, 2010
Messages
650
Update: AfriGenie reset my port and my speed is back to normal. Not sure what happened, but at least it's fixed. Thanks again! :)
 
S

standerr

Well-Known Member
Joined
Feb 14, 2012
Messages
390
Same thing happening again tonight. Http downloads down to nothing. It's not the remote site though, because via my work internet connection it works fine.

Work
500Mb Download Work.png

Home
500Mb Download Home.png

Ping to bras
Code: 
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=20ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=20ms TTL=62
Reply from 155.239.255.250: bytes=32 time=20ms TTL=62
Reply from 155.239.255.250: bytes=32 time=20ms TTL=62
Reply from 155.239.255.250: bytes=32 time=19ms TTL=62
Reply from 155.239.255.250: bytes=32 time=27ms TTL=62
Reply from 155.239.255.250: bytes=32 time=20ms TTL=62
Reply from 155.239.255.250: bytes=32 time=20ms TTL=62
Reply from 155.239.255.250: bytes=32 time=20ms TTL=62

Latency to my domain from work
Code: 
Pinging www.exa.co.za [197.221.2.20] with 32 bytes of data:
Reply from 197.221.2.20: bytes=32 time=6ms TTL=57
Reply from 197.221.2.20: bytes=32 time=5ms TTL=57
Reply from 197.221.2.20: bytes=32 time=4ms TTL=57
Reply from 197.221.2.20: bytes=32 time=18ms TTL=57
Reply from 197.221.2.20: bytes=32 time=5ms TTL=57
Reply from 197.221.2.20: bytes=32 time=4ms TTL=57
Reply from 197.221.2.20: bytes=32 time=4ms TTL=57
Reply from 197.221.2.20: bytes=32 time=5ms TTL=57
Reply from 197.221.2.20: bytes=32 time=5ms TTL=57
Reply from 197.221.2.20: bytes=32 time=6ms TTL=57

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

From home with Afrihost
Code: 
Pinging www.exa.co.za [197.221.2.20] with 32 bytes of data:
Reply from 197.221.2.20: bytes=32 time=110ms TTL=57
Reply from 197.221.2.20: bytes=32 time=120ms TTL=57
Reply from 197.221.2.20: bytes=32 time=137ms TTL=57
Reply from 197.221.2.20: bytes=32 time=123ms TTL=57
Reply from 197.221.2.20: bytes=32 time=59ms TTL=57
Reply from 197.221.2.20: bytes=32 time=102ms TTL=57
Request timed out.
Request timed out.
Reply from 197.221.2.20: bytes=32 time=130ms TTL=57
Reply from 197.221.2.20: bytes=32 time=246ms TTL=57

Ping statistics for 197.221.2.20:
    Packets: Sent = 10, Received = 8, Lost = 2 (20% loss),
Approximate round trip times in milli-seconds:
    Minimum = 59ms, Maximum = 246ms, Average = 128ms

Same is visible in PRTG, but as seen in the graph all is fine before happy hours in the evening
exa_prtg.png

Tracert from home
Code: 
Tracing route to www.exa.co.za [197.221.2.20]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2    <1 ms    <1 ms    <1 ms  10.100.0.1 
  3     *        *        *     Request timed out.
  4   140 ms   139 ms   139 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  5    20 ms    18 ms    25 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  6    18 ms    19 ms    18 ms  hetzner2.ixp.capetown [196.10.140.21] 
  7    48 ms    49 ms    53 ms  core-access-switch1-vlan1001.cpt.host-h.net [196.40.102.70] 
  8   132 ms   131 ms   131 ms  www20.cpt1.host-h.net [197.221.2.20] 

Trace complete.

Seems Afrihost is still out of capacity in the South :crying:
 
Last edited:
S

standerr

Well-Known Member
Joined
Feb 14, 2012
Messages
390
Switch to a free 1GB Crystalweb account

Code: 
Pinging www.exa.co.za [197.221.2.20] with 32 bytes of data:
Reply from 197.221.2.20: bytes=32 time=22ms TTL=51
Reply from 197.221.2.20: bytes=32 time=22ms TTL=51
Reply from 197.221.2.20: bytes=32 time=21ms TTL=51
Reply from 197.221.2.20: bytes=32 time=22ms TTL=51
Reply from 197.221.2.20: bytes=32 time=25ms TTL=51
Reply from 197.221.2.20: bytes=32 time=26ms TTL=51
Reply from 197.221.2.20: bytes=32 time=21ms TTL=51
Reply from 197.221.2.20: bytes=32 time=25ms TTL=51
Reply from 197.221.2.20: bytes=32 time=24ms TTL=51
Reply from 197.221.2.20: bytes=32 time=21ms TTL=51
Reply from 197.221.2.20: bytes=32 time=218ms TTL=51
Reply from 197.221.2.20: bytes=32 time=22ms TTL=51
Reply from 197.221.2.20: bytes=32 time=31ms TTL=51
Reply from 197.221.2.20: bytes=32 time=22ms TTL=51
Reply from 197.221.2.20: bytes=32 time=26ms TTL=51
Reply from 197.221.2.20: bytes=32 time=23ms TTL=51
Reply from 197.221.2.20: bytes=32 time=21ms TTL=51
Reply from 197.221.2.20: bytes=32 time=175ms TTL=51
Reply from 197.221.2.20: bytes=32 time=22ms TTL=51
Reply from 197.221.2.20: bytes=32 time=25ms TTL=51

Ping statistics for 197.221.2.20:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 21ms, Maximum = 218ms, Average = 40ms

Code: 
Tracing route to www.exa.co.za [197.221.2.20]
over a maximum of 30 hops:

  1     3 ms     5 ms     2 ms  10.0.0.254
  2     2 ms     2 ms     2 ms  10.100.0.1
  3     *        *        *     Request timed out.
  4    28 ms    21 ms    21 ms  196.38.75.70
  5    23 ms    21 ms    21 ms  196.38.75.69
  6    21 ms    21 ms    21 ms  196.35.115.128
  7    21 ms    22 ms    21 ms  mi-za-cpt-p7-te0-0-0-0.ip.isnet.net [168.209.6.12]
  8    21 ms    21 ms    21 ms  css1-ctn-gi0-1.ip.isnet.net [168.209.2.10]
  9    21 ms    21 ms    22 ms  196.36.84.154
 10    21 ms    21 ms    21 ms  core.xe-0-0-0-wc-ro-het-mee-1.za.africainx.net [41.84.13.37]
 11    21 ms    22 ms    21 ms  41-66-133-2-3.het001-cpe-1.africainx.net [41.66.133.2]
 12    23 ms    22 ms    23 ms  core-access-switch1-vlan1001.cpt.host-h.net [196.40.102.70]
 13    21 ms    22 ms    20 ms  www20.cpt1.host-h.net [197.221.2.20]

Trace complete.

Then back to Afrihost
Code: 
Pinging www.exa.co.za [197.221.2.20] with 32 bytes of data:
Reply from 197.221.2.20: bytes=32 time=46ms TTL=57
Reply from 197.221.2.20: bytes=32 time=62ms TTL=57
Reply from 197.221.2.20: bytes=32 time=103ms TTL=57
Reply from 197.221.2.20: bytes=32 time=43ms TTL=57
Reply from 197.221.2.20: bytes=32 time=99ms TTL=57
Reply from 197.221.2.20: bytes=32 time=85ms TTL=57
Reply from 197.221.2.20: bytes=32 time=96ms TTL=57
Reply from 197.221.2.20: bytes=32 time=95ms TTL=57
Reply from 197.221.2.20: bytes=32 time=86ms TTL=57
Reply from 197.221.2.20: bytes=32 time=105ms TTL=57
Reply from 197.221.2.20: bytes=32 time=98ms TTL=57
Reply from 197.221.2.20: bytes=32 time=124ms TTL=57
Reply from 197.221.2.20: bytes=32 time=82ms TTL=57
Reply from 197.221.2.20: bytes=32 time=113ms TTL=57
Reply from 197.221.2.20: bytes=32 time=57ms TTL=57
Reply from 197.221.2.20: bytes=32 time=75ms TTL=57
Reply from 197.221.2.20: bytes=32 time=74ms TTL=57
Reply from 197.221.2.20: bytes=32 time=96ms TTL=57
Reply from 197.221.2.20: bytes=32 time=108ms TTL=57
Reply from 197.221.2.20: bytes=32 time=106ms TTL=57

Ping statistics for 197.221.2.20:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 43ms, Maximum = 124ms, Average = 87ms

Code: 
Tracing route to www.exa.co.za [197.221.2.20]
over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  10.0.0.254
  2     2 ms     2 ms     2 ms  10.100.0.1
  3     *        *        *     Request timed out.
  4   120 ms   228 ms    73 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82]
  5   114 ms   109 ms   107 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6    93 ms    96 ms    90 ms  hetzner2.ixp.capetown [196.10.140.21]
  7    96 ms    96 ms    94 ms  core-access-switch1-vlan1001.cpt.host-h.net [196.40.102.70]
  8    78 ms    80 ms    91 ms  www20.cpt1.host-h.net [197.221.2.20]

Trace complete.
 
AfriGenie

AfriGenie

Afrihost
Company Rep
Joined
Oct 9, 2014
Messages
7,266
Bl1zz4rd said:
Update: AfriGenie reset my port and my speed is back to normal. Not sure what happened, but at least it's fixed. Thanks again! :)
Click to expand...

Awesome! :D Thanks for the update! If there is any change, please let me know!
 
AfriGenie

AfriGenie

Afrihost
Company Rep
Joined
Oct 9, 2014
Messages
7,266
standerr said:
Same thing happening again tonight. Http downloads down to nothing. It's not the remote site though, because via my work internet connection it works fine.

Work
View attachment 450760

Home
View attachment 450762

Ping to bras
Code: 
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=20ms TTL=62
Reply from 155.239.255.250: bytes=32 time=21ms TTL=62
Reply from 155.239.255.250: bytes=32 time=20ms TTL=62
Reply from 155.239.255.250: bytes=32 time=20ms TTL=62
Reply from 155.239.255.250: bytes=32 time=20ms TTL=62
Reply from 155.239.255.250: bytes=32 time=19ms TTL=62
Reply from 155.239.255.250: bytes=32 time=27ms TTL=62
Reply from 155.239.255.250: bytes=32 time=20ms TTL=62
Reply from 155.239.255.250: bytes=32 time=20ms TTL=62
Reply from 155.239.255.250: bytes=32 time=20ms TTL=62

Latency to my domain from work
Code: 
Pinging www.exa.co.za [197.221.2.20] with 32 bytes of data:
Reply from 197.221.2.20: bytes=32 time=6ms TTL=57
Reply from 197.221.2.20: bytes=32 time=5ms TTL=57
Reply from 197.221.2.20: bytes=32 time=4ms TTL=57
Reply from 197.221.2.20: bytes=32 time=18ms TTL=57
Reply from 197.221.2.20: bytes=32 time=5ms TTL=57
Reply from 197.221.2.20: bytes=32 time=4ms TTL=57
Reply from 197.221.2.20: bytes=32 time=4ms TTL=57
Reply from 197.221.2.20: bytes=32 time=5ms TTL=57
Reply from 197.221.2.20: bytes=32 time=5ms TTL=57
Reply from 197.221.2.20: bytes=32 time=6ms TTL=57

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

From home with Afrihost
Code: 
Pinging www.exa.co.za [197.221.2.20] with 32 bytes of data:
Reply from 197.221.2.20: bytes=32 time=110ms TTL=57
Reply from 197.221.2.20: bytes=32 time=120ms TTL=57
Reply from 197.221.2.20: bytes=32 time=137ms TTL=57
Reply from 197.221.2.20: bytes=32 time=123ms TTL=57
Reply from 197.221.2.20: bytes=32 time=59ms TTL=57
Reply from 197.221.2.20: bytes=32 time=102ms TTL=57
Request timed out.
Request timed out.
Reply from 197.221.2.20: bytes=32 time=130ms TTL=57
Reply from 197.221.2.20: bytes=32 time=246ms TTL=57

Ping statistics for 197.221.2.20:
    Packets: Sent = 10, Received = 8, Lost = 2 (20% loss),
Approximate round trip times in milli-seconds:
    Minimum = 59ms, Maximum = 246ms, Average = 128ms

Same is visible in PRTG, but as seen in the graph all is fine before happy hours in the evening
View attachment 450764

Tracert from home
Code: 
Tracing route to www.exa.co.za [197.221.2.20]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2    <1 ms    <1 ms    <1 ms  10.100.0.1 
  3     *        *        *     Request timed out.
  4   140 ms   139 ms   139 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  5    20 ms    18 ms    25 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  6    18 ms    19 ms    18 ms  hetzner2.ixp.capetown [196.10.140.21] 
  7    48 ms    49 ms    53 ms  core-access-switch1-vlan1001.cpt.host-h.net [196.40.102.70] 
  8   132 ms   131 ms   131 ms  www20.cpt1.host-h.net [197.221.2.20] 

Trace complete.

Seems Afrihost is still out of capacity in the South :crying:
Click to expand...

standerr said:
Switch to a free 1GB Crystalweb account

Code: 
Pinging www.exa.co.za [197.221.2.20] with 32 bytes of data:
Reply from 197.221.2.20: bytes=32 time=22ms TTL=51
Reply from 197.221.2.20: bytes=32 time=22ms TTL=51
Reply from 197.221.2.20: bytes=32 time=21ms TTL=51
Reply from 197.221.2.20: bytes=32 time=22ms TTL=51
Reply from 197.221.2.20: bytes=32 time=25ms TTL=51
Reply from 197.221.2.20: bytes=32 time=26ms TTL=51
Reply from 197.221.2.20: bytes=32 time=21ms TTL=51
Reply from 197.221.2.20: bytes=32 time=25ms TTL=51
Reply from 197.221.2.20: bytes=32 time=24ms TTL=51
Reply from 197.221.2.20: bytes=32 time=21ms TTL=51
Reply from 197.221.2.20: bytes=32 time=218ms TTL=51
Reply from 197.221.2.20: bytes=32 time=22ms TTL=51
Reply from 197.221.2.20: bytes=32 time=31ms TTL=51
Reply from 197.221.2.20: bytes=32 time=22ms TTL=51
Reply from 197.221.2.20: bytes=32 time=26ms TTL=51
Reply from 197.221.2.20: bytes=32 time=23ms TTL=51
Reply from 197.221.2.20: bytes=32 time=21ms TTL=51
Reply from 197.221.2.20: bytes=32 time=175ms TTL=51
Reply from 197.221.2.20: bytes=32 time=22ms TTL=51
Reply from 197.221.2.20: bytes=32 time=25ms TTL=51

Ping statistics for 197.221.2.20:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 21ms, Maximum = 218ms, Average = 40ms

Code: 
Tracing route to www.exa.co.za [197.221.2.20]
over a maximum of 30 hops:

  1     3 ms     5 ms     2 ms  10.0.0.254
  2     2 ms     2 ms     2 ms  10.100.0.1
  3     *        *        *     Request timed out.
  4    28 ms    21 ms    21 ms  196.38.75.70
  5    23 ms    21 ms    21 ms  196.38.75.69
  6    21 ms    21 ms    21 ms  196.35.115.128
  7    21 ms    22 ms    21 ms  mi-za-cpt-p7-te0-0-0-0.ip.isnet.net [168.209.6.12]
  8    21 ms    21 ms    21 ms  css1-ctn-gi0-1.ip.isnet.net [168.209.2.10]
  9    21 ms    21 ms    22 ms  196.36.84.154
 10    21 ms    21 ms    21 ms  core.xe-0-0-0-wc-ro-het-mee-1.za.africainx.net [41.84.13.37]
 11    21 ms    22 ms    21 ms  41-66-133-2-3.het001-cpe-1.africainx.net [41.66.133.2]
 12    23 ms    22 ms    23 ms  core-access-switch1-vlan1001.cpt.host-h.net [196.40.102.70]
 13    21 ms    22 ms    20 ms  www20.cpt1.host-h.net [197.221.2.20]

Trace complete.

Then back to Afrihost
Code: 
Pinging www.exa.co.za [197.221.2.20] with 32 bytes of data:
Reply from 197.221.2.20: bytes=32 time=46ms TTL=57
Reply from 197.221.2.20: bytes=32 time=62ms TTL=57
Reply from 197.221.2.20: bytes=32 time=103ms TTL=57
Reply from 197.221.2.20: bytes=32 time=43ms TTL=57
Reply from 197.221.2.20: bytes=32 time=99ms TTL=57
Reply from 197.221.2.20: bytes=32 time=85ms TTL=57
Reply from 197.221.2.20: bytes=32 time=96ms TTL=57
Reply from 197.221.2.20: bytes=32 time=95ms TTL=57
Reply from 197.221.2.20: bytes=32 time=86ms TTL=57
Reply from 197.221.2.20: bytes=32 time=105ms TTL=57
Reply from 197.221.2.20: bytes=32 time=98ms TTL=57
Reply from 197.221.2.20: bytes=32 time=124ms TTL=57
Reply from 197.221.2.20: bytes=32 time=82ms TTL=57
Reply from 197.221.2.20: bytes=32 time=113ms TTL=57
Reply from 197.221.2.20: bytes=32 time=57ms TTL=57
Reply from 197.221.2.20: bytes=32 time=75ms TTL=57
Reply from 197.221.2.20: bytes=32 time=74ms TTL=57
Reply from 197.221.2.20: bytes=32 time=96ms TTL=57
Reply from 197.221.2.20: bytes=32 time=108ms TTL=57
Reply from 197.221.2.20: bytes=32 time=106ms TTL=57

Ping statistics for 197.221.2.20:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 43ms, Maximum = 124ms, Average = 87ms

Code: 
Tracing route to www.exa.co.za [197.221.2.20]
over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  10.0.0.254
  2     2 ms     2 ms     2 ms  10.100.0.1
  3     *        *        *     Request timed out.
  4   120 ms   228 ms    73 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82]
  5   114 ms   109 ms   107 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6    93 ms    96 ms    90 ms  hetzner2.ixp.capetown [196.10.140.21]
  7    96 ms    96 ms    94 ms  core-access-switch1-vlan1001.cpt.host-h.net [196.40.102.70]
  8    78 ms    80 ms    91 ms  www20.cpt1.host-h.net [197.221.2.20]

Trace complete.
Click to expand...

I'm pretty sure it's not a capacity issue, but we need to figure out what's going on.

Could you quickly PM me the account details that you are connecting with.
 
S

standerr

Well-Known Member
Joined
Feb 14, 2012
Messages
390
Are any of you guys also experiencing slow speed not in the south? Just trying to understand if this is region specific.
 
Creag

Creag

The Boar's Rock
Joined
May 19, 2009
Messages
43,527
Another evening of miserable performance! Starting to feel like this is the future of Afrihost experience with 4mbps.

Afrihost.jpg
 
You must log in or register to reply here.
Top