Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
It could still be normalising, but the experience is better for a lot of clients.
Perhaps try a reboot?

=AFRIHOST=
Tracing route to ql.kreaper.co.za [196.44.45.98]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 72 ms 67 ms 63 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 75 ms 76 ms 78 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 75 ms 87 ms 74 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 75 ms 68 ms 72 ms adept.ct1.napafrica.net [196.10.140.72]
7 43 ms 43 ms 42 ms v498.pe0.adc.adept.za.net [196.44.40.193]
8 66 ms 63 ms 64 ms g0-9.bb3.adc.adept.za.net [196.44.40.118]
9 36 ms 33 ms 30 ms e1.fw0.adc.adept.za.net [196.44.32.197]
10 * * 77 ms ql.kreaper.co.za [196.44.45.98]


Trace complete.

=WEB AFRICA=
Tracing route to ql.kreaper.co.za [196.44.45.98]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 13 ms 14 ms 13 ms cdsl2-ctn-vl2473-ipc.ip.isnet.net [196.38.72.194]
4 12 ms 12 ms 12 ms vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
5 16 ms 12 ms 12 ms 196.35.115.136
6 12 ms 13 ms 12 ms mi-za-cpt-p8-te0-7-0-0.ip.isnet.net [168.209.2.13]
7 19 ms 12 ms 12 ms 168.209.2.131
8 13 ms 12 ms 32 ms neotel.cinx.net.za [196.223.22.24]
9 14 ms 12 ms 13 ms 172.18.48.29
10 14 ms 14 ms 15 ms neotel.pe0.ter.cpt.adept.za.net [41.164.53.2]
11 17 ms 17 ms 22 ms v498.pe0.adc.adept.za.net [196.44.40.193]
12 20 ms 23 ms 18 ms g0-9.bb3.adc.adept.za.net [196.44.40.118]
13 22 ms 17 ms 16 ms e1.fw0.adc.adept.za.net [196.44.32.197]
14 21 ms 17 ms 17 ms ql.kreaper.co.za [196.44.45.98]

Trace complete.

Please drop a note once Afrihost's sorted their IPC network latency issues.
 
=AFRIHOST=
Tracing route to ql.kreaper.co.za [196.44.45.98]
over a maximum of 30 hops:

-snip

Please drop a note once Afrihost's sorted their IPC network latency issues.

I'm sure you'll see the results start to normalise soon.
 
=AFRIHOST=
Tracing route to ql.kreaper.co.za [196.44.45.98]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 72 ms 67 ms 63 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 75 ms 76 ms 78 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 75 ms 87 ms 74 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 75 ms 68 ms 72 ms adept.ct1.napafrica.net [196.10.140.72]
7 43 ms 43 ms 42 ms v498.pe0.adc.adept.za.net [196.44.40.193]
8 66 ms 63 ms 64 ms g0-9.bb3.adc.adept.za.net [196.44.40.118]
9 36 ms 33 ms 30 ms e1.fw0.adc.adept.za.net [196.44.32.197]
10 * * 77 ms ql.kreaper.co.za [196.44.45.98]


Trace complete.

=WEB AFRICA=
Tracing route to ql.kreaper.co.za [196.44.45.98]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 13 ms 14 ms 13 ms cdsl2-ctn-vl2473-ipc.ip.isnet.net [196.38.72.194]
4 12 ms 12 ms 12 ms vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
5 16 ms 12 ms 12 ms 196.35.115.136
6 12 ms 13 ms 12 ms mi-za-cpt-p8-te0-7-0-0.ip.isnet.net [168.209.2.13]
7 19 ms 12 ms 12 ms 168.209.2.131
8 13 ms 12 ms 32 ms neotel.cinx.net.za [196.223.22.24]
9 14 ms 12 ms 13 ms 172.18.48.29
10 14 ms 14 ms 15 ms neotel.pe0.ter.cpt.adept.za.net [41.164.53.2]
11 17 ms 17 ms 22 ms v498.pe0.adc.adept.za.net [196.44.40.193]
12 20 ms 23 ms 18 ms g0-9.bb3.adc.adept.za.net [196.44.40.118]
13 22 ms 17 ms 16 ms e1.fw0.adc.adept.za.net [196.44.32.197]
14 21 ms 17 ms 17 ms ql.kreaper.co.za [196.44.45.98]

Trace complete.

Please drop a note once Afrihost's sorted their IPC network latency issues.
Exactly the same latency here in KZN.
Afrihost account 80ms
Mweb account 16ms
 
AfriGuy do we have any word on what caused the issues this afternoon?

There was an IPC issue which caused throughput levels to drop, that in turn created huge contention causing the slow speeds and latency :( As for the cause/ fix - I'm not 100% sure on the details just yet I'm afraid.
 
Slow DSL Speeds And Latency South Region

Hey guys

I've just marked the issue on the site as resolved, we've monitored for over 2 hours and are happy with the overall results we're seeing on monitoring.
If you are still seeing an issue with low throughput and high latency please shoot a mail with your DSL details to our Support team so we can better trend the information.
 
So what you're saying is the issue is resolved but we still need to send tests through because the issue is not resolved?

This is really quite something
 
Seeing the same ~90ms on ipc hop. Going to reboot the router to see if it helps at all
 
Definitely not back to normal. 172ms ping and 6mb speddtest on my 20mb adsl line.

Screenshot_2016-07-20-21-15-43.jpg
Tracert and bras.afrihost ping already tweeted to @afrihost. The network is still groaning badly here in East London.
 
Yep, same story after a reboot :( If anything its back to where it was this afternoon...

5491479819.png
 
1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 26 ms 24 ms 27 ms jhb-up7.ip.adsl.co.za [169.1.5.6]
4 136 ms 163 ms 140 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
5 27 ms 32 ms 33 ms eoh-ns.ixp.joburg [196.46.25.157]
6 23 ms 24 ms 27 ms 41-66-181-63-3f.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.63]
7 134 ms 138 ms 144 ms 104.20.72.110

Eish.
 
I gather there is still an issue because their Twitter account is now silent and not responding to me after I sent the tests they asked for.
 
@AfriGuy Feel free to pass this on to your support team.

Twitter
http://puu.sh/q8ql8/cb6886b4dd.png

Facebook
http://puu.sh/q8qqt/bb0cee9a60.png

YouTube
http://puu.sh/q8qvi/c2f0cb4a4b.png

Twitch
http://puu.sh/q8qzE/e3a9082796.png

MyBB
http://puu.sh/q8qDL/9328ceb16e.png

RANT
I've had enough for one day, experienced similar issues yesterday evening, since I've come home at around 15:30 the network has performed poorly and as of right now it being 21:30 that's a total of ~6 hours. The site says everything is running perfectly but the users and test results on here clearly say otherwise. /RANT
 
So from 400ms ping (pic below ) and unstable Internet, I put my MWEB details in and instantly 80ms (pic below ) and constant streams.


Come on afrihost!! Fix your network!

0244206d6bd3d4a61188e6d7256e5792.jpg
5b9f2042ac712c1d3873ec5b104653cb.jpg
 
Last edited:
It was alright for awhile now it is back to **** again. Rubberbanding now included in cs
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X