Community Forum

Bad Packet Loss Causing Interrupted Connection

New Poster

Bad Packet Loss Causing Interrupted Connection

Hello,

 

I moved into a new apartment this week, and I'm experiencing some fairly signifgant packet loss. Unfortunately the representative I spoke to wasn't too sure of the issue and I have a tech coming out tomorrow to look at my wiring/connectors.

 

Out of curiosity I was looking to get a second opinion here since you folks seem very helpful.

 

When I run a ping on my modem (ping -n 20 10.0.0.1) I drop zero packets. I'm hardwired into my modem.

 

However,  when I ping something like the google public DNS (ping -n 20 8.8.8.8) I experience between 5% and 30% packet loss. (copied below) No matter what time of day this happens to me.

 

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=25ms TTL=53
Reply from 8.8.8.8: bytes=32 time=23ms TTL=53
Reply from 8.8.8.8: bytes=32 time=21ms TTL=53
Request timed out.
Reply from 8.8.8.8: bytes=32 time=25ms TTL=53
Reply from 8.8.8.8: bytes=32 time=23ms TTL=53
Reply from 8.8.8.8: bytes=32 time=28ms TTL=53
Reply from 8.8.8.8: bytes=32 time=20ms TTL=53
Request timed out.
Reply from 8.8.8.8: bytes=32 time=24ms TTL=53
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=979ms TTL=53
Reply from 8.8.8.8: bytes=32 time=22ms TTL=53
Request timed out.
Reply from 8.8.8.8: bytes=32 time=24ms TTL=53
Reply from 8.8.8.8: bytes=32 time=25ms TTL=53
Reply from 8.8.8.8: bytes=32 time=20ms TTL=53
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=23ms TTL=53
Request timed out.
Reply from 8.8.8.8: bytes=32 time=52ms TTL=53
Request timed out.
Reply from 8.8.8.8: bytes=32 time=25ms TTL=53
Reply from 8.8.8.8: bytes=32 time=23ms TTL=53
Reply from 8.8.8.8: bytes=32 time=68ms TTL=53
Reply from 8.8.8.8: bytes=32 time=21ms TTL=53
Reply from 8.8.8.8: bytes=32 time=22ms TTL=53
Reply from 8.8.8.8: bytes=32 time=75ms TTL=53
Reply from 8.8.8.8: bytes=32 time=28ms TTL=53
Reply from 8.8.8.8: bytes=32 time=20ms TTL=53
Reply from 8.8.8.8: bytes=32 time=82ms TTL=53
Request timed out.
Reply from 8.8.8.8: bytes=32 time=109ms TTL=53
Reply from 8.8.8.8: bytes=32 time=25ms TTL=53
Reply from 8.8.8.8: bytes=32 time=20ms TTL=53
Reply from 8.8.8.8: bytes=32 time=21ms TTL=53
Reply from 8.8.8.8: bytes=32 time=20ms TTL=53
Request timed out.
Reply from 8.8.8.8: bytes=32 time=23ms TTL=53
Reply from 8.8.8.8: bytes=32 time=25ms TTL=53
Reply from 8.8.8.8: bytes=32 time=21ms TTL=53
Reply from 8.8.8.8: bytes=32 time=21ms TTL=53
Reply from 8.8.8.8: bytes=32 time=22ms TTL=53
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=27ms TTL=53

Ping statistics for 8.8.8.8:
Packets: Sent = 50, Received = 35, Lost = 15 (30% loss
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 979ms, Average = 58ms

 

 

Here are my modems current power levels as signal to noise ratios: Does the upstream power level on index 3 look high? I've read that between 35 and 49 is optimal. Is there anyway to bring it inline with the other 3?

 

https://imgur.com/a/hHyEgxJ

Capture.PNG

 

Any idea what could be going on?

 

I do some gaming from time to time, and the packet loss is very noticable in those situations. I would hate to have to switch ISPs because of this issue.