Line Issues - How Do I Get the Best Help

A

ASR

Active Member
Joined
Jan 14, 2011
Messages
52
Reaction score
4
My line is from Telkom - the tool says I may have an issue with line performance. Generally suffer slow downloads speeds after 20:00 almost daily. Log a call with Telkom? What do I ask them to fix?

Zertop's "Is it my Line" Results
Date/Time: Fri Jul 03 22:54:45 GMT+02:00 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 83ms.
Your maximum ping was 299ms.

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: 
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=25ms TTL=64
Reply from 192.168.1.1: bytes=32 time=23ms TTL=64
Reply from 192.168.1.1: bytes=32 time=19ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=299ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=231ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=288ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=247ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=286ms TTL=64
Reply from 192.168.1.1: bytes=32 time=192ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=216ms TTL=64
Reply from 192.168.1.1: bytes=32 time=137ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=267ms TTL=64
Reply from 192.168.1.1: bytes=32 time=172ms TTL=64
Reply from 192.168.1.1: bytes=32 time=78ms TTL=64

Ping statistics for 192.168.1.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 299ms, Average = 83ms
 
Sounds like dslam congestion, nothing you can do about it.
 
ASR said:
My line is from Telkom - the tool says I may have an issue with line performance. Generally suffer slow downloads speeds after 20:00 almost daily. Log a call with Telkom? What do I ask them to fix?

Zertop's "Is it my Line" Results
Date/Time: Fri Jul 03 22:54:45 GMT+02:00 2015

Basic Report:

Your packet loss was 0%.
Your average ping was 83ms.
Your maximum ping was 299ms.

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: 
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=25ms TTL=64
Reply from 192.168.1.1: bytes=32 time=23ms TTL=64
Reply from 192.168.1.1: bytes=32 time=19ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=299ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=231ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=288ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=247ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=286ms TTL=64
Reply from 192.168.1.1: bytes=32 time=192ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=216ms TTL=64
Reply from 192.168.1.1: bytes=32 time=137ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=267ms TTL=64
Reply from 192.168.1.1: bytes=32 time=172ms TTL=64
Reply from 192.168.1.1: bytes=32 time=78ms TTL=64

Ping statistics for 192.168.1.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 299ms, Average = 83ms
Click to expand...

Why are you pinging your router?

Well since you gave crappy ping results to your router, you found the problem already. It's not your telkom line. It's your ethernet line or router causing this.
 
Ok firstly let's address your issue. You are pinging your gateway, which isn't even leaving your house so the issue is between you're client (computer) and the modem/router (gateway). I'm assuming you use Wireless from the tests, this correct?


Ok now let's fix it. Try connecting to the router via cable and do the test again. Does it improve?
No?
Your r00ter is f00ked
Yes?
Great, FAR easier to fix. You either have some bad interference going on by either a Microwave or similar near the router or somewhere around there. So go into the same room as the router and connect via WiFi and test again. Better or worse?
Better?
Great, now you know. Stay close to the router or fix the interference issue.
Worse?
Eish............ either r00ter f00ked or the interference is coming from inside that room(bad movie pun...)



ponder said:
Sounds like dslam congestion, nothing you can do about it.
Click to expand...
My guy, did you bother to read the report?
 
ajan said:
Why are you pinging your router?

Well since you gave crappy ping results to your router, you found the problem already. It's not your telkom line. It's your ethernet line or router causing this.
Click to expand...

MVP
 
Thanks for the feedback. I did not realise I was pinging the router. I just used the "Is it my Line" tool. Downloaded and hit run...assumed it would ping Telkom dslam (it said it was pinging "telkom equipment").

Yes - indeed using Wifi. However, not sure why the results are this bad. Dual band AC router (Asus DSL-AC68U) is sitting 50 cms from laptop (on the same desk) with cordless phone and microwave in separate/other rooms. So really hard to make sense of interference. Will try ethernet cable and see.

Also, this drop in wifi performance happens regularly in the evenings around 20:00-21:00..so assumed it was line related
 
Today - tested wifi and ethernet. Perfect and identical performance on both (downloads 19 Mbps, 8ms latency, 2Mbps uploads. No issues - let's see what happens tonight again...
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X