I know its not shaped, as my TI account same results. But technitian left so will check again tonight
Generally speaking, once any noise that's on the line is cleared up (and it's causing the fault) it clears up the DSL stability.
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
I know its not shaped, as my TI account same results. But technitian left so will check again tonight
AfriGuy, I am at home now and logged onto my AH account. Everything seems normal...
Awesome
Keep me posted on how things go!!
Don't get me wrong, it is awesome, but what could have caused it? I started happening intermittently last week and then yesterday was a complete ballsup. Couldn't do anything for like an hour - until I switched to the AW account...![]()
Shoot me a PM with your DSL username and I can take a look through the logs to see what's caused this.
Dont say that.. AfriGuy will think it meansYGPM
Getting some high latency on teamspeak.
Any test results you can post here?
Tracing route to mybroadband.co.za [104.20.72.110]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 95 ms * * jhb-up7.ip.adsl.co.za [169.1.5.6]
4 25 ms 24 ms 26 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
5 81 ms 76 ms 79 ms eoh-ns.ixp.joburg [196.46.25.157]
6 26 ms 24 ms 24 ms 41-66-181-63-3f.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.63]
7 24 ms * 26 ms 104.20.72.110
mybb
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 <1 ms 1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 95 ms 101 ms * jhb-up7.ip.adsl.co.za [169.1.5.6]
4 24 ms 24 ms 25 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
5 30 ms 26 ms 24 ms 169-1-5-243.ip.afrihost.co.za [169.1.5.243]
6 25 ms 24 ms 38 ms 72.14.239.35
7 27 ms 26 ms 95 ms google-public-dns-a.google.com [8.8.8.8]
Google DNS
Not seeing any reported latency on monitoring - what's your ping to bras.afrihost.com like?
Tracing route to 197-80-200-53.jhb.mweb.co.za [197.80.200.53] -Game
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 78 ms 78 ms 75 ms jhb-up7.ip.adsl.co.za [169.1.5.6]
4 28 ms 26 ms 29 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
5 26 ms 25 ms 25 ms mweb.ixp.joburg [196.46.25.145]
6 42 ms 25 ms 26 ms 197-80-7-79.jhb.mweb.co.za [197.80.7.79]
7 29 ms 26 ms 27 ms bu-ether3.mca-pe-1.optinet.net [197.80.4.37]
8 91 ms 136 ms 138 ms 197-80-96-30.jhb.mweb.co.za [197.80.96.30]
9 25 ms 26 ms 50 ms 197-80-200-53.jhb.mweb.co.za [197.80.200.53]
Trace complete.
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Ping statistics for 155.239.255.250:
Packets: Sent = 27, Received = 27, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 34ms, Average = 24ms
Control-C
Looks OK from there.
What happens when you ping 169.1.5.6?
Pinging 169.1.5.6 with 32 bytes of data:
Reply from 169.1.5.6: bytes=32 time=89ms TTL=59
Reply from 169.1.5.6: bytes=32 time=70ms TTL=59
Reply from 169.1.5.6: bytes=32 time=57ms TTL=59
Reply from 169.1.5.6: bytes=32 time=96ms TTL=59
Ping statistics for 169.1.5.6:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 57ms, Maximum = 96ms, Average = 78ms
the f is going on
-snip
Nope... The trace says otherwise, but i cant quite figure this out. While those results seem normal i get thisHas your Telkom fault been resolved?