Afrihost New Network Feedback

Status
Not open for further replies.
Cheers guys, I'm out.
We'll be back on Thursday - our Support team are standing by for any urgent queries over the public holiday.
 
Streaming is up **** creek without a paddle. Keeps buffering every few minutes.

Tracing route to hosted.co.za [196.38.40.162]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 7 ms 21 ms 8 ms 169-0-53-1.ip.afrihost.co.za [169.0.53.1]
3 * * * Request timed out.
4 11 ms 10 ms 9 ms jhb-up7.ip.adsl.co.za [169.1.5.6]
5 12 ms 10 ms 9 ms jhb-up8b.ip.adsl.co.za [169.1.5.56]
6 10 ms 10 ms 9 ms 41.169.57.218
7 10 ms 14 ms 73 ms is.jinx.net.za [196.223.14.10]
8 10 ms 11 ms 10 ms 168.209.1.140
9 12 ms 18 ms 11 ms 168.209.100.206
10 164 ms 209 ms 104 ms 168.209.217.17
11 558 ms 554 ms 390 ms 196.34.134.105
12 * 145 ms 88 ms gw.aserv.co.za [196.33.227.1]
13 107 ms 84 ms 44 ms duke2.aserv.co.za [196.38.40.162]

The timeout on 3 has been there since the streaming bull**** started
 
I just cant understand why this happens every single evening and goes back to normal in the morning. 2mb line.

MyBB Speedtest

When it is acting up again, please run my second tool (as attached below)...

The symptoms you mention tend to exchange congestion during peak (evening) times :/

Z :)
 
@zertop

Thanks for the tool, here are the details:


Zertop's LineTool Results
Date/Time: Wed Dec 16 14:57:29 SAST 2015


Basic Report:


Your packet loss was 3%.
Your average ping was 97ms.
Your maximum ping was 189ms.

You seem to have some packet loss. This indicates an issue on the line.
Looking at your average ping, there is definitely something wrong with your line! Please post the results (at the end of the program) into the forum for advice!

Detailed Report:
Code:
PING 169.0.49.1 (169.0.49.1) 56(84) bytes of data.
64 bytes from 169.0.49.1: icmp_seq=1 ttl=254 time=68.4 ms
64 bytes from 169.0.49.1: icmp_seq=2 ttl=254 time=74.9 ms
64 bytes from 169.0.49.1: icmp_seq=3 ttl=254 time=127 ms
64 bytes from 169.0.49.1: icmp_seq=4 ttl=254 time=90.2 ms
64 bytes from 169.0.49.1: icmp_seq=5 ttl=254 time=61.2 ms
64 bytes from 169.0.49.1: icmp_seq=6 ttl=254 time=84.7 ms
64 bytes from 169.0.49.1: icmp_seq=7 ttl=254 time=105 ms
64 bytes from 169.0.49.1: icmp_seq=8 ttl=254 time=81.7 ms
64 bytes from 169.0.49.1: icmp_seq=9 ttl=254 time=96.3 ms
64 bytes from 169.0.49.1: icmp_seq=10 ttl=254 time=89.1 ms
64 bytes from 169.0.49.1: icmp_seq=11 ttl=254 time=105 ms
64 bytes from 169.0.49.1: icmp_seq=12 ttl=254 time=136 ms
64 bytes from 169.0.49.1: icmp_seq=13 ttl=254 time=109 ms
64 bytes from 169.0.49.1: icmp_seq=14 ttl=254 time=109 ms
64 bytes from 169.0.49.1: icmp_seq=15 ttl=254 time=83.5 ms
64 bytes from 169.0.49.1: icmp_seq=16 ttl=254 time=104 ms
64 bytes from 169.0.49.1: icmp_seq=17 ttl=254 time=102 ms
64 bytes from 169.0.49.1: icmp_seq=18 ttl=254 time=84.9 ms
64 bytes from 169.0.49.1: icmp_seq=19 ttl=254 time=81.1 ms
64 bytes from 169.0.49.1: icmp_seq=20 ttl=254 time=57.8 ms
64 bytes from 169.0.49.1: icmp_seq=21 ttl=254 time=79.5 ms
64 bytes from 169.0.49.1: icmp_seq=22 ttl=254 time=69.5 ms
64 bytes from 169.0.49.1: icmp_seq=24 ttl=254 time=98.6 ms
64 bytes from 169.0.49.1: icmp_seq=25 ttl=254 time=82.0 ms
64 bytes from 169.0.49.1: icmp_seq=26 ttl=254 time=145 ms
64 bytes from 169.0.49.1: icmp_seq=27 ttl=254 time=189 ms
64 bytes from 169.0.49.1: icmp_seq=28 ttl=254 time=83.6 ms
64 bytes from 169.0.49.1: icmp_seq=29 ttl=254 time=124 ms
64 bytes from 169.0.49.1: icmp_seq=30 ttl=254 time=114 ms

--- 169.0.49.1 ping statistics ---
30 packets transmitted, 29 received, 3% packet loss, time 29341ms
rtt min/avg/max/mdev = 57.830/97.996/189.911/27.321 ms

Hope this can be fixed, can't go on like this.
 
My ping was averaging 250ms today and I called the call centre. Spoke with one of your agents, i won't mention his name, and he helped me as much as he could by recreating my port, checking for errors etc. but referred me to Telkom to recreate the port from their side and check for errors.

Called them and they found that even though my connection was showing fine, good attenuation etc i was getting quite a few disconnects at the exchange directly, they logged a fault and now I wait for them to fix it.

Thanks to your call centre staff for all the help.
 
Hi, Anybody has a clue what might be happening here? I normally get 8.4Mbps download speed on my 10Meg Line. Today I all of a sudden I get 9.7Mbps on each and every speedtest.

4920457629.png

Untitled.jpg
 
Last edited:
Hi, Anybody has a clue what might be happening here? I normally get 8.4Mbps download speed on my 10Meg Line. Today I all of a sudden I get 9.7Mbps on each and every speedtest.

View attachment 324661

View attachment 324663

Your line may be Sync'd at 12Mbps. Telkom's system started doing this and changed the mode from fast path to interleaved.

The disadvantage is that it adds ~20-25ms to your trip (quite significant actually). If you do not do anything that requires lower latency (e.g. online gaming) then go ahead and stay on interleave.
 
Getting ISP authentication and nothing else at the moment:
View attachment 324713

Anyone else experiencing similar?
There was an outage in Century City at 4pm. Telkom's apparently doing a software upgrade here following on the heels of an exchange equipment upgrade last Tuesday (8/12). Might be similar in your area. The consequence is that whatever they've done has messed up International throughput. Local is fine. International (for me) is a complete mess. Have a Telkom tech looking at this. At the moment they're confused. The upgrade was apparently to enable impending Fibre rollout in Milnerton. Telkom guy said they'd moved to different hardware. Wasn't able to get more info than this. If anyone knows the jargon let me know and I'll quiz the guy.
 
Slow Browsing Speeds / Low Ping

There was an outage in Century City at 4pm. Telkom's apparently doing a software upgrade here following on the heels of an exchange equipment upgrade last Tuesday (8/12). Might be similar in your area. The consequence is that whatever they've done has messed up International throughput. Local is fine. International (for me) is a complete mess. Have a Telkom tech looking at this. At the moment they're confused. The upgrade was apparently to enable impending Fibre rollout in Milnerton. Telkom guy said they'd moved to different hardware. Wasn't able to get more info than this. If anyone knows the jargon let me know and I'll quiz the guy.

It seems that the problem is also in Kraaifontein (Cape Town Northern Suburbs), as i am only getting a download speed of 290kbps and an upload of 350kbps, as well as a ping result of 292ms.

someone broke something....
speedtest.png
 
@zertop

Thanks for the tool, here are the details:


Zertop's LineTool Results
Date/Time: Wed Dec 16 14:57:29 SAST 2015


Basic Report:


Your packet loss was 3%.
Your average ping was 97ms.
Your maximum ping was 189ms.

You seem to have some packet loss. This indicates an issue on the line.
Looking at your average ping, there is definitely something wrong with your line! Please post the results (at the end of the program) into the forum for advice!

Detailed Report:
Code:
PING 169.0.49.1 (169.0.49.1) 56(84) bytes of data.
64 bytes from 169.0.49.1: icmp_seq=1 ttl=254 time=68.4 ms
64 bytes from 169.0.49.1: icmp_seq=2 ttl=254 time=74.9 ms
64 bytes from 169.0.49.1: icmp_seq=3 ttl=254 time=127 ms
64 bytes from 169.0.49.1: icmp_seq=4 ttl=254 time=90.2 ms
64 bytes from 169.0.49.1: icmp_seq=5 ttl=254 time=61.2 ms
64 bytes from 169.0.49.1: icmp_seq=6 ttl=254 time=84.7 ms
64 bytes from 169.0.49.1: icmp_seq=7 ttl=254 time=105 ms
64 bytes from 169.0.49.1: icmp_seq=8 ttl=254 time=81.7 ms
64 bytes from 169.0.49.1: icmp_seq=9 ttl=254 time=96.3 ms
64 bytes from 169.0.49.1: icmp_seq=10 ttl=254 time=89.1 ms
64 bytes from 169.0.49.1: icmp_seq=11 ttl=254 time=105 ms
64 bytes from 169.0.49.1: icmp_seq=12 ttl=254 time=136 ms
64 bytes from 169.0.49.1: icmp_seq=13 ttl=254 time=109 ms
64 bytes from 169.0.49.1: icmp_seq=14 ttl=254 time=109 ms
64 bytes from 169.0.49.1: icmp_seq=15 ttl=254 time=83.5 ms
64 bytes from 169.0.49.1: icmp_seq=16 ttl=254 time=104 ms
64 bytes from 169.0.49.1: icmp_seq=17 ttl=254 time=102 ms
64 bytes from 169.0.49.1: icmp_seq=18 ttl=254 time=84.9 ms
64 bytes from 169.0.49.1: icmp_seq=19 ttl=254 time=81.1 ms
64 bytes from 169.0.49.1: icmp_seq=20 ttl=254 time=57.8 ms
64 bytes from 169.0.49.1: icmp_seq=21 ttl=254 time=79.5 ms
64 bytes from 169.0.49.1: icmp_seq=22 ttl=254 time=69.5 ms
64 bytes from 169.0.49.1: icmp_seq=24 ttl=254 time=98.6 ms
64 bytes from 169.0.49.1: icmp_seq=25 ttl=254 time=82.0 ms
64 bytes from 169.0.49.1: icmp_seq=26 ttl=254 time=145 ms
64 bytes from 169.0.49.1: icmp_seq=27 ttl=254 time=189 ms
64 bytes from 169.0.49.1: icmp_seq=28 ttl=254 time=83.6 ms
64 bytes from 169.0.49.1: icmp_seq=29 ttl=254 time=124 ms
64 bytes from 169.0.49.1: icmp_seq=30 ttl=254 time=114 ms

--- 169.0.49.1 ping statistics ---
30 packets transmitted, 29 received, 3% packet loss, time 29341ms
rtt min/avg/max/mdev = 57.830/97.996/189.911/27.321 ms

Hope this can be fixed, can't go on like this.

You'd definitely need to get telkom to have a look at your exchange! That does not look great...

169.x.x.x is on the AH network, however it is the hop just off the telkom network, so it usually indicates the same thing :)

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