Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
Exchange congestion is entirely out of our hands.
I get that. It's why I need AH to drive them hard to correct the issue. It's why I have my line with you guys rather than TI. :)

We'll need to see a ping to bras.afrihost.com to see if the latency jumps up from there. I can definitely tell you that there's no where near the amount of latency on our network compared to the results you've posted here.

Please include a ping to bras.afrihost.com, the more pings the better. This will monitor your latency to your exchange.

Here you go. Pings this evening to bras.afrihost.com.
No packet loss noted tonight. Just erratic latency.
Code:
Target Name: bras.afrihost.com
         IP: 155.239.255.250
  Date/Time: 04-Aug-16 20:35:52 to 04-Aug-16 20:40:52

Hop Sent Err PL% Min  Max Avg  Host Name / [IP]
 1   301   0 0.0   0    3   0  router.asus.com [192.168.1.1]
 2   301   0 0.0  18 1027 182  [155.239.255.250]

The attached image shows it's erratic
Untitled.png
 
Could somebody explain the limited twitch bandwidth?

40Mb line can't handle a 5Mb stream... Can watch the TI but I expected to be able to watch in source quality

No idea if you live in Cape Town but I've been struggling with this for about a year now. 20mb line here can only watch on high (if I'm lucky) but usually medium and lower.
 
There it goes... Routing to M-Web broken. Youtube videos not streaming due to adverts not being able to load... Very very frustrating.

M-Web.

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

1 <1 ms <1 ms <1 ms 192.168.1.254
2 * * * Request timed out.
3 22 ms 20 ms 19 ms dbn-up1.ip.adsl.co.za [169.1.5.161]
4 21 ms 19 ms 19 ms dbn-up2.ip.adsl.co.za [169.1.5.162]
5 21 ms 19 ms 19 ms 169-1-5-208.ip.afrihost.co.za [169.1.5.208]
6 19 ms 18 ms 19 ms optinet.ixp.durban [196.10.141.75]
7 * * * Request timed out.
8 * * * Request timed out.


News24

Tracing route to x.24.com [41.86.110.143]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 * * * Request timed out.
3 21 ms 19 ms 19 ms dbn-up1.ip.adsl.co.za [169.1.5.161]
4 20 ms 20 ms 19 ms dbn-up2.ip.adsl.co.za [169.1.5.162]
5 20 ms 19 ms 19 ms 169-1-5-208.ip.afrihost.co.za [169.1.5.208]
6 19 ms 19 ms 18 ms optinet.ixp.durban [196.10.141.75]
7 * * * Request timed out.
8 * * * Request timed out.

this is what i get tracing to www.mweb.co.za


C:\Users\Dell>tracert www.mweb.co.za

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

1 2 ms 2 ms 4 ms 192.168.1.1
2 * * * Request timed out.
3 * 14 ms 10 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 16 ms 10 ms 10 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 96 ms 99 ms 108 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 12 ms 11 ms 10 ms optinet.ixp.capetown [196.10.140.145]
7 80 ms 73 ms 69 ms te0-0-0-1.cpt-p-1.optinet.net [197.84.7.1]
8 12 ms 11 ms 10 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
9 16 ms 10 ms 10 ms 196.28.178.66
10 17 ms 15 ms 11 ms cte-core-sw2.vwol.net [196.41.144.35]
11 13 ms 11 ms 12 ms www.mweb.co.za [196.2.63.110]

Trace complete.

C:\Users\Dell>



C:\Users\Dell>ping bras.afrihost.com

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 10ms, Average = 9ms

C:\Users\Dell>


Tracing route to x.24.com [41.86.110.143]
over a maximum of 30 hops:

1 3 ms 4 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 * * 70 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 22 ms 22 ms 23 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 23 ms 23 ms 23 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 11 ms 13 ms 11 ms optinet.ixp.capetown [196.10.140.145]
7 40 ms 42 ms 41 ms te0-0-0-1.cpt-p-1.optinet.net [197.84.7.1]
8 33 ms 39 ms 96 ms vl12.cpt-hscore-2.optinet.net [197.84.5.254]
9 25 ms 10 ms 10 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
10 12 ms 10 ms 11 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]
11 12 ms 10 ms 10 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
12 42 ms 38 ms 41 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
13 12 ms 10 ms 10 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.
 
Last edited:
There it goes... Routing to M-Web broken. Youtube videos not streaming due to adverts not being able to load... Very very frustrating.

M-Web.

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

1 <1 ms <1 ms <1 ms 192.168.1.254
2 * * * Request timed out.
3 22 ms 20 ms 19 ms dbn-up1.ip.adsl.co.za [169.1.5.161]
4 21 ms 19 ms 19 ms dbn-up2.ip.adsl.co.za [169.1.5.162]
5 21 ms 19 ms 19 ms 169-1-5-208.ip.afrihost.co.za [169.1.5.208]
6 19 ms 18 ms 19 ms optinet.ixp.durban [196.10.141.75]
7 * * * Request timed out.
8 * * * Request timed out.


News24

Tracing route to x.24.com [41.86.110.143]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 * * * Request timed out.
3 21 ms 19 ms 19 ms dbn-up1.ip.adsl.co.za [169.1.5.161]
4 20 ms 20 ms 19 ms dbn-up2.ip.adsl.co.za [169.1.5.162]
5 20 ms 19 ms 19 ms 169-1-5-208.ip.afrihost.co.za [169.1.5.208]
6 19 ms 19 ms 18 ms optinet.ixp.durban [196.10.141.75]
7 * * * Request timed out.
8 * * * Request timed out.

Yip, same story. But at least general latency has improved. For how long who knows. Afrihost's network is like a lucky packet, you never know what you will get.

We're actively working on this, our Team is definitely making progress, this is a top-priority for us.
 
No idea if you live in Cape Town but I've been struggling with this for about a year now. 20mb line here can only watch on high (if I'm lucky) but usually medium and lower.

That should definitely not be the case. :( Which DNS Servers are you using at the moment?
 
this is what i get tracing to www.mweb.co.za


C:\Users\Dell>tracert www.mweb.co.za

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

1 2 ms 2 ms 4 ms 192.168.1.1
2 * * * Request timed out.
3 * 14 ms 10 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 16 ms 10 ms 10 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 96 ms 99 ms 108 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 12 ms 11 ms 10 ms optinet.ixp.capetown [196.10.140.145]
7 80 ms 73 ms 69 ms te0-0-0-1.cpt-p-1.optinet.net [197.84.7.1]
8 12 ms 11 ms 10 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
9 16 ms 10 ms 10 ms 196.28.178.66
10 17 ms 15 ms 11 ms cte-core-sw2.vwol.net [196.41.144.35]
11 13 ms 11 ms 12 ms www.mweb.co.za [196.2.63.110]

Trace complete.

C:\Users\Dell>



C:\Users\Dell>ping bras.afrihost.com

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 10ms, Average = 9ms

C:\Users\Dell>


Tracing route to x.24.com [41.86.110.143]
over a maximum of 30 hops:

1 3 ms 4 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 * * 70 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 22 ms 22 ms 23 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 23 ms 23 ms 23 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 11 ms 13 ms 11 ms optinet.ixp.capetown [196.10.140.145]
7 40 ms 42 ms 41 ms te0-0-0-1.cpt-p-1.optinet.net [197.84.7.1]
8 33 ms 39 ms 96 ms vl12.cpt-hscore-2.optinet.net [197.84.5.254]
9 25 ms 10 ms 10 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
10 12 ms 10 ms 11 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]
11 12 ms 10 ms 10 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
12 42 ms 38 ms 41 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
13 12 ms 10 ms 10 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.

:(

From what our Team has been able to figure out, it looks like the issue with connections to Mweb is largely affecting our Clients in the East and South. We're working overtime to get this figured out.
 
Last edited:
Back to struggling again
Cannot cownload from usenet or any other P2p

Struggling to connect to work VPN, and when connected takes up to a minute to do a screen update. Started again at 19:00 this evening. Taking bets it will work fine again after 22:00 like in the past.
Shaping again on Business???????????????

That shouldn't have been the case last night. What sort of speeds were you getting on your connection?
 
Afri-ppl, if I move my ADSL line to be managed by Afrihost, and in the future I decide to move it back to Telkom, is it true that the line may be disconnected for a few days during the move?
 
Afri-ppl, if I move my ADSL line to be managed by Afrihost, and in the future I decide to move it back to Telkom, is it true that the line may be disconnected for a few days during the move?

I'm afraid so... Although in my experience the downtime has always been pretty minimal.
 
That should definitely not be the case. :( Which DNS Servers are you using at the moment?

Google's DNS. I did send you (at least I think it was you) a PM about it while ago and never got a response so I figured you guys were busy.
 
Google's DNS. I did send you (at least I think it was you) a PM about it while ago and never got a response so I figured you guys were busy.

Sorry if we missed your PM :(
Have you tried using auto-assigned DNS to see if this helps at all?

Twitch has always been pretty bandwidth intensive, from my tests some streams work OK and others don't across multiple ISPs.
 
Hi Afriguy,

The problem, as someone else pointed out earlier, appears to be occurring after the bras.
See ping trace for bras and afrihost.com done at exactly the same time.
Note packet loss at Hop 3 of the trace to afrihost.com vs no packet loss to bras.
So... thoughts?

... oh and BTW - still no feedback on my support ticket.
Telkom SMS thinks the problem is resolved. :(


Code:
Target Name: bras.afrihost.com
         IP: 155.239.255.250
  Date/Time: 05/08/2016 13:24:48 to 05/08/2016 13:34:13

Hop Sent Err PL% Min Max Avg  Host Name / [IP]
 1   226   0 0.0   0   1   0  router.asus.com [192.168.1.1]
 2   226   0 0.0  18 161  20  [155.239.255.250]

Code:
Target Name: www.afrihost.com
         IP: 104.20.31.244
  Date/Time: 05/08/2016 13:25:43 to 05/08/2016 13:34:10

Hop Sent Err   PL% Min Max Avg  Host Name / [IP]
 1   203   0   0.0   0   5   0  router.asus.com [192.168.1.1]
 2   203 203 100.0   0   0   0   [-]
[B] 3   203  95  46.8  20  71  21  cpt-up1.ip.adsl.co.za [169.1.5.105][/B]
 4   203   1   0.5  19 261  22  cpt-in1.ip.adsl.co.za [169.1.5.118]
 5   203   0   0.0  19 253  23  cpt-net1.ip.adsl.co.za [169.1.5.128]
 6   203   0   0.0  20 161  21  [41.164.52.40]
 7   203   0   0.0  20 114  23  if-ae-7-0.tcore2.KLT-Cape-Town.as6453.net [41.206.165.25]
 8   203   0   0.0 170 566 179  if-ae-2-2.tcore1.KLT-Cape-Town.as6453.net [41.206.164.253]
 9   203   0   0.0 162 679 166  if-ae-5-10.tcore2.PV9-Lisbon.as6453.net [80.231.159.93]
10   203   0   0.0 163 630 167  if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
11   203   0   0.0 162 579 169  if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
12   203  27  13.3 162 375 165  if-ae-19-2.tcore2.L78-London.as6453.net [80.231.138.22]
13   203   0   0.0 162 480 167  if-ae-15-2.tcore2.LDN-London.as6453.net [80.231.131.118]
14   203   0   0.0 166 434 170  [80.231.20.66]
15   203   0   0.0 165 261 167  [104.20.31.244]
 
Hi Afriguy,

The problem, as someone else pointed out earlier, appears to be occurring after the bras.
See ping trace for bras and afrihost.com done at exactly the same time.
Note packet loss at Hop 3 of the trace to afrihost.com vs no packet loss to bras.
So... thoughts?

... oh and BTW - still no feedback on my support ticket.
Telkom SMS thinks the problem is resolved. :(


-snip

If your exchange is congested and you're on a newer ESR (which you are) latency will reflect as being high on the 3rd hop since the BRAS no longer accepts ICMP requests.
Pinging bras.afrihost.com shows latency to your exchange, of which yours if high.

Do you experience the same issue when testing with another ISP?
 
If your exchange is congested and you're on a newer ESR (which you are) latency will reflect as being high on the 3rd hop since the BRAS no longer accepts ICMP requests.
Pinging bras.afrihost.com shows latency to your exchange, of which yours if high.

Do you experience the same issue when testing with another ISP?
If you recall my previous post - I don't have accounts with other ISPs.
You might also recall my additional comments on the subject.

I've just received this from support. What the .... !!!!
Would have been nice if they picked up the telephone to talk to me.
If they did they would have realized that a) I'm not a pleb, b) I'm very familiar with ASSIA, c) evidence clearly points to the issue being on the Telkom side (you seem to concur), d) AH manage my line and therefore should be driving resolution with Telkom and e) what's the modem re-config going to achieve - a reset maybe, but re-configure. Eish!

Dunno man - put yourself in my shoes... actually put yourself in the shoes of a large number of people currently experiencing issues.

:twisted:

Charlotte said:
I have analyzed your line connection 02155xxxxx, and found that it's syncing on 22522 kbps with your exchange. What this means is that your exchange has been updated, and along with that there is some heightened latency reported. Unfortunately, this is not something we can correct, as it's part of the new ASSIA system of Telkom intertwined with the line profile optimization system.

Also, there are no defects found on this line, and from what I can tell, everything is running 100%, and healthy.

What I would like you to do however, is to reconfigure your router by using the setup wizard from the beginning till the end and connect to your 1GB capped account.

Protocol should be set to PPPoE
PPPoE username: xxxxxx
PPPoE password: xxxxxx
Multiplexing method should be set to LLC
VPI set to 8
VCI set to 35
NAT: Enabled
- Obtain Dynamic IP from ISP
- Use the following Domain Name Servers as specified:
Primary DNS: 169.1.1.1
Secondary DNS: 169.1.1.2

Once configured and restarted, please test your connection with no wireless devices connected, and one computer connected via a LAN cable; as well as all background downloads turned off.

Once tested, and happy with the the results; enter the setup wizard again, test the connection with your regular account, and see if there is still the problem with packet loss you're experiencing.

Thanking you in advance for doing the above, and I look forward to the results thereof.

BTW -
1. My exchange was upgraded months ago. The pain associated was overcome. Charlotte's pasting a PR clip.
2. ASSIA hasn't changed / been changing the profile. The sync, interleave depth, interleave block size haven't changed since it was stabilized months ago.
3. If it's ASSIA then it's now time to move me to FASTPATH.
4. So is everyone forgetting that Telkom had had node issues a few weeks ago.
 
Last edited:
That shouldn't have been the case last night. What sort of speeds were you getting on your connection?
I did not check the speeds as I had to sort out an emergency at work. But just to give you and idea. going in via the VPN and then RDP to a pc at work was frustrating. Response was 15-20 seconds between keystrokes

Connected via a different ISP and response was instantaneous.

Will check again tonight
 
Back to struggling again
Cannot cownload from usenet or any other P2p

Struggling to connect to work VPN, and when connected takes up to a minute to do a screen update. Started again at 19:00 this evening. Taking bets it will work fine again after 22:00 like in the past.
Shaping again on Business???????????????

Same story here - every single night. Not only P2P / Usenet, but can barely even work in a simple SSH session...
 
If you recall my previous post - I don't have accounts with other ISPs.
You might also recall my additional comments on the subject.

I've just received this from support. What the .... !!!!
Would have been nice if they picked up the telephone to talk to me.
If they did they would have realized that a) I'm not a pleb, b) I'm very familiar with ASSIA, c) evidence clearly points to the issue being on the Telkom side (you seem to concur), d) AH manage my line and therefore should be driving resolution with Telkom and e) what's the modem re-config going to achieve - a reset maybe, but re-configure. Eish!

Dunno man - put yourself in my shoes... actually put yourself in the shoes of a large number of people currently experiencing issues.

:twisted:



BTW -
1. My exchange was upgraded months ago. The pain associated was overcome. Charlotte's pasting a PR clip.
2. ASSIA hasn't changed / been changing the profile. The sync, interleave depth, interleave block size haven't changed since it was stabilized months ago.
3. If it's ASSIA then it's now time to move me to FASTPATH.
4. So is everyone forgetting that Telkom had had node issues a few weeks ago.

This is part of the troubleshooting process. I understand you're frustrated, but we need to run through various tests together to get the bottom of the test.

Are you not able to test a friends account or sign up for a trial account as a comparison?
Either way, the pings to bras.afrihost.com are concerning and indicate issues/ congestion on your exchange.
 
Same story here - every single night. Not only P2P / Usenet, but can barely even work in a simple SSH session...

Well, I am just a little bit away from you in Table View, I did 17GB last night P2P and 19GB the night before (10Mbps line, average ~800kB/s).
805.png
 
100% speed

Garmin update from mweb CDN.

dbd7165bfd.png
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X