Afrihost Capped DSL Feedback

Your BRAS ping isn't great. We like to see latency around 10ms or less ideally. It may seem like a small difference but can compound to add latency onto your end destination.

We'll definitely try to recreate this on our end as well.
BRAS has never got below 19ms since ASSIA was rolled out. Your critical care team couldn't resolve with Telkom. So it's my 'new' normal. YET I'm still a loyal customer. Why? Because I seek to get to the root-cause to enable improvement for everyone... and often you guys step up where telephone support does not.

In this particular case the issue appears hop 4 is anomalous. I'd like to get the AH team's thoughts on this suggestion.

Thx, SD
 
BRAS has never got below 19ms since ASSIA was rolled out. Your critical care team couldn't resolve with Telkom. So it's my 'new' normal. YET I'm still a loyal customer. Why? Because I seek to get to the root-cause to enable improvement for everyone... and often you guys step up where telephone support does not.

In this particular case the issue appears hop 4 is anomalous. I'd like to get the AH team's thoughts on this suggestion.

Thx, SD

We'll push this through to our network team and see what they can make of it :)
 
We'll push this through to our network team and see what they can make of it :)
Appreciate it. Please keep us in the loop.
Also don't lose sight of the reported issues with DSTV, NNTP, slow streaming, etc, etc. Something isn't right and it's affecting multiple regions.

Food for thought..
Occam's razor paraphrased... When all things are accounted for, the simplest answer, no matter how improbable, might be true. I.E. we started seeing significant issues after shaped capped was announced.
 
I wonder if there isn't an issue with the routing. I think it may be best to ask our Critical Care Team to get hold of you. They will definitely be able to figure out what's going on.

Hey buddy. Haven't had anyone reach out to me yet. Let me know if i can assist further. If they have it under control that's great. Just let us have updates.
 
BRAS has never got below 19ms since ASSIA was rolled out. Your critical care team couldn't resolve with Telkom. So it's my 'new' normal. YET I'm still a loyal customer. Why? Because I seek to get to the root-cause to enable improvement for everyone... and often you guys step up where telephone support does not.

In this particular case the issue appears hop 4 is anomalous. I'd like to get the AH team's thoughts on this suggestion.

Thx, SD

This is the same for me. BRAS is averaging +-16ms and there is a hop in CT that is always an issue in the evenings. If I trace to the previous hop (cpt-tx2.ip.adsl.co.za) it's clean. The next hop is another story.

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 1 | 2497 | 2495 | 0 | 0 | 2 | 0 |
| No response from host - 100 | 501 | 0 | 0 | 0 | 0 | 0 |
| cpt-tx2.ip.adsl.co.za - 3 | 2293 | 2240 | 40 | 43 | 67 | 41 |
| 169-1-21-54.ip.afrihost.co.za - 1 | 2438 | 2421 | 33 | 118 | 263 | 123 |
| cpt-net1.ip.adsl.co.za - 2 | 2321 | 2275 | 86 | 161 | 237 | 166 |
| optinet.ixp.capetown - 0 | 2504 | 2504 | 34 | 37 | 64 | 40 |

As an interesting aside. If I speedtest to Telkom SAIX in CT, I get very bad results. If I choose another server, i.e. MWEB, Cell-C etc my throughput is perfect. I am talking 10mb down as opposed to 30mb! Maybe look at this?
 
This is the same for me. BRAS is averaging +-16ms and there is a hop in CT that is always an issue in the evenings. If I trace to the previous hop (cpt-tx2.ip.adsl.co.za) it's clean. The next hop is another story.

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 1 | 2497 | 2495 | 0 | 0 | 2 | 0 |
| No response from host - 100 | 501 | 0 | 0 | 0 | 0 | 0 |
| cpt-tx2.ip.adsl.co.za - 3 | 2293 | 2240 | 40 | 43 | 67 | 41 |
| 169-1-21-54.ip.afrihost.co.za - 1 | 2438 | 2421 | 33 | 118 | 263 | 123 |
| cpt-net1.ip.adsl.co.za - 2 | 2321 | 2275 | 86 | 161 | 237 | 166 |
| optinet.ixp.capetown - 0 | 2504 | 2504 | 34 | 37 | 64 | 40 |

As an interesting aside. If I speedtest to Telkom SAIX in CT, I get very bad results. If I choose another server, i.e. MWEB, Cell-C etc my throughput is perfect. I am talking 10mb down as opposed to 30mb! Maybe look at this?
Yep something is awfully weird. I'll check out the speedtests tonight and let you know. To date I've always received full speed to saix using beta.speedtest.net. If that's the case then I'll have to figure out the server IP and we can trace that.
 
This is the same for me. BRAS is averaging +-16ms and there is a hop in CT that is always an issue in the evenings. If I trace to the previous hop (cpt-tx2.ip.adsl.co.za) it's clean. The next hop is another story.

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 1 | 2497 | 2495 | 0 | 0 | 2 | 0 |
| No response from host - 100 | 501 | 0 | 0 | 0 | 0 | 0 |
| cpt-tx2.ip.adsl.co.za - 3 | 2293 | 2240 | 40 | 43 | 67 | 41 |
| 169-1-21-54.ip.afrihost.co.za - 1 | 2438 | 2421 | 33 | 118 | 263 | 123 |
| cpt-net1.ip.adsl.co.za - 2 | 2321 | 2275 | 86 | 161 | 237 | 166 |
| optinet.ixp.capetown - 0 | 2504 | 2504 | 34 | 37 | 64 | 40 |

As an interesting aside. If I speedtest to Telkom SAIX in CT, I get very bad results. If I choose another server, i.e. MWEB, Cell-C etc my throughput is perfect. I am talking 10mb down as opposed to 30mb! Maybe look at this?

Thanks for testing. :) We're passing all of your reports onto our NOC Team. Could you please PM me your username?
 
Yep something is awfully weird. I'll check out the speedtests tonight and let you know. To date I've always received full speed to saix using beta.speedtest.net. If that's the case then I'll have to figure out the server IP and we can trace that.

Good idea. :) We'll be here tonight.
 
Hi, I've just had an online chat with Afrihost support and am at a loss. I recently downgraded my capped account to 1GB free (because my capped account is now a shaped capped account..). Since I did this on the 10th, I've noticed my cap disappearing - it seems after hours (12-8) uncapped no longer applied to me I used 21GB this morning BEFORE 8AM. The support guy told me that because I'm now on 1GB free account this is normal... Really? I paid for a 100GB capped data package on the 1st of March, I expect the service I paid for the exist until the end of the month, at which point I will move ISPs. Is this even legal ??
 
Hi, I've just had an online chat with Afrihost support and am at a loss. I recently downgraded my capped account to 1GB free (because my capped account is now a shaped capped account..). Since I did this on the 10th, I've noticed my cap disappearing - it seems after hours (12-8) uncapped no longer applied to me I used 21GB this morning BEFORE 8AM. The support guy told me that because I'm now on 1GB free account this is normal... Really? I paid for a 100GB capped data package on the 1st of March, I expect the service I paid for the exist until the end of the month, at which point I will move ISPs. Is this even legal ??

Heya foxmatt. Downgrades should only take effect at the end of the month. Your 100GB data link should definitely still be active until the end of March. I'm interested to see what could have happened with your After Hours data allocation. Please feel free to drop me a PM with your account info and I'll investigate.
 
Hmmm. That's odd.
Did you try the "Test" option from Config --> Servers. Try a couple of times. It sometimes say's it can't find the server.

My config is as follows:
Code:
Host: news.afrihost.com
Port: 119
Username: 
Password: 
Connections: 10
Retention time: 0 days
Timeout: 120 seconds
SSL ~ unchecked 
Backup server ~ Unchecked 
Optional ~ Unchecked

It's the only Enabled service.

Anyone found some solutions. I get a timed out error when I test server with the same input CPT.
Sunnyusenet server working.
 
Anyone found some solutions. I get a timed out error when I test server with the same input CPT.
Sunnyusenet server working.

Post the route to news.afrihost.com. I'll compare to mine this evening. That's the only logical reason. If not then something is wrong with authentication.
 
Facebook dead in the water, switching to my IS account and it loads fine. :confused:

Tracing route to facebook.com [185.60.219.35]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 19 ms 18 ms 19 ms dbn-up2.ip.adsl.co.za [169.1.5.173]
4 24 ms 24 ms 24 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
5 28 ms 27 ms 28 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
6 39 ms 38 ms 49 ms 169-1-21-32.ip.afrihost.co.za [169.1.21.32]
7 * 39 ms 39 ms 196-60-9-16.ixp.joburg [196.60.9.16]
8 38 ms 41 ms 38 ms po102.psw03.jnb1.tfbnw.net [157.240.41.251]
9 38 ms 42 ms 43 ms 173.252.67.115
10 * 33 ms * 185.60.219.35
11 34 ms 33 ms 33 ms 185.60.219.35

Trace complete.
 
Post the route to news.afrihost.com. I'll compare to mine this evening. That's the only logical reason. If not then something is wrong with authentication.

Okay here's the tracert via my server ...
As you can see it's going to the Netherlands server.
Forgot the packet loss for now. That's another issue we haven't quite had answers to yet.
Code:
                                       Packets               Pings
 Host                                Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. router.asus.com                   0.0%    41    0.3   0.3   0.2   0.6   0.0
 2. ???
 3. cpt-up1.ip.adsl.co.za             4.9%    41   20.8  23.8  20.1  83.3  10.4
 4. cpt-in1.ip.adsl.co.za             0.0%    41   22.1  24.5  20.2  76.5  11.2
 5. cpt-net1.ip.adsl.co.za            0.0%    41   27.0  55.1  19.6 178.0  40.7
 6. 41.164.52.40                      2.4%    41   20.3  26.6  19.7  56.0   9.5
 7. ix-ae-7-0.tcore2.KLT-Cape-Town.a  0.0%    41   20.8  30.6  20.1 129.6  23.7
 8. if-ae-2-2.tcore1.KLT-Cape-Town.a  0.0%    41  210.2 228.9 172.5 285.6  25.6
 9. if-ae-5-2.tcore2.PV9-Lisbon.as64  4.9%    41  174.6 179.4 173.9 227.5  13.2
10. if-ae-2-2.tcore1.PV9-Lisbon.as64  2.4%    41  175.7 179.4 174.4 227.3  12.3
11. if-ae-1-3.tcore1.SV8-Highbridge.  0.0%    41  180.9 189.0 180.9 219.9  10.9
12. if-ae-19-2.tcore2.L78-London.as6 12.5%    41  226.8 228.6 175.0 264.6  20.8
13. if-ae-8-2.tcore2.AV2-Amsterdam.a  0.0%    41  181.2 186.0 180.8 236.1  11.3
14. if-ae-2-2.tcore1.AV2-Amsterdam.a  0.0%    41  261.4 191.7 174.1 261.4  19.9
15. 195.219.194.118                   0.0%    40  175.5 178.1 174.6 203.0   7.0
16. 1-1.r2.am.hwng.net                0.0%    40  241.6 239.3 180.5 303.7  25.6
17. 81.171.92.236                     0.0%    40  175.7 178.7 174.8 213.8   7.7

Now look at Windows ...
Code:
Target Name: news.afrihost.com
         IP: 169.1.1.36
  Date/Time: 14 Mar 2017 4:57:52 PM - 14 Mar 2017 5:07:52 PM

Hop  Sent  PL%    Min     Max     Avg  Host Name / [IP]
  1    92    0   0.71    1.53    1.01  router.asus.com [192.168.1.1]
  2    92  100      0       0       0   [-]
  3    92    5  20.39   70.29   22.87  cpt-up1.ip.adsl.co.za [169.1.5.105]
  4    92    0  20.00   65.41   23.33  cpt-up2.ip.adsl.co.za [169.1.5.106]
  5    92    0  19.96  191.16   49.00  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6    92    7  20.21   52.33   22.07  41.164.52.40 [41.164.52.40]
  7    92    0  40.00   62.59   41.86  172.18.1.164 [172.18.1.164]
  8    92    3  41.41  244.91  102.92  41.169.57.219 [41.169.57.219]
  9    92    0  39.17   78.21   42.02  169-1-5-195.ip.afrihost.co.za [169.1.5.195]
 10    92   33  40.56  210.69   60.17  jhb-ex0b.ip.adsl.co.za [169.1.5.63]
 11    92    0  39.84  220.08   54.86  news.afrihost.com [169.1.1.36]

That's going to the local mirror.

Why so? Dunno. Bizzarre.
I flushed my Windows DNS tables and...
Code:
Target Name: news.afrihost.com
         IP: 81.171.92.222
  Date/Time: 14 Mar 2017 5:06:48 PM - 14 Mar 2017 5:16:48 PM

Hop  Sent  PL%     Min     Max     Avg  Host Name / [IP]
  1   172    0    0.70    2.15    0.97  router.asus.com [192.168.1.1]
  2   172  100       0       0       0   [-]
  3   172   11   20.53   65.64   23.82  cpt-up1.ip.adsl.co.za [169.1.5.105]
  4   172    3   20.00   66.48   23.32  169-1-21-66.ip.afrihost.co.za [169.1.21.66]
  5   172    1   20.36  169.93   50.91  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6   172    5   20.36   54.05   22.89  41.164.52.40 [41.164.52.40]
  7   172    0   20.88   72.69   23.71  ix-ae-7-0.tcore1.KLT-Cape-Town.as6453.net [41.206.164.53]
  8   172    0  168.57  211.83  170.93  if-ae-5-2.tcore2.PV9-Lisbon.as6453.net [80.231.159.89]
  9   172    0  168.59  216.32  171.31  if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
 10   172    0  175.22  339.83  192.28  if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
 11   172   84  168.00  267.90  190.69  if-ae-19-2.tcore2.L78-London.as6453.net [80.231.138.22]
 12   172    1  174.75  214.52  177.67  if-ae-8-2.tcore2.AV2-Amsterdam.as6453.net [80.231.131.6]
 13   172    1  167.83  319.29  185.07  if-ae-2-2.tcore1.AV2-Amsterdam.as6453.net [195.219.194.5]
 14   172    3  167.78  222.57  172.04  195.219.194.122 [195.219.194.122]
 15   172    0  169.01  332.69  216.14  1-1.r2.am.hwng.net [69.16.191.101]
 16   172    0  173.00  219.00  176.25  news.afrihost.com [81.171.92.222]
Lo and behold .... it now hits the Nertherlands server(s).

So there are different servers locally and international and I'm guessing the local one ain't working.
If you're hitting that you're likely buggered.

If I'm right about this and the other issues then AH need to start thinking about an engagement with SD. :p;)

Additional note: My DNS tables on Windows were flushed 48hrs ago so the local server hit happened with pretty fresh DNS data. Why the server and Windows have different resolutions... not 100% sure yet.
 
Last edited:
Yep something is awfully weird. I'll check out the speedtests tonight and let you know. To date I've always received full speed to saix using beta.speedtest.net. If that's the case then I'll have to figure out the server IP and we can trace that.

Okay here are the latest speedtests. SAIX, Vodacom, MWeb, and Vox (auto selected optimal).
A bit erratic today. Typical is >19mbps. Took very long to get to full speed. Re-tests often fluctuate down to 18mbps.
These are the best result of three.

- SAIX 18.15mbps - okay. typically >19mbps
http://beta.speedtest.net/result/6129587540.png

- Vodacom 19.53 - certainly working as expected. quick to get up to full speed.
http://beta.speedtest.net/result/6129611911.png

- MWEb 18.22mbps
http://beta.speedtest.net/result/6129626770.png

- Vox 19.39mbps - expected
http://beta.speedtest.net/result/6129579317.png

So the other part of the question. Routing to SAIX.
The SAIX server beta.speedtest.net connected to was 196.25.37.14 capetown.spdtst.saix.net.
Here's the tracert.

Code:
Tracing route to wblv-ip-dlr-15-3.saix.net [196.25.37.14]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  router.asus.com [192.168.1.1]
  2     *        *        *     Request timed out.
  3    22 ms    21 ms    20 ms  cpt-up1.ip.adsl.co.za [169.1.5.105]
  4    23 ms    22 ms    21 ms  cpt-up2.ip.adsl.co.za [169.1.5.106]
  5    21 ms    21 ms    20 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6    20 ms    20 ms    20 ms  41.164.52.40
  7    60 ms    52 ms    50 ms  wblv-ip-se-2-wan.telkom-ipnet.co.za [196.25.3.101]
  8    23 ms    21 ms    21 ms  196.43.25.205
  9    28 ms    25 ms    23 ms  196.43.39.58
 10    35 ms    35 ms    39 ms  wblv-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za [196.25.37.2]
 11    23 ms    22 ms    22 ms  wblv-ip-dlr-15-3.saix.net [196.25.37.14]

EISH!!!!!!!!!!!!
I just redid the SAIX test and got 8mbps. To the server above.
http://beta.speedtest.net/result/6129689635.png

Dunno whether it used a different server on the original test.

So decided to redo the other server tests and they are ok.
So something's not right with the saix server above.
Packet loss at Hop 3 again and latency issues down the line. IPC issues?
Seeing the same to catchup.dstv.com, which sucks.

I'll post the same server test from the SAIX test account a bit later.

Code:
Target Name: 196.25.37.14
         IP: 196.25.37.14
  Date/Time: 14 Mar 2017 6:02:54 PM - 14 Mar 2017 6:12:54 PM

Hop  Sent  PL%    Min     Max     Avg  Host Name / [IP]
  1    18    0   0.69    1.37    0.95  router.asus.com [192.168.1.1]
  2    17  100      0       0       0   [-]
  3    18   33  20.21   21.93   21.15  cpt-up1.ip.adsl.co.za [169.1.5.105]
  4    18    0  20.73   23.13   21.60  cpt-up2.ip.adsl.co.za [169.1.5.106]
  5    18    0  51.45  138.59   92.58  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6    18    0  20.17   44.10   22.24  41.164.52.40 [41.164.52.40]
  7    18    0  70.67  144.91  109.44  wblv-ip-se-2-wan.telkom-ipnet.co.za [196.25.3.101]
  8    18    0  21.20   38.87   22.93  196.43.25.205 [196.43.25.205]
  9    18    0  21.00   22.30   21.61  196.43.39.58 [196.43.39.58]
 10    18    0  58.63  141.83   94.89  wblv-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za [196.25.37.2]
 11    18    0  21.33   23.06   21.93  196.25.37.14 [196.25.37.14]
 
Last edited:
.
-- DELETED ---

EISH!!!!!!!!!!!!
I just redid the SAIX test and got 8mbps. To the server above.
Dunno whether it used a different server on the original test.

So decided to redo the other server tests and they are ok.
So something's not right with the saix server above.
Packet loss at Hop 3 again and latency issues down the line. IPC issues?
Seeing the same to catchup.dstv.com, which sucks.

I'll post the same server test from the SAIX test account a bit later.

Code:
Target Name: 196.25.37.14
         IP: 196.25.37.14
  Date/Time: 14 Mar 2017 6:02:54 PM - 14 Mar 2017 6:12:54 PM

Hop  Sent  PL%    Min     Max     Avg  Host Name / [IP]
  1    18    0   0.69    1.37    0.95  router.asus.com [192.168.1.1]
  2    17  100      0       0       0   [-]
  3    18   33  20.21   21.93   21.15  cpt-up1.ip.adsl.co.za [169.1.5.105]
  4    18    0  20.73   23.13   21.60  cpt-up2.ip.adsl.co.za [169.1.5.106]
  5    18    0  51.45  138.59   92.58  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6    18    0  20.17   44.10   22.24  41.164.52.40 [41.164.52.40]
  7    18    0  70.67  144.91  109.44  wblv-ip-se-2-wan.telkom-ipnet.co.za [196.25.3.101]
  8    18    0  21.20   38.87   22.93  196.43.25.205 [196.43.25.205]
  9    18    0  21.00   22.30   21.61  196.43.39.58 [196.43.39.58]
 10    18    0  58.63  141.83   94.89  wblv-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za [196.25.37.2]
 11    18    0  21.33   23.06   21.93  196.25.37.14 [196.25.37.14]

Okay I've swapped to the SAIX account and checked routing and latencies.
Code:
Target Name: 196.25.37.14
         IP: 196.25.37.14
  Date/Time: 14 Mar 2017 6:08:44 PM - 14 Mar 2017 6:18:44 PM

Hop  Sent  PL%    Min     Max    Avg  Host Name / [IP]
  1    37    0   0.67    1.65   0.96  router.asus.com [192.168.1.1]
  2    37  100      0       0      0   [-]
  3    37    0  19.49  198.34  43.04  196.43.31.249 [196.43.31.249]
  4    37    0  19.82   21.78  20.64  196.43.31.250 [196.43.31.250]
  5    37    0  20.04   22.32  20.71  196.43.31.253 [196.43.31.253]
  6    37    0  20.00   22.01  20.76  196.43.39.58 [196.43.39.58]
  7    37    0  20.31   32.84  21.91  wblv-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za [196.25.37.2]
  8    37    0  20.59   24.59  21.63  196.25.37.14 [196.25.37.14]

Speedtest redone...
Confirmed that the same server was being used.
Outcome - spectacular. Full speed... almost. 19.5mbps
http://beta.speedtest.net/result/6129730559.png

So there is something wrong with the AH capped account.
Same symptoms as my DSTV catchup issues. AH struggling and SAIX account not.

@AfriPeeps - over to you guys. There is a problem on the AH side. [Yes] [No] [Maybe]
 
Okay here are the latest speedtests. SAIX, Vodacom, MWeb, and Vox (auto selected optimal).
A bit erratic today. Typical is >19mbps. Took very long to get to full speed. Re-tests often fluctuate down to 18mbps.
These are the best result of three.

- SAIX 18.15mbps - okay. typically >19mbps
http://beta.speedtest.net/result/6129587540.png

- Vodacom 19.53 - certainly working as expected. quick to get up to full speed.
http://beta.speedtest.net/result/6129611911.png

- MWEb 18.22mbps
http://beta.speedtest.net/result/6129626770.png

- Vox 19.39mbps - expected but why erratic?
http://beta.speedtest.net/result/6129579317.png

So the other part of the question. Routing to SAIX.
The SAIX server beta.speedtest.net connected to was 196.25.37.14 capetown.spdtst.saix.net.
Here's the tracert.

Code:
Tracing route to wblv-ip-dlr-15-3.saix.net [196.25.37.14]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  router.asus.com [192.168.1.1]
  2     *        *        *     Request timed out.
  3    22 ms    21 ms    20 ms  cpt-up1.ip.adsl.co.za [169.1.5.105]
  4    23 ms    22 ms    21 ms  cpt-up2.ip.adsl.co.za [169.1.5.106]
  5    21 ms    21 ms    20 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6    20 ms    20 ms    20 ms  41.164.52.40
  7    60 ms    52 ms    50 ms  wblv-ip-se-2-wan.telkom-ipnet.co.za [196.25.3.101]
  8    23 ms    21 ms    21 ms  196.43.25.205
  9    28 ms    25 ms    23 ms  196.43.39.58
 10    35 ms    35 ms    39 ms  wblv-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za [196.25.37.2]
 11    23 ms    22 ms    22 ms  wblv-ip-dlr-15-3.saix.net [196.25.37.14]

EISH!!!!!!!!!!!!
I just redid the SAIX test and got 8mbps. To the server above.
Dunno whether it used a different server on the original test.

So decided to redo the other server tests and they are ok.
So something's not right with the saix server above.
Packet loss at Hop 3 again and latency issues down the line. IPC issues?
Seeing the same to catchup.dstv.com, which sucks.

I'll post the same server test from the SAIX test account a bit later.

Code:
Target Name: 196.25.37.14
         IP: 196.25.37.14
  Date/Time: 14 Mar 2017 6:02:54 PM - 14 Mar 2017 6:12:54 PM

Hop  Sent  PL%    Min     Max     Avg  Host Name / [IP]
  1    18    0   0.69    1.37    0.95  router.asus.com [192.168.1.1]
  2    17  100      0       0       0   [-]
  3    18   33  20.21   21.93   21.15  cpt-up1.ip.adsl.co.za [169.1.5.105]
  4    18    0  20.73   23.13   21.60  cpt-up2.ip.adsl.co.za [169.1.5.106]
  5    18    0  51.45  138.59   92.58  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6    18    0  20.17   44.10   22.24  41.164.52.40 [41.164.52.40]
  7    18    0  70.67  144.91  109.44  wblv-ip-se-2-wan.telkom-ipnet.co.za [196.25.3.101]
  8    18    0  21.20   38.87   22.93  196.43.25.205 [196.43.25.205]
  9    18    0  21.00   22.30   21.61  196.43.39.58 [196.43.39.58]
 10    18    0  58.63  141.83   94.89  wblv-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za [196.25.37.2]
 11    18    0  21.33   23.06   21.93  196.25.37.14 [196.25.37.14]

Okay I've swapped to the SAIX account and checked routing and latencies.
Code:
Target Name: 196.25.37.14
         IP: 196.25.37.14
  Date/Time: 14 Mar 2017 6:08:44 PM - 14 Mar 2017 6:18:44 PM

Hop  Sent  PL%    Min     Max    Avg  Host Name / [IP]
  1    37    0   0.67    1.65   0.96  router.asus.com [192.168.1.1]
  2    37  100      0       0      0   [-]
  3    37    0  19.49  198.34  43.04  196.43.31.249 [196.43.31.249]
  4    37    0  19.82   21.78  20.64  196.43.31.250 [196.43.31.250]
  5    37    0  20.04   22.32  20.71  196.43.31.253 [196.43.31.253]
  6    37    0  20.00   22.01  20.76  196.43.39.58 [196.43.39.58]
  7    37    0  20.31   32.84  21.91  wblv-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za [196.25.37.2]
  8    37    0  20.59   24.59  21.63  196.25.37.14 [196.25.37.14]

Speedtest redone...
Confirmed that the same server was being used.
Outcome - spectacular. Full speed... almost. 19.5mbps
http://beta.speedtest.net/result/6129730559.png

So there is something wrong with the AH capped account.
Same symptoms as my DSTV catchup issues. AH struggling and SAIX account not.

@AfriPeeps - over to you guys. There is a problem on the AH side. [Yes] [No] [Maybe]

We'll figure out what's going on with your connection. I'm going to make sure that our Critical Care Team contacts you and works with you to figure out what's going on.
 
We'll figure out what's going on with your connection. I'm going to make sure that our Critical Care Team contacts you and works with you to figure out what's going on.

Don't forget that it's not just my connection. There are a lot of other folks reporting exactly the same. I've been diagnosing in the best interest of all.
 
Top
Sign up to the MyBroadband newsletter
X