Afrihost Business Uncapped Feedback - 2

Status
Not open for further replies.
Holy moly... these results look terrible :(
I'd like to get this escalated ASAP - could you PM me your DSL username please?

Anyone else seeing results like this?

PM'd
I hope it's not just me. I don't see how it would be though since the 2nd hop is good

Line ping graph:
pingsgoogle.png
 
Last edited:
Going to do the 1GB in a bit. Here's the 4mbps uncapped now:
cache.google.com-2014-10-28_18-59.PNG

And 1GB:
(spiked when doing speed test upload)
cache.google.com-2014-10-28_19-15.PNG
Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|   105-236-10-1-esr-lo.mtnbusiness.co.za -    0 |  537 |  537 |    6 |   38 | 1676 |   17 |
|                          41.181.221.214 -    2 |  506 |  498 |   35 |   81 | 1444 |   77 |
|   rb-dca-2.za--qux-b.za.mtnbusiness.net -    3 |  486 |  473 |   35 |   90 | 1526 |  144 |
|          rb-cr-1.za--rb-dca-2.mtnns.net -    0 |  537 |  537 |   18 |   56 | 1698 |   63 |
|      jh-cr-2.za--rb-cr-1.za-b.mtnns.net -    3 |  486 |  473 |   42 |   83 | 1350 |   58 |
|     jh-dca-2.za--jh-cr-2.za-a.mtnns.net -    0 |  537 |  537 |   17 |   55 | 1635 |   24 |
|                        cache.google.com -    3 |  477 |  463 |   37 |   82 | 1496 |   51 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Oddly enough there is more packet loss on the 1GB but more stable pings. Also, pings are higher by a bit.

I've found that when uploading, the ping tends to skyrocket. Is it possible for Afrihost to control the upload speed of services so that each service is limited to something like 75% of upload speed to prevent one simply wrecking the entire experience? For example, if uploading dropbox files, it only uploads @ 75% of line speed so that other services remain operational with the remaining 25%.
 
Last edited:
Going to do the 1GB in a bit. Here's the 4mbps uncapped now:
View attachment 162145

And 1GB:
(spiked when doing speed test upload)
View attachment 162153
Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|   105-236-10-1-esr-lo.mtnbusiness.co.za -    0 |  537 |  537 |    6 |   38 | 1676 |   17 |
|                          41.181.221.214 -    2 |  506 |  498 |   35 |   81 | 1444 |   77 |
|   rb-dca-2.za--qux-b.za.mtnbusiness.net -    3 |  486 |  473 |   35 |   90 | 1526 |  144 |
|          rb-cr-1.za--rb-dca-2.mtnns.net -    0 |  537 |  537 |   18 |   56 | 1698 |   63 |
|      jh-cr-2.za--rb-cr-1.za-b.mtnns.net -    3 |  486 |  473 |   42 |   83 | 1350 |   58 |
|     jh-dca-2.za--jh-cr-2.za-a.mtnns.net -    0 |  537 |  537 |   17 |   55 | 1635 |   24 |
|                        cache.google.com -    3 |  477 |  463 |   37 |   82 | 1496 |   51 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Oddly enough there is more packet loss on the 1GB but more stable pings. Also, pings are higher by a bit.

I've found that when uploading, the ping tends to skyrocket. Is it possible for Afrihost to control the upload speed of services so that each service is limited to something like 75% of upload speed to prevent one simply wrecking the entire experience? For example, if uploading dropbox files, it only uploads @ 75% of line speed so that other services remain operational with the remaining 25%.

Sorry to be a pain, could you include this in your PM please? I'd like to have the info all in one place.
Also if possible, could you add some traceroutes into the mix too?
 
And its fallen off a cliff again tonight

3866189250.png

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Segg>tracert www.google.co.za

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

1 1 ms 1 ms <1 ms Router [10.0.0.1]
2 8 ms 7 ms 13 ms 105-236-15-1-esr-lo.mtnbusiness.co.za [105.236.15.1]
3 44 ms 73 ms 49 ms ipc-recieve-jh-2a.za.mtnbusiness.net [41.181.178.17]
4 25 ms 123 ms 43 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
5 50 ms 18 ms 46 ms jh-dca-2.za--qux-q.za.mtnbusiness.net [196.31.180.4]
6 218 ms 212 ms 201 ms ls-pr-2.uk--ls-cr-2.uk-a.mtn.net [209.212.111.187]
7 195 ms 212 ms 189 ms google-peering-ls-pr-2.uk.mtnns.net [209.212.99.13]
8 250 ms 214 ms 249 ms 209.85.255.76
9 299 ms 272 ms 206 ms 66.249.95.9
10 437 ms 250 ms 214 ms 72.14.237.239
11 209 ms 196 ms 197 ms jnb01s07-in-f3.1e100.net [74.125.233.3]

Trace complete.


C:\Users\Segg>tracert www.mybroadband.co.za

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

1 1 ms 1 ms <1 ms Router [10.0.0.1]
2 7 ms 8 ms 7 ms 105-236-15-1-esr-lo.mtnbusiness.co.za [105.236.15.1]
3 32 ms 29 ms 43 ms 41.181.221.250
4 9 ms 37 ms 10 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
5 10 ms 10 ms 10 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
6 32 ms 31 ms 54 ms 41.181.180.10
7 106 ms 38 ms 58 ms 196.44.0.72
8 * * * Request timed out.
9 52 ms 63 ms 36 ms CORE.GP-CN-HET-MEE-1.TO.GP-MR-VOD-MEE-1.DFA.P2P.10G.za.africainx.net [41.84.12.151]
10 36 ms 36 ms 74 ms 41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1.africainx.net [41.66.132.246]
11 44 ms 71 ms 48 ms core-access-switch1.jnb1.host-h.net [197.189.193.1]
12 46 ms 62 ms 36 ms row-access-switch1-row3-4.jnb1.host-h.net [197.189.193.36]
13 115 ms 103 ms 128 ms 197.242.89.170

Trace complete.
 
Last edited:
Woo hoo, seems like we flying tonight... - into the ground

this is utter disgraceful for a 8mb business uncapped account.
3866268161.png

@Afriman - what has been the issue with Afrihost this week, last night I could barely get a skype call going.:(

P2P - bursting up to 266KBs and hovering around 60KBs | NNTP over SSL @ an awesome 32KBS
 
Last edited:
Sorry to be a pain, could you include this in your PM please? I'd like to have the info all in one place.
Also if possible, could you add some traceroutes into the mix too?

I don't think you can include images in a PM... Or I don't know how to at least. Tracerts are the same as MTRs... They're just more accurate since they don't rely on every hop being good to find the culprit. But anyways:
Code:
Tracing route to google.co.za [66.8.14.26]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2    16 ms    14 ms    17 ms  105-236-10-1-esr-lo.mtnbusiness.co.za [105.236.10.1]
  3    24 ms    31 ms    31 ms  41.181.221.214
  4    20 ms    28 ms    24 ms  rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.118]
  5    95 ms    83 ms    77 ms  rb-dca-2.za--rb-cr-1.mtnns.net [196.44.31.122]
  6    65 ms    72 ms     *     jh-cr-2.za--rb-cr-1.za-b.mtnns.net [196.44.31.171]
  7    76 ms    61 ms    56 ms  jh-dca-2.za--jh-cr-2.za-a.mtnns.net [196.44.0.225]
  8    64 ms    90 ms    81 ms  cache.google.com [66.8.14.26]

Trace complete.
 
And its fallen off a cliff again tonight

View attachment 162199

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Segg>tracert www.google.co.za

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

1 1 ms 1 ms <1 ms Router [10.0.0.1]
2 8 ms 7 ms 13 ms 105-236-15-1-esr-lo.mtnbusiness.co.za [105.236.15.1]
3 44 ms 73 ms 49 ms ipc-recieve-jh-2a.za.mtnbusiness.net [41.181.178.17]
4 25 ms 123 ms 43 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
5 50 ms 18 ms 46 ms jh-dca-2.za--qux-q.za.mtnbusiness.net [196.31.180.4]
6 218 ms 212 ms 201 ms ls-pr-2.uk--ls-cr-2.uk-a.mtn.net [209.212.111.187]
7 195 ms 212 ms 189 ms google-peering-ls-pr-2.uk.mtnns.net [209.212.99.13]
8 250 ms 214 ms 249 ms 209.85.255.76
9 299 ms 272 ms 206 ms 66.249.95.9
10 437 ms 250 ms 214 ms 72.14.237.239
11 209 ms 196 ms 197 ms jnb01s07-in-f3.1e100.net [74.125.233.3]

Trace complete.


C:\Users\Segg>tracert www.mybroadband.co.za

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

1 1 ms 1 ms <1 ms Router [10.0.0.1]
2 7 ms 8 ms 7 ms 105-236-15-1-esr-lo.mtnbusiness.co.za [105.236.15.1]
3 32 ms 29 ms 43 ms 41.181.221.250
4 9 ms 37 ms 10 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
5 10 ms 10 ms 10 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
6 32 ms 31 ms 54 ms 41.181.180.10
7 106 ms 38 ms 58 ms 196.44.0.72
8 * * * Request timed out.
9 52 ms 63 ms 36 ms CORE.GP-CN-HET-MEE-1.TO.GP-MR-VOD-MEE-1.DFA.P2P.10G.za.africainx.net [41.84.12.151]
10 36 ms 36 ms 74 ms 41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1.africainx.net [41.66.132.246]
11 44 ms 71 ms 48 ms core-access-switch1.jnb1.host-h.net [197.189.193.1]
12 46 ms 62 ms 36 ms row-access-switch1-row3-4.jnb1.host-h.net [197.189.193.36]
13 115 ms 103 ms 128 ms 197.242.89.170

Trace complete.

This looks a trace from the North, so we shouldn't be seeing poor results like this. Demand was at it's peak around that time of the day, so we may have had some poor performance if we didn't manage traffic effectively enough on the overall network during that period. I'll report this to the network team so they can factor into their tweaking of the network since the upgrade.
 
Woo hoo, seems like we flying tonight... - into the ground

this is utter disgraceful for a 8mb business uncapped account.
View attachment 162215

@Afriman - what has been the issue with Afrihost this week, last night I could barely get a skype call going.:(

P2P - bursting up to 266KBs and hovering around 60KBs | NNTP over SSL @ an awesome 32KBS

From what I can see, overall performance in the North is much better than it has been, but we're still checking the limits of the additional capacity to see at which point the network takes too much strain. From previous IPC upgrades, this has taken a week or so for our network team to get 100% right, because it depends on dynamic user behaviour and tweaking limits for best performance.
 
I don't think you can include images in a PM... Or I don't know how to at least. Tracerts are the same as MTRs... They're just more accurate since they don't rely on every hop being good to find the culprit. But anyways:
Code:
Tracing route to google.co.za [66.8.14.26]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2    16 ms    14 ms    17 ms  105-236-10-1-esr-lo.mtnbusiness.co.za [105.236.10.1]
  3    24 ms    31 ms    31 ms  41.181.221.214
  4    20 ms    28 ms    24 ms  rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.118]
  5    95 ms    83 ms    77 ms  rb-dca-2.za--rb-cr-1.mtnns.net [196.44.31.122]
  6    65 ms    72 ms     *     jh-cr-2.za--rb-cr-1.za-b.mtnns.net [196.44.31.171]
  7    76 ms    61 ms    56 ms  jh-dca-2.za--jh-cr-2.za-a.mtnns.net [196.44.0.225]
  8    64 ms    90 ms    81 ms  cache.google.com [66.8.14.26]

Trace complete.

Maybe use something like http://imgur.com :)
 
http://www.speedtest.net/result/3866272210.png
10mbps "Business"

http://www.speedtest.net/result/3866312131.png
Plugg capped.

Ping is great, indicating not enough capacity...

I think it's problematic to use just an international speedtest as an indicator. It's an effectively longer routing chain, and makes it more difficult to determine if there are local factors. It's hard for us to determine if this is an local or international issue and whether it relates to capacity or peering. The less variables and more data we can look at, the more accurately we can determine what the possible cause could be and go straight to looking at a solution.
 
Earlier result shows decent usable speed:
IMG_20141029_085320.jpg

But it has all gone to hell yet again......
IMG_20141029_085337.jpg


So when are we actually going to get the service we are paying a premium for?
This is now getting close to the third month of this crap and frankly I could care less who does what, I just want the "guaranteed full line speed at all times" 6Mb I am paying for.
 
Last edited:
Earlier result shows decent usable speed:
View attachment 162301

But it has all gone to hell yet again......
View attachment 162303


So when are we actually going to get the service we are paying a premium for?
This is now getting close to the third month of this crap and frankly I could care less who does what, I just want the "guaranteed full line speed at all times" 6Mb I am paying for.

This is very concerning, the north was supposed to have been upgraded and the service is still poor. I am in the south and we always seem to have crap service, and it looks like the capacity increase has not helped or was never the real issue in the first place. Wonder what the new excuse will be?
 
Earlier result shows decent usable speed:

But it has all gone to hell yet again......

So when are we actually going to get the service we are paying a premium for?
This is now getting close to the third month of this crap and frankly I could care less who does what, I just want the "guaranteed full line speed at all times" 6Mb I am paying for.

I am having a very similar experience in the North. The line goes up and down more than a hooker's panty! Really starting to irritate me.
 
This is a screenshot I posted a few pages back just to show how erratic it really is:

View attachment 162311


IPC shmipeecee.........

Since the IPC was upgraded there are only a few tests to go by. I believe you when you say you're experience is erratic but we need to demonstrate that a lot more definitively if we're going to escalate this. We'll really need to run more thorough tests with our support team to get more data here.
 
This is very concerning, the north was supposed to have been upgraded and the service is still poor. I am in the south and we always seem to have crap service, and it looks like the capacity increase has not helped or was never the real issue in the first place. Wonder what the new excuse will be?

From the feedback from clients via support and on general social media and the decrease in support requests, we've definitely seen an improvement in overall experience in the North for the majority of clients. I don't know if one can generalise and say the entire North region is experiencing poor service based on a few reports here. We need to troubleshoot each specific query to determine what the unique (or common) factors are.
 
what happened to the old days when it just use to work
now it is all about tweaking the most out of the least bandwidth
keep up the good tweaking work
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X