Afrihost Capped DSL Feedback

[AfriGenie]

Done!

Much appreciated

Got it! Thanks.

 

[steel_dog]

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.

Cool. Got to get to the bottom of this. As I mentioned in another post the issues just seem to rotate between days and people. I'm good with NNTP and YouTube this week. Others are struggling.
To summarize ...

• DSTV Watch Now (via immediate download) - not working at all on capped account. Works with SAIX account. I'll wait on a call from CC. [and holding thumbs on that 'cause I've not received promised callbacks on another issue. Bad form ]
• DNS - what's the official AH primary and secondary? Meaning the never changing best options. I assumed it was dns1.afrihost.com and dns2.afrihost.com but I was wrong. They aren't the ones being pushed to the modem.
• General speedtests - were poor on the capped acount and were perfect on the SAIX account. Someone, I assume CC, will feedback to us about this?

Thx, SD.

 

[longboy]

I have recently noticed that with my standard Telkom isp account that came with the router bundle, I get a constant 178-180ms ping to London Path of Exile/Diablo servers. With Afrihost unshaped capped it's much higher, around 200-250ms on bad days.

Any reason why it is this way? Not complainin', just curious.

 

[AfriGenie]

I have recently noticed that with my standard Telkom isp account that came with the router bundle, I get a constant 178-180ms ping to London Path of Exile/Diablo servers. With Afrihost unshaped capped it's much higher, around 200-250ms on bad days.

Any reason why it is this way? Not complainin', just curious.

Could be different routing that we use compared to Telkom. Does the latency on our side affect the gaming experience at all?

 

[longboy]

Could be different routing that we use compared to Telkom. Does the latency on our side affect the gaming experience at all?

Gaming experience is the same, I can't really tell the difference to be honest.

 

[Geoff.D]

Just to add to this debate on latencies. Last year until about October 2016, I would get about 13 ms to any router/server located at Teraco Isando. This year since I started measuring it again last week, it is now 26 ms.

Just shows that our ISPs and network providers are always "fiddling" in the engine and never leave well alone ...... Not that it makes much difference to what I use connectivity for, just saying ...

 

[AfriGenie]

Just to add to this debate on latencies. Last year until about October 2016, I would get about 13 ms to any router/server located at Teraco Isando. This year since I started measuring it again last week, it is now 26 ms.

Just shows that our ISPs and network providers are always "fiddling" in the engine and never leave well alone ...... Not that it makes much difference to what I use connectivity for, just saying ...

Routing isn't something that we can really leave as is once it's been configured. As networks expand and get upgraded we do have to make changes from time to time. It's always a priority for us to make sure that the network is stable and has enough redundancy in place.

 

[Geoff.D]

Routing isn't something that we can really leave as is once it's been configured. As networks expand and get upgraded we do have to make changes from time to time. It's always a priority for us to make sure that the network is stable and has enough redundancy in place.

Ja agreed. But tell me how one can "improve" network redundancy by effectively doubling latency and believe that this will be in the best interests of everyone? What has (Telkom/OpenServe in my case) done to improve redundancy that has effectively doubled the latency between PTA East and Teraco Isando? Poor network engineering and no consideration on the effects on other important parameters comes to mind. By this logic can we expect that a route between PTA and CT will now also have a doubling effect in Latency?

Well actually, that is about what has happened in my case! Latencies to CT were about 25 ms and are now also in the fifties. Something is not right here in the network configuration department in OpenServe.

 

[AfriGenie]

Ja agreed. But tell me how one can "improve" network redundancy by effectively doubling latency and believe that this will be in the best interests of everyone? What has (Telkom/OpenServe in my case) done to improve redundancy that has effectively doubled the latency between PTA East and Teraco Isando? Poor network engineering and no consideration on the effects on other important parameters comes to mind. By this logic can we expect that a route between PTA and CT will now also have a doubling effect in Latency?

Well actually, that is about what has happened in my case! Latencies to CT were about 25 ms and are now also in the fifties. Something is not right here in the network configuration department in OpenServe.

Distance has as much of an affect on latency as the quality of the network and the routing.

I think in most cases the latency to Cape Town from Pretoria will be around 50ms maybe a bit more maybe a bit less depending on the time of day or night.

Running a traceroute should give a good indication of the current network performance to Cape Town.

If you have a specific server in mind I can run one as well to compare to.

 

[Kosmik]

Sigh no throughput, again.

 

[homerj]

I can connect to the server and it says test successful but when it tries to download anything, it has zero throughput. Other servers work fine.

This is exactly the same for me, what is going on Afrihost?

When I switch to my IS provider I have no issues on news.is.co.za!!

 

[Kosmik]

This is exactly the same for me, what is going on Afrihost?

When I switch to my IS provider I have no issues on news.is.co.za!!

I'm going to switch accounts in a bit and see if still an issue. If resolved, going to cancel, don't see why paying for cap with zero throughput.

 

[AfriGenie]

I'm going to switch accounts in a bit and see if still an issue. If resolved, going to cancel, don't see why paying for cap with zero throughput.

That's not cool! To which service are you not seeing throughput?

 

[AfriGenie]

This is exactly the same for me, what is going on Afrihost?

When I switch to my IS provider I have no issues on news.is.co.za!!

Do you mean you aren't seeing throughput to our News Server?

 

[Kosmik]

Do you mean you aren't seeing throughput to our News Server?

Correct. Since the 1st already.

 

[roadcat]

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 |

 

[Hummercellc]

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

 

[Kosmik]

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.

 

[steel_dog]

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 ??

 

[savage]

but this has been a issue for the month and nothing has been done.

This has been an ongoing, daily issue for a LOT of PPL in CPT since October/November last year already

My MetroEthernet Fiber's hanging outside on the pole... Can't wait to show AH the finger. Sick of this shyte