Afrihost Capped DSL Feedback

I either have no luck or intermittent buffering with streaming, inc youtube. But my Webafrica backup account runs fine. Can you explain why? Below is the traceroute.

Tracing route to afrihost.co.za [169.1.1.221]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 * * * Request timed out.
4 59 ms 9 ms 9 ms 169-1-21-170.ip.afrihost.co.za [169.1.21.170]
5 115 ms 115 ms 126 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
6 * 128 ms 108 ms 169-1-5-77.ip.afrihost.co.za [169.1.5.77]
7 9 ms 9 ms 9 ms luzonex.net.afrihost.co.za [169.1.1.221]

Trace complete.

C:\Users\>tracert google.com

Tracing route to google.com [216.58.223.14]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 * * * Request timed out.
4 10 ms 9 ms 10 ms jhb-in1.ip.adsl.co.za [169.1.5.42]
5 * 9 ms 9 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
6 10 ms 9 ms 8 ms 169-1-5-74.ip.afrihost.co.za [169.1.5.74]
7 9 ms 9 ms 14 ms 169-1-5-241.ip.afrihost.co.za [169.1.5.241]
8 9 ms 9 ms 10 ms 72.14.237.239
9 9 ms 32 ms 8 ms jnb01s07-in-f14.1e100.net [216.58.223.14]

Trace complete.

C:\Users\>tracert youtube.com

Tracing route to youtube.com [216.58.223.14]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 * 9 ms 9 ms jhb-up3.ip.adsl.co.za [169.1.5.29]
4 10 ms 12 ms 35 ms jhb-in1.ip.adsl.co.za [169.1.5.42]
5 57 ms 57 ms 44 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
6 * 10 ms 9 ms 169-1-5-74.ip.afrihost.co.za [169.1.5.74]
7 * 19 ms 17 ms 169-1-5-241.ip.afrihost.co.za [169.1.5.241]
8 9 ms 9 ms 9 ms 72.14.237.239
9 8 ms 28 ms 24 ms jnb01s07-in-f14.1e100.net [216.58.223.14]

Seems very intermittent. We're not seeing general issues on our network (especially in JHB). Can you please ping bras.afrihost.com so I can see the whole picture? :(
 
I submitted a ticket regarding frequent disconnects on the adsl line as well as high noise on the line.
10 days later I get a message saying that the connection was reset and the ports recreated and that my speeds should be higher
which has nothing to do with the problem that I mentioned 10 days prior . . .
 
I submitted a ticket regarding frequent disconnects on the adsl line as well as high noise on the line.
10 days later I get a message saying that the connection was reset and the ports recreated and that my speeds should be higher
which has nothing to do with the problem that I mentioned 10 days prior . . .

Port was re created perhaps?
 
I submitted a ticket regarding frequent disconnects on the adsl line as well as high noise on the line.
10 days later I get a message saying that the connection was reset and the ports recreated and that my speeds should be higher
which has nothing to do with the problem that I mentioned 10 days prior . . .

That's pretty terrible if we got it wrong like that :(

Can you please PM with the ticket reference so I can pass that on to our QA team? :(
 
Pretty crappy streaming experience on Amazon Prime at the moment. Speedtest shows 8MB on 8MB line. First real problem in a long time.
 
Not a pretty picture, seems international is toast.

traceroute to primevideo.com (72.21.210.29), 64 hops max, 52 byte packets
1 192.168.11.1 (192.168.11.1) 1.706 ms 1.233 ms 1.247 ms
2 * * *
3 cpt-rx2.ip.adsl.co.za (169.1.5.82) 23.980 ms 22.373 ms 23.987 ms
4 cpt-net1.ip.adsl.co.za (169.1.5.128) 24.077 ms 21.809 ms 24.109 ms
5 41.164.52.40 (41.164.52.40) 23.694 ms 23.511 ms 24.795 ms
6 ix-ae-7-0.tcore1.klt-cape-town.as6453.net (41.206.164.53) 25.143 ms 23.546 ms 24.238 ms
7 if-ae-5-2.tcore2.pv9-lisbon.as6453.net (80.231.159.89) 260.967 ms
if-ae-5-2.tcore2.pv9-lisbon.as6453.net (80.231.159.109) 167.940 ms
if-ae-2-2.tcore1.klt-cape-town.as6453.net (41.206.164.253) 247.858 ms
8 if-ae-5-2.tcore2.pv9-lisbon.as6453.net (80.231.159.61) 212.436 ms
if-xe-0-0-0-15.tcore1.pv9-lisbon.as6453.net (80.231.158.1) 279.157 ms
if-ae-2-2.tcore1.pv9-lisbon.as6453.net (80.231.158.5) 336.008 ms
9 if-ae-2-2.tcore1.pv9-lisbon.as6453.net (80.231.158.5) 276.286 ms 265.676 ms 306.718 ms
10 if-ae-2-2.tcore2.sv8-highbridge.as6453.net (80.231.139.1) 239.009 ms
if-ae-1-3.tcore1.sv8-highbridge.as6453.net (80.231.158.30) 255.529 ms
if-ae-2-2.tcore2.sv8-highbridge.as6453.net (80.231.139.1) 209.912 ms
11 if-ae-11-2.tcore1.l78-london.as6453.net (80.231.139.42) 170.343 ms
if-ae-2-2.tcore2.sv8-highbridge.as6453.net (80.231.139.1) 214.557 ms 211.476 ms
12 if-ae-17-2.tcore1.ldn-london.as6453.net (80.231.130.130) 252.906 ms 250.411 ms 259.941 ms
13 if-ae-17-2.tcore1.ldn-london.as6453.net (80.231.130.130) 243.587 ms
80.231.60.123 (80.231.60.123) 170.107 ms
if-ae-17-2.tcore1.ldn-london.as6453.net (80.231.130.130) 255.049 ms
14 80.231.60.123 (80.231.60.123) 168.526 ms 169.378 ms
ae-13.r24.londen12.uk.bb.gin.ntt.net (129.250.4.25) 170.305 ms
15 ae-13.r24.londen12.uk.bb.gin.ntt.net (129.250.4.25) 169.374 ms 168.471 ms 169.193 ms
16 ae-1.r08.nycmny01.us.bb.gin.ntt.net (129.250.5.62) 234.741 ms
ae-1.r07.nycmny01.us.bb.gin.ntt.net (129.250.3.181) 232.540 ms 237.929 ms
17 ae-1.r08.nycmny01.us.bb.gin.ntt.net (129.250.5.62) 237.234 ms
ae-1.r07.nycmny01.us.bb.gin.ntt.net (129.250.3.181) 230.945 ms
ae-0.a00.nycmny01.us.bb.gin.ntt.net (129.250.3.94) 323.955 ms
18 ae-0.a00.nycmny01.us.bb.gin.ntt.net (129.250.3.94) 335.570 ms
ae-2.amazon.nycmny01.us.bb.gin.ntt.net (129.250.201.126) 235.004 ms
ae-1.a00.nycmny01.us.bb.gin.ntt.net (129.250.6.55) 231.646 ms
19 ae-0.amazon.nycmny01.us.bb.gin.ntt.net (129.250.201.118) 235.690 ms
ae-1.amazon.nycmny01.us.bb.gin.ntt.net (129.250.201.122) 239.671 ms
ae-2.amazon.nycmny01.us.bb.gin.ntt.net (129.250.201.126) 239.352 ms
^C
 
internet has been up to crap after 5pm lately with heavy shaping looks like ah is out of ipc again

With many clients moving to fibre, we've actually been doing pretty well. But we upgraded extensively last year, so we're not seeing any issues for a while.

Any tests I can look at?
 
Not a pretty picture, seems international is toast.

traceroute to primevideo.com (72.21.210.29), 64 hops max, 52 byte packets
1 192.168.11.1 (192.168.11.1) 1.706 ms 1.233 ms 1.247 ms
2 * * *
3 cpt-rx2.ip.adsl.co.za (169.1.5.82) 23.980 ms 22.373 ms 23.987 ms
4 cpt-net1.ip.adsl.co.za (169.1.5.128) 24.077 ms 21.809 ms 24.109 ms
5 41.164.52.40 (41.164.52.40) 23.694 ms 23.511 ms 24.795 ms
6 ix-ae-7-0.tcore1.klt-cape-town.as6453.net (41.206.164.53) 25.143 ms 23.546 ms 24.238 ms
7 if-ae-5-2.tcore2.pv9-lisbon.as6453.net (80.231.159.89) 260.967 ms
if-ae-5-2.tcore2.pv9-lisbon.as6453.net (80.231.159.109) 167.940 ms
if-ae-2-2.tcore1.klt-cape-town.as6453.net (41.206.164.253) 247.858 ms
8 if-ae-5-2.tcore2.pv9-lisbon.as6453.net (80.231.159.61) 212.436 ms
if-xe-0-0-0-15.tcore1.pv9-lisbon.as6453.net (80.231.158.1) 279.157 ms
if-ae-2-2.tcore1.pv9-lisbon.as6453.net (80.231.158.5) 336.008 ms
9 if-ae-2-2.tcore1.pv9-lisbon.as6453.net (80.231.158.5) 276.286 ms 265.676 ms 306.718 ms
10 if-ae-2-2.tcore2.sv8-highbridge.as6453.net (80.231.139.1) 239.009 ms
if-ae-1-3.tcore1.sv8-highbridge.as6453.net (80.231.158.30) 255.529 ms
if-ae-2-2.tcore2.sv8-highbridge.as6453.net (80.231.139.1) 209.912 ms
11 if-ae-11-2.tcore1.l78-london.as6453.net (80.231.139.42) 170.343 ms
if-ae-2-2.tcore2.sv8-highbridge.as6453.net (80.231.139.1) 214.557 ms 211.476 ms
12 if-ae-17-2.tcore1.ldn-london.as6453.net (80.231.130.130) 252.906 ms 250.411 ms 259.941 ms
13 if-ae-17-2.tcore1.ldn-london.as6453.net (80.231.130.130) 243.587 ms
80.231.60.123 (80.231.60.123) 170.107 ms
if-ae-17-2.tcore1.ldn-london.as6453.net (80.231.130.130) 255.049 ms
14 80.231.60.123 (80.231.60.123) 168.526 ms 169.378 ms
ae-13.r24.londen12.uk.bb.gin.ntt.net (129.250.4.25) 170.305 ms
15 ae-13.r24.londen12.uk.bb.gin.ntt.net (129.250.4.25) 169.374 ms 168.471 ms 169.193 ms
16 ae-1.r08.nycmny01.us.bb.gin.ntt.net (129.250.5.62) 234.741 ms
ae-1.r07.nycmny01.us.bb.gin.ntt.net (129.250.3.181) 232.540 ms 237.929 ms
17 ae-1.r08.nycmny01.us.bb.gin.ntt.net (129.250.5.62) 237.234 ms
ae-1.r07.nycmny01.us.bb.gin.ntt.net (129.250.3.181) 230.945 ms
ae-0.a00.nycmny01.us.bb.gin.ntt.net (129.250.3.94) 323.955 ms
18 ae-0.a00.nycmny01.us.bb.gin.ntt.net (129.250.3.94) 335.570 ms
ae-2.amazon.nycmny01.us.bb.gin.ntt.net (129.250.201.126) 235.004 ms
ae-1.a00.nycmny01.us.bb.gin.ntt.net (129.250.6.55) 231.646 ms
19 ae-0.amazon.nycmny01.us.bb.gin.ntt.net (129.250.201.118) 235.690 ms
ae-1.amazon.nycmny01.us.bb.gin.ntt.net (129.250.201.122) 239.671 ms
ae-2.amazon.nycmny01.us.bb.gin.ntt.net (129.250.201.126) 239.352 ms
^C

If I am reading this correctly you're routing to the US, in which case the latency is pretty decent.

I'm not aware of any issues at the moment, but we'll test on our side as well.
 
internet is truly down the crapper every day after 5pm like before when ah had all this problems with ipc and doing serious shaping
 
Last edited:
Top
Sign up to the MyBroadband newsletter
X