Afrihost Uncapped ADSL Feedback (Pt2)

Status
Not open for further replies.
Thanks,

And with an alternate? Just to eliminate Telkom?

It's not Telkom, can see it from the tracerts:

International:
Code:
Tracing route to www.google.co.uk [173.194.113.159]
over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  192.168.0.1
  2    10 ms     8 ms     8 ms  105-236-3-193-esr-lo.mtnbusiness.co.za [105.236.3.193]
  3    12 ms    11 ms    12 ms  ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178.65]
  4    13 ms    13 ms   452 ms  rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
  5    12 ms    13 ms    12 ms  jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
  6    11 ms    10 ms     9 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
  7   981 ms   899 ms   216 ms  core2.ams.net.google.com [195.69.145.100]
  8   758 ms  1047 ms  1010 ms  209.85.254.90
  9  1114 ms   827 ms   597 ms  209.85.253.249
 10  2066 ms   522 ms   751 ms  216.239.43.126
 11   553 ms     *     1042 ms  72.14.233.215
 12  1334 ms   817 ms     *     72.14.235.215
 13   628 ms  1323 ms   310 ms  ham02s11-in-f31.1e100.net [173.194.113.159]

Trace complete.

Local:
Code:
Tracing route to www.mybroadband.co.za [41.203.21.137]
over a maximum of 30 hops:

  1     3 ms     2 ms     2 ms  192.168.0.1
  2     8 ms     8 ms     9 ms  105-236-3-193-esr-lo.mtnbusiness.co.za [105.236.3.193]
  3    13 ms    11 ms    10 ms  ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178.89]
  4    13 ms    11 ms    11 ms  rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
  5    13 ms    12 ms    12 ms  jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
  6    12 ms    10 ms     9 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
  7    12 ms    12 ms    11 ms  196.44.31.99
  8    13 ms    12 ms    13 ms  196.31.220.6
  9    14 ms    12 ms    11 ms  tengigabitethernet1-1.gw20.jnb6.za.mtnbusiness.net [196.31.220.23]
 10    14 ms    10 ms    12 ms  tengigabitethernet5-1.hr9.jnb6.za.mtnbusiness.net [196.31.63.146]
 11    14 ms    11 ms    12 ms  core-router1.jnb2.host-h.net [196.30.213.108]
 12    14 ms     *       14 ms  core-access-switch1-vlan1001.jnb.host-h.net [41.72.136.53]
 13    14 ms    11 ms    10 ms  mybroadband.co.za [41.203.21.137]

Trace complete.
 
It's not Telkom, can see it from the tracerts:

International:
Code:
Tracing route to www.google.co.uk [173.194.113.159]
over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  192.168.0.1
  2    10 ms     8 ms     8 ms  105-236-3-193-esr-lo.mtnbusiness.co.za [105.236.3.193]
  3    12 ms    11 ms    12 ms  ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178.65]
  4    13 ms    13 ms   452 ms  rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
  5    12 ms    13 ms    12 ms  jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
  6    11 ms    10 ms     9 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
  7   981 ms   899 ms   216 ms  core2.ams.net.google.com [195.69.145.100]
  8   758 ms  1047 ms  1010 ms  209.85.254.90
  9  1114 ms   827 ms   597 ms  209.85.253.249
 10  2066 ms   522 ms   751 ms  216.239.43.126
 11   553 ms     *     1042 ms  72.14.233.215
 12  1334 ms   817 ms     *     72.14.235.215
 13   628 ms  1323 ms   310 ms  ham02s11-in-f31.1e100.net [173.194.113.159]

Trace complete.

Local:
Code:
Tracing route to www.mybroadband.co.za [41.203.21.137]
over a maximum of 30 hops:

  1     3 ms     2 ms     2 ms  192.168.0.1
  2     8 ms     8 ms     9 ms  105-236-3-193-esr-lo.mtnbusiness.co.za [105.236.3.193]
  3    13 ms    11 ms    10 ms  ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178.89]
  4    13 ms    11 ms    11 ms  rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
  5    13 ms    12 ms    12 ms  jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
  6    12 ms    10 ms     9 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
  7    12 ms    12 ms    11 ms  196.44.31.99
  8    13 ms    12 ms    13 ms  196.31.220.6
  9    14 ms    12 ms    11 ms  tengigabitethernet1-1.gw20.jnb6.za.mtnbusiness.net [196.31.220.23]
 10    14 ms    10 ms    12 ms  tengigabitethernet5-1.hr9.jnb6.za.mtnbusiness.net [196.31.63.146]
 11    14 ms    11 ms    12 ms  core-router1.jnb2.host-h.net [196.30.213.108]
 12    14 ms     *       14 ms  core-access-switch1-vlan1001.jnb.host-h.net [41.72.136.53]
 13    14 ms    11 ms    10 ms  mybroadband.co.za [41.203.21.137]

Trace complete.


OK, fair enough, but I just love showing up the ISP's lack of... by comparing with another ISP on another backbone.

If you don't have one to test with, PM me and I can give you an account to try?

EDIT: My philosophy is that if an ISP is having issues (like what you having) and another isn't, then I will just go there, as at the end of the day is the ISP's job to keep things going (best effort and all). They can't get it right = they don't know what they doing!
 
Last edited:
OK, fair enough, but I just love showing up the ISP's lack of... by comparing with another ISP on another backbone.

If you don't have one to test with, PM me and I can give you an account to try?

Have an Openweb account that I can test with, couldn't be asked to change to it at the moment as I'm building a new Azure environment
 
OK, fair enough, but I just love showing up the ISP's lack of... by comparing with another ISP on another backbone.

If you don't have one to test with, PM me and I can give you an account to try?

EDIT: My philosophy is that if an ISP is having issues (like what you having) and another isn't, then I will just go there, as at the end of the day is the ISP's job to keep things going (best effort and all). They can't get it right = they don't know what they doing!

We weren't showing a general decline in overseas service from our monitoring. We'd have to spend more time looking at diagnostics to see exactly where the service could be breaking down and what the commonalities and differences are. The nature of the internet is that it's a complex weaving of networks and infrastructure, and any link in the chain can fail or flap somewhere, and we need to be precise about exactly what has gone wrong in order to get it fixed. Also, we need to measure the impact. If 10k users all complain at once, yes, there is most likely a major issue. If one or two clients are complaining, then the issue is most likely more localised, and must be addressed differently.

Drop me a PM, and we'll get the testing started so we can try and sort this out for you.
 
My first post in this thread!

I joined Afri on the uncapped account now from July after being with Openweb since 2006. After Openweb decided my lack of proper service on their Gold account is an issue on my side I joined Afri. Since 1 July I have not had any issue whatsoever. I always had a capped account from Afri as backup to Openweb which always served me well. Currently downloading a large file and it runs at full speed.

So far I am 100% happy with the service I get from Afri on my uncapped account and a R100 saving per month as well. Well done Afri!
 
My first post in this thread!

I joined Afri on the uncapped account now from July after being with Openweb since 2006. After Openweb decided my lack of proper service on their Gold account is an issue on my side I joined Afri. Since 1 July I have not had any issue whatsoever. I always had a capped account from Afri as backup to Openweb which always served me well. Currently downloading a large file and it runs at full speed.

So far I am 100% happy with the service I get from Afri on my uncapped account and a R100 saving per month as well. Well done Afri!

Loving your post (and choice of MyBB Handle). Hearing that clients are getting the best service ever is what we live for. Awesome :)
 
Hey Afriman/Afrigirl/Afriguy

Just a quick question, For the past few days, i have been getting home to some strangely slow browsing speeds. Downloads run at full speeds but web browsing is quite slow. After restarting the router, the web browsing returns to full speed?

I have no idea if this is somehow a router issue, or if it could be a strange issue on your guys side? However, i have a feeling it is just me.

Btw, my account is always unshaped at these times.

Thanks!
 
Hey Afriman/Afrigirl/Afriguy

Just a quick question, For the past few days, i have been getting home to some strangely slow browsing speeds. Downloads run at full speeds but web browsing is quite slow. After restarting the router, the web browsing returns to full speed?

I have no idea if this is somehow a router issue, or if it could be a strange issue on your guys side? However, i have a feeling it is just me.

Btw, my account is always unshaped at these times.

Thanks!

What I've seen in some cases is that when your line is getting short but frequent disconnections, browsing is terrible. You think you are still online becuase the disconnections are short, but we see multiple sessions being logged on our side. Downloads will indicate full line speed, but in reality they are also not great becuase of the interruptions.

But that is just a theory. Drop me a PM and let's see what's happening under the hood. Definitely not a general issue on the network at this point :(
 
HI,

Posting this here as the Business Uncapped thread seems to be either ignored or forgotten about. My international speeds are extremely poor

http://www.speedtest.net/my-result/2857634739

http://www.speedtest.net/my-result/2857644427

I have clients in the USA and Australia, and with these speed its not possible to even use skype. Please what is going on?


As has been mentioned numerous times before ........... drop Afriman/Afriguy/Afrigirl a PM with your login details ..............
 
As has been mentioned numerous times before ........... drop Afriman/Afriguy/Afrigirl a PM with your login details ..............

Eventually tried the online support, but they also could not help. Seems like there are no official Afrihost people on the forums after hours. This is not 24/7 priority support as advertised.
 
Last edited:
HI,

Posting this here as the Business Uncapped thread seems to be either ignored or forgotten about. My international speeds are extremely poor

http://www.speedtest.net/my-result/2857634739

http://www.speedtest.net/my-result/2857644427

I have clients in the USA and Australia, and with these speed its not possible to even use skype. Please what is going on?

Sorry to hear you're having issues. We do monitor the other Afrihost threads, but they sometimes pop up late on our alerts. Will read through and make sure we're up to date.

Please drop me a PM. As far as I know Business accounts should be performing as normal, but we'll investigate this fully until we sort this out for you :)
 
Afrihost WTF!!! :cry: Last night again (17:00 to 23:00) you were doing some serious shaping or something. Ping was 400ms. Download speed ~10KBps. This has been happening every evening for over a week now :mad:
 
Afrihost WTF!!! :cry: Last night again (17:00 to 23:00) you were doing some serious shaping or something. Ping was 400ms. Download speed ~10KBps. This has been happening every evening for over a week now :mad:

Even if there is shaping, the purpose of it is to prevent latency, so high pings should not be the result of shaping. From what I see on my reports, shaping was very light last night, so I don't believe this is due to shaping. Even if a change is made, there would be say maximum a 5 minute period where, while changes are being made, bandwidth usage spikes above the optimum level while the shaper does it's thing. It definitely can't go on for a 6 hour period consistently.

Please drop me a PM so we can run some further tests. Running some traceroutes to check where the latency is being introduced will be a very good indicator if the latency is on our network or not. At this stage, it doesn't seem to be the case.
 
Okay Afriman - I have to post this in public.

Afrihost has been the BEST ISP ever. You guys listened to us down here in cape town. Not once have I been shaped this month after we reported the shaping in CPT. It really is great to have an ISP that listens to your problems, and tries to solve them.
 
Okay Afriman - I have to post this in public.

Afrihost has been the BEST ISP ever. You guys listened to us down here in cape town. Not once have I been shaped this month after we reported the shaping in CPT. It really is great to have an ISP that listens to your problems, and tries to solve them.

Thanks for the love. I must also say that we appreciate that so many heeded our call to schedule their downloads, and, with a little tweaking, we were able to improve the situation hugely :)
 
Have to echo the praise here, Afriman, I wish there was on the spot public recognition awards - you would win hands down.
Thanks for everything :)

Keep up the awesome client service!
 
Even if there is shaping, the purpose of it is to prevent latency, so high pings should not be the result of shaping. From what I see on my reports, shaping was very light last night, so I don't believe this is due to shaping. Even if a change is made, there would be say maximum a 5 minute period where, while changes are being made, bandwidth usage spikes above the optimum level while the shaper does it's thing. It definitely can't go on for a 6 hour period consistently.

Please drop me a PM so we can run some further tests. Running some traceroutes to check where the latency is being introduced will be a very good indicator if the latency is on our network or not. At this stage, it doesn't seem to be the case.

Here are some ping's, traceroute's, and speedtests.

Code:
Pinging mybroadband.co.za [41.203.21.137] with 32 bytes of data:
Reply from 41.203.21.137: bytes=32 time=189ms TTL=51
Reply from 41.203.21.137: bytes=32 time=162ms TTL=51
Reply from 41.203.21.137: bytes=32 time=112ms TTL=51
Reply from 41.203.21.137: bytes=32 time=183ms TTL=51
Reply from 41.203.21.137: bytes=32 time=205ms TTL=51
Reply from 41.203.21.137: bytes=32 time=169ms TTL=51
Reply from 41.203.21.137: bytes=32 time=126ms TTL=51
Reply from 41.203.21.137: bytes=32 time=183ms TTL=51
Reply from 41.203.21.137: bytes=32 time=191ms TTL=51
Reply from 41.203.21.137: bytes=32 time=106ms TTL=51
Reply from 41.203.21.137: bytes=32 time=100ms TTL=51
Reply from 41.203.21.137: bytes=32 time=185ms TTL=51
Reply from 41.203.21.137: bytes=32 time=196ms TTL=51
Reply from 41.203.21.137: bytes=32 time=105ms TTL=51
Reply from 41.203.21.137: bytes=32 time=193ms TTL=51
Reply from 41.203.21.137: bytes=32 time=207ms TTL=51
Reply from 41.203.21.137: bytes=32 time=212ms TTL=51
Reply from 41.203.21.137: bytes=32 time=108ms TTL=51
Reply from 41.203.21.137: bytes=32 time=141ms TTL=51
Reply from 41.203.21.137: bytes=32 time=178ms TTL=51
Reply from 41.203.21.137: bytes=32 time=251ms TTL=51
Reply from 41.203.21.137: bytes=32 time=199ms TTL=51
Reply from 41.203.21.137: bytes=32 time=118ms TTL=51
Reply from 41.203.21.137: bytes=32 time=164ms TTL=51
Reply from 41.203.21.137: bytes=32 time=166ms TTL=51
Reply from 41.203.21.137: bytes=32 time=96ms TTL=51
Reply from 41.203.21.137: bytes=32 time=170ms TTL=51
Reply from 41.203.21.137: bytes=32 time=188ms TTL=51
Reply from 41.203.21.137: bytes=32 time=139ms TTL=51
Reply from 41.203.21.137: bytes=32 time=95ms TTL=51
Reply from 41.203.21.137: bytes=32 time=217ms TTL=51
Reply from 41.203.21.137: bytes=32 time=129ms TTL=51
Reply from 41.203.21.137: bytes=32 time=157ms TTL=51
Reply from 41.203.21.137: bytes=32 time=204ms TTL=51
Reply from 41.203.21.137: bytes=32 time=115ms TTL=51
Reply from 41.203.21.137: bytes=32 time=184ms TTL=51
Reply from 41.203.21.137: bytes=32 time=210ms TTL=51
Reply from 41.203.21.137: bytes=32 time=240ms TTL=51
Reply from 41.203.21.137: bytes=32 time=75ms TTL=51
Reply from 41.203.21.137: bytes=32 time=171ms TTL=51
Reply from 41.203.21.137: bytes=32 time=207ms TTL=51
Reply from 41.203.21.137: bytes=32 time=224ms TTL=51
Reply from 41.203.21.137: bytes=32 time=90ms TTL=51
Reply from 41.203.21.137: bytes=32 time=139ms TTL=51
Reply from 41.203.21.137: bytes=32 time=175ms TTL=51
Reply from 41.203.21.137: bytes=32 time=163ms TTL=51
Reply from 41.203.21.137: bytes=32 time=149ms TTL=51
Reply from 41.203.21.137: bytes=32 time=205ms TTL=51
Reply from 41.203.21.137: bytes=32 time=241ms TTL=51
Reply from 41.203.21.137: bytes=32 time=162ms TTL=51
Reply from 41.203.21.137: bytes=32 time=172ms TTL=51
Reply from 41.203.21.137: bytes=32 time=187ms TTL=51
Reply from 41.203.21.137: bytes=32 time=255ms TTL=51
Reply from 41.203.21.137: bytes=32 time=160ms TTL=51
Reply from 41.203.21.137: bytes=32 time=211ms TTL=51
Reply from 41.203.21.137: bytes=32 time=242ms TTL=51
Reply from 41.203.21.137: bytes=32 time=204ms TTL=51
Reply from 41.203.21.137: bytes=32 time=110ms TTL=51
Reply from 41.203.21.137: bytes=32 time=239ms TTL=51
Reply from 41.203.21.137: bytes=32 time=236ms TTL=51
Reply from 41.203.21.137: bytes=32 time=151ms TTL=51
Reply from 41.203.21.137: bytes=32 time=180ms TTL=51
Reply from 41.203.21.137: bytes=32 time=245ms TTL=51
Reply from 41.203.21.137: bytes=32 time=218ms TTL=51
Reply from 41.203.21.137: bytes=32 time=193ms TTL=51
Reply from 41.203.21.137: bytes=32 time=154ms TTL=51
Reply from 41.203.21.137: bytes=32 time=234ms TTL=51
Reply from 41.203.21.137: bytes=32 time=239ms TTL=51
Reply from 41.203.21.137: bytes=32 time=216ms TTL=51
Reply from 41.203.21.137: bytes=32 time=212ms TTL=51
Reply from 41.203.21.137: bytes=32 time=99ms TTL=51
Reply from 41.203.21.137: bytes=32 time=147ms TTL=51
Reply from 41.203.21.137: bytes=32 time=217ms TTL=51
Reply from 41.203.21.137: bytes=32 time=201ms TTL=51
Reply from 41.203.21.137: bytes=32 time=52ms TTL=51
Reply from 41.203.21.137: bytes=32 time=84ms TTL=51
Reply from 41.203.21.137: bytes=32 time=179ms TTL=51
Reply from 41.203.21.137: bytes=32 time=206ms TTL=51
Reply from 41.203.21.137: bytes=32 time=51ms TTL=51
Reply from 41.203.21.137: bytes=32 time=117ms TTL=51
Reply from 41.203.21.137: bytes=32 time=165ms TTL=51
Reply from 41.203.21.137: bytes=32 time=160ms TTL=51
Reply from 41.203.21.137: bytes=32 time=154ms TTL=51
Reply from 41.203.21.137: bytes=32 time=171ms TTL=51

Ping statistics for 41.203.21.137:
    Packets: Sent = 84, Received = 84, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 51ms, Maximum = 255ms, Average = 170ms


Pinging google.co.za [74.125.233.88] with 32 bytes of data:
Request timed out.
Reply from 74.125.233.88: bytes=32 time=44ms TTL=53
Reply from 74.125.233.88: bytes=32 time=92ms TTL=53
Reply from 74.125.233.88: bytes=32 time=119ms TTL=53
Reply from 74.125.233.88: bytes=32 time=152ms TTL=53
Reply from 74.125.233.88: bytes=32 time=141ms TTL=53
Reply from 74.125.233.88: bytes=32 time=114ms TTL=53
Reply from 74.125.233.88: bytes=32 time=137ms TTL=53
Reply from 74.125.233.88: bytes=32 time=149ms TTL=53
Reply from 74.125.233.88: bytes=32 time=165ms TTL=53
Reply from 74.125.233.88: bytes=32 time=159ms TTL=53
Reply from 74.125.233.88: bytes=32 time=89ms TTL=53
Reply from 74.125.233.88: bytes=32 time=84ms TTL=53
Reply from 74.125.233.88: bytes=32 time=134ms TTL=53
Reply from 74.125.233.88: bytes=32 time=158ms TTL=53

Ping statistics for 74.125.233.88:
    Packets: Sent = 15, Received = 14, Lost = 1 (6% loss),
Approximate round trip times in milli-seconds:
    Minimum = 44ms, Maximum = 165ms, Average = 124ms
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X