Afrihost Capped DSL Feedback

[CloudStrif3]

Were you able to run a speedtest at all?

Speed test:
Download Speed: 2836 kbps (354.5 KB/sec transfer rate)
Upload Speed: 842 kbps (105.3 KB/sec transfer rate)
Latency: 26 ms
Jitter: 3 ms

I even got a call from Telkom to say the problem was fixed...however...I guessed wrong.
At the same time, over the weekend my account was even upgraded to unshaped! So i'm paying more...for? you guessed it...nothing. Defs not a 20mbps line...

 

[CloudStrif3]

Switched ISP and a huge difference. I've now paused this account, will test periodically but going to spend my money where it actually gets you data. Benefit of the doubt for you chaps to fix but this has been a issue for the month and nothing has been done.

Please share your wisdom! I'd like to do the same.

 

[Kosmik]

Please share your wisdom! I'd like to do the same.

Pausing is an option in your account panel under the service. You can pause a service going forward but obviously not for the current month.

 

[CloudStrif3]

Pausing is an option in your account panel under the service. You can pause a service going forward but obviously not for the current month.

Yes, I see this. Who are you using at the moment? PM me details perhaps? Thanks.

 

[CloudStrif3]

Speed test:
Download Speed: 2836 kbps (354.5 KB/sec transfer rate)
Upload Speed: 842 kbps (105.3 KB/sec transfer rate)
Latency: 26 ms
Jitter: 3 ms

I even got a call from Telkom to say the problem was fixed...however...I guessed wrong.
At the same time, over the weekend my account was even upgraded to unshaped! So i'm paying more...for? you guessed it...nothing. Def not a 20mbps line...

And this is now:

Download Speed: 4087 kbps (510.9 KB/sec transfer rate)
Upload Speed: 846 kbps (105.8 KB/sec transfer rate)
Latency: 53 ms
Jitter: 173 ms
2017/03/14, 01:21:23

Bleh.

 

[AfriMan]

Signs of congestion on the Afrihost IPC in the East, throughput is not much better

All tests done on the same line, the same PC, and the same Router

Afrihost
1 * * *
2 dbn-up2.ip.adsl.co.za (169.1.5.173) 162.323 ms 160.243 ms 161.104 ms
3 dbn-up2.ip.adsl.co.za (169.1.5.174) 143.610 ms 140.184 ms 138.927 ms
4 dbn-in1.ip.adsl.co.za (169.1.5.204) 128.606 ms 126.441 ms 122.213 ms
5 169-1-21-32.ip.afrihost.co.za (169.1.21.32) 177.817 ms 177.165 ms 178.593 ms
6 169-1-5-243.ip.afrihost.co.za (169.1.5.243) 179.328 ms 177.386 ms 178.131 ms
7 72.14.239.53 (72.14.239.53) 169.982 ms 171.205 ms 172.190 ms
8 google-public-dns-b.google.com (8.8.4.4) 126.374 ms 125.203 ms 124.875 ms

Mweb
1 * * *
2 197-82-5-249.dbn.mweb.co.za (197.82.5.249) 15.918 ms 15.524 ms 15.994 ms
3 501.po-channel10.trv-ipc-1.optinet.net (197.82.5.250) 20.939 ms 21.475 ms 20.924 ms
4 vl92.trv-hscore-1.optinet.net (197.82.2.3) 15.768 ms 16.026 ms 16.021 ms
5 201.te0-0-2-3.vic-pr-3.optinet.net (197.80.7.73) 28.802 ms 29.640 ms 29.577 ms
6 197-80-96-6.jhb.mweb.co.za (197.80.96.6) 34.700 ms 34.471 ms 34.975 ms
7 72.14.239.33 (72.14.239.33) 29.078 ms 29.633 ms 29.788 ms
8 google-public-dns-b.google.com (8.8.4.4) 34.716 ms 35.497 ms 33.977 ms

IS Ignite
1 * * *
2 196.38.74.214 (196.38.74.214) 21.153 ms 21.501 ms 21.404 ms
3 196.38.74.213 (196.38.74.213) 21.913 ms 21.825 ms 21.410 ms
4 196.26.210.212 (196.26.210.212) 20.938 ms 21.002 ms 21.180 ms
5 mi-za-umh-p8-ten-0-0-1-1.ip.isnet.net (168.209.93.204) 21.925 ms 21.289 ms 20.927 ms
6 mi-za-bry-p8-ten-0-7-2-0sub10.ip.isnet.net (168.209.0.178) 45.099 ms 43.368 ms 44.841 ms
7 core2a-bry-gi0-0-0.ip.isnet.net (168.209.217.2) 36.957 ms 37.390 ms 37.159 ms
8 core2a-pkl-te1-2.isnet.net (168.209.100.241) 42.116 ms 42.031 ms 42.870 ms
9 pr2-pkl-xe-2-2-0.ip.isnet.net (168.209.1.179) 37.215 ms 36.994 ms 36.936 ms
10 72.14.205.16 (72.14.205.16) 43.360 ms 42.249 ms 43.118 ms
11 72.14.239.35 (72.14.239.35) 37.957 ms 37.168 ms 37.136 ms
12 google-public-dns-b.google.com (8.8.4.4) 36.460 ms 36.013 ms 37.430 ms

BRAS PING
PING bras.afrihost.com (155.239.255.250) from 169.0.237.142: 56 data bytes
64 bytes from 155.239.255.250: icmp_seq=0 ttl=64 time=14.353 ms
64 bytes from 155.239.255.250: icmp_seq=1 ttl=64 time=13.965 ms
64 bytes from 155.239.255.250: icmp_seq=2 ttl=64 time=14.193 ms
64 bytes from 155.239.255.250: icmp_seq=3 ttl=64 time=13.959 ms
64 bytes from 155.239.255.250: icmp_seq=4 ttl=64 time=13.191 ms
64 bytes from 155.239.255.250: icmp_seq=5 ttl=64 time=12.937 ms
64 bytes from 155.239.255.250: icmp_seq=6 ttl=64 time=12.927 ms
64 bytes from 155.239.255.250: icmp_seq=7 ttl=64 time=12.917 ms
64 bytes from 155.239.255.250: icmp_seq=8 ttl=64 time=14.393 ms
64 bytes from 155.239.255.250: icmp_seq=9 ttl=64 time=14.379 ms

--- bras.afrihost.com ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 12.917/13.721/14.393/0.616 ms

the first result is quite horrible, though the rest seem pretty acceptable. It's a little hard cos we can't see the hop to the router or the BRAS, so we don't really know if there are other contributing factors. Would definitely like to see more full results to analyse

 

[AfriMan]

Still see major issues in Cape Town, this starts in the evenings only..

For example a trace to afrihost.co.za, a couple of the hops in Cape Town struggle.

| 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 |
| bu-ether1.cpt-p-1.optinet.net - 5 | 2134 | 2041 | 55 | 141 | 269 | 145 |
| te0-7-0-0.cpt-p-2.optinet.net - 5 | 2106 | 2006 | 56 | 151 | 301 | 172 |
| tengig-0-7-0-1-vic-p-1.mweb.co.za - 4 | 2202 | 2126 | 55 | 127 | 212 | 127 |
| 197-84-4-101.cpt.mweb.co.za - 4 | 2193 | 2115 | 55 | 59 | 79 | 56 |
| 201.bu-ether5.vic-pe-2.optinet.net - 5 | 2138 | 2046 | 0 | 62 | 103 | 69 |
| 197-81-226-81.jhb.mweb.co.za - 3 | 2262 | 2201 | 52 | 69 | 173 | 62 |
| 197-81-226-61.jhb.mweb.co.za - 4 | 2182 | 2101 | 60 | 68 | 1062 | 69 |
| 197-81-229-4.jhb.mweb.co.za - 5 | 2118 | 2021 | 61 | 65 | 119 | 66 |
| 197-81-229-11.jhb.mweb.co.za - 5 | 2158 | 2071 | 116 | 186 | 220 | 205 |
| 41-86-112-68.mweb.co.za - 4 | 2190 | 2111 | 54 | 57 | 83 | 60 |

Seeing lots of packet loss all over this result as well, and performance is also poor on the 3rd hop. Any idea what your ping to the BRAS is at the moment?

 

[AfriMan]

Switched ISP and a huge difference. I've now paused this account, will test periodically but going to spend my money where it actually gets you data. Benefit of the doubt for you chaps to fix but this has been a issue for the month and nothing has been done.

We are definitely monitoring closely and looking for anomalies. If we can reproduce the issues mentioned in this thread, we'll definitely make changes to improve the experience

 

[AfriMan]

Yep. Something is up with the network.

BRAS is, as always, fine. Note never any packet loss here.

Target Name: bras.afrihost.com
         IP: 155.239.255.250
  Date/Time: 13 Mar 2017 9:26:00 PM - 13 Mar 2017 9:36:00 PM

Hop  Sent  PL%    Min    Max    Avg  Host Name / [IP]
  1    32    0   0.75   1.38   0.93  router.asus.com [192.168.1.1]
  2    32    0  18.77  20.55  19.55  bras.afrihost.com [155.239.255.250]

afrihost.co.za done for reference. Show's the same issues I'm seeing when tracing to catchup.dstv.com - latency spikes and packet loss.

Target Name: afrihost.co.za
         IP: 41.86.112.68
  Date/Time: 13 Mar 2017 9:23:08 PM - 13 Mar 2017 9:33:08 PM

Hop  Sent  PL%     Min     Max     Avg  Host Name / [IP]
  1    43    0    0.73    1.57    1.08  router.asus.com [192.168.1.1]
  2    43  100       0       0       0   [-]
  3    43   42   20.41   21.84   21.08  cpt-up1.ip.adsl.co.za [169.1.5.105]
  4    43    2   28.77  151.98  104.58  cpt-up2.ip.adsl.co.za [169.1.5.106]
  5    43    0   20.16   44.68   21.65  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6    43    2   85.79  165.50  147.76  optinet.ixp.capetown [196.10.140.145]
  7    43    7  150.02  187.32  173.00  te0-0-0-1.cpt-p-2.optinet.net [197.84.7.34]
  8    43   12  147.65  190.24  176.15  tengig-0-7-0-1-vic-p-1.mweb.co.za [197.84.4.47]
  9    43    9   41.50  109.25   70.38  101.te0-0-2-0.vic-tr-1.optinet.net [197.80.7.4]
 10    43    0  113.18  182.97  166.97  197-81-226-77.jhb.mweb.co.za [197.81.226.77]
 11    43    0   39.86  110.52   46.11  197-81-226-53.jhb.mweb.co.za [197.81.226.53]
 12    43    0   80.75  173.61  128.56  197-81-229-2.jhb.mweb.co.za [197.81.229.2]
 13    43    0   39.71   50.02   41.07  197-81-229-9.jhb.mweb.co.za [197.81.229.9]
 14    43    7   41.00   71.28   43.11  afrihost.co.za [41.86.112.68]

Now an interesting note.
There's absolutely no packet loss to Hop 3 [169.1.5.105] if traced alone. Latency is also stable.

Target Name: 169.1.5.105
         IP: 169.1.5.105
  Date/Time: 13 Mar 2017 9:31:30 PM - 13 Mar 2017 9:41:30 PM

Hop  Sent  PL%    Min    Max    Avg  Host Name / [IP]
  1    55    0   0.58   1.93   0.98  router.asus.com [192.168.1.1]
  2    54  100      0      0      0   [-]
  3    55    0  19.95  23.46  21.08  169.1.5.105 [169.1.5.105]

Now notice the issues when I trace to Hop 4 [169.1.5.106]. Terrible latency and packet loss.

Target Name: 169.1.5.106
         IP: 169.1.5.106
  Date/Time: 13 Mar 2017 9:33:36 PM - 13 Mar 2017 9:43:36 PM

Hop  Sent  PL%    Min     Max     Avg  Host Name / [IP]
  1    43    0   0.71    1.05    0.86  router.asus.com [192.168.1.1]
  2    43  100      0       0       0   [-]
  3    43   35  20.36   31.30   21.57  cpt-up1.ip.adsl.co.za [169.1.5.105]
  4    43    0  75.71  152.60  121.35  169.1.5.106 [169.1.5.106]

Think that's enough to get the team looking into this ??

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.

 

[AfriMan]

Speed test:
Download Speed: 2836 kbps (354.5 KB/sec transfer rate)
Upload Speed: 842 kbps (105.3 KB/sec transfer rate)
Latency: 26 ms
Jitter: 3 ms

I even got a call from Telkom to say the problem was fixed...however...I guessed wrong.
At the same time, over the weekend my account was even upgraded to unshaped! So i'm paying more...for? you guessed it...nothing. Defs not a 20mbps line...

Latency seems pretty good, but that is definitely horrible throughput for a 20Mbps line

That should have nothing to do with shaping though. Drop me a PM so we can troubleshoot further

 

[Hummercellc]

the first result is quite horrible, though the rest seem pretty acceptable. It's a little hard cos we can't see the hop to the router or the BRAS, so we don't really know if there are other contributing factors. Would definitely like to see more full results to analyse

PPPoE from notebook with no other devices connected. And I pinged the bras there.

You can clearly see its a Afrihost problem. But if you believe those tests do not show you anything, well who am I to argue. Best to start shopping for a new ISP, this started happening more and more frequently.

 

[AfriMan]

PPPoE from notebook with no other devices connected. And I pinged the bras there.

You can clearly see its a Afrihost problem. But if you believe those tests do not show you anything, well who am I to argue. Best to start shopping for a new ISP, this started happening more and more frequently.

I meant in the tests for each run - there is clearly a big difference in the first test compared to the others, so knowing the results specific to each test. So if there was a spike in latency while running the first test, it wouldn't show up later.

We're definitely not seeing latency or complaints in the East right now, so we'll need to see exactly what is happening to investigate further.

 

[danny0]

Generally it's not possible... Could you DM me your details and I'll see what I can do.

AfriGenie... you're a freaking GENIE!!!

Wow dude! I got an sms from Telkom last night around 8pm saying my line is ready for migration.

Why'd you have to be so helpful.... now i feel bad for leaving AH.

 

[AfriMan]

AfriGenie... you're a freaking GENIE!!!

Wow dude! I got an sms from Telkom last night around 8pm saying my line is ready for migration.

Why'd you have to be so helpful.... now i feel bad for leaving AH.

The road back is just as easy

Glad to hear you're all squared away

 

[danny0]

The road back is just as easy

Glad to hear you're all squared away

Talk about bitter-sweet

 

[jdido87]

If i reduce my cap would I forfeit data already accumulated. I have a lot of data expiring every month.

 

[savage]

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.

So from everything provided, you just turn a blind eye to everything else? WOW, talk about being selective.

No good riddance. I think you've just proven that you have NFC what you are doing...

 

[AfriMan]

Talk about bitter-sweet

At least you know that it's never really final - you can always change your mind

 

[AfriMan]

If i reduce my cap would I forfeit data already accumulated. I have a lot of data expiring every month.

Reducing your cap will only affect your next data allocation. It won't affect roll over data and your data already allocated in the current month.

 

[jdido87]

Reducing your cap will only affect your next data allocation. It won't affect roll over data and your data already allocated in the current month.

Thanks you for that