Who do I ask for help? This looks like a line quality or node issue. Please help.
modem: SB5101 (still compatible.)
12Mb service
wireless router: not the issue.
Unless I state otherwise, I am pinging the first hop outside of the service address.
And by the way, this behavior is the same as what I am seeing at work on Comcast Business class with a rented modem.
I have been seeing random lost packets. All year.
I have been seeing ping times rise into the 400s or even 800s. Less common lately, but all year.
Lately I am seeing often seconds at a time of signal loss. Enough to stop me from playing games. (so many now require constant connection.)
Reply from 50.151.184.1: bytes=32 time=48ms TTL=63
Reply from 50.151.184.1: bytes=32 time=51ms TTL=63
Reply from 50.151.184.1: bytes=32 time=25ms TTL=63
Reply from 50.151.184.1: bytes=32 time=109ms TTL=63
Reply from 50.151.184.1: bytes=32 time=443ms TTL=63
Reply from 50.151.184.1: bytes=32 time=33ms TTL=63
Reply from 50.151.184.1: bytes=32 time=13ms TTL=63
Reply from 50.151.184.1: bytes=32 time=598ms TTL=63
Reply from 50.151.184.1: bytes=32 time=1049ms TTL=63
Reply from 50.151.184.1: bytes=32 time=125ms TTL=63
Reply from 50.151.184.1: bytes=32 time=13ms TTL=63
Reply from 50.151.184.1: bytes=32 time=10ms TTL=63
Reply from 50.151.184.1: bytes=32 time=10ms TTL=63
This is getting to be really common : just randomly, whenever.
Reply from 50.151.184.1: bytes=32 time=14ms TTL=63
Reply from 50.151.184.1: bytes=32 time=23ms TTL=63
Reply from 50.151.184.1: bytes=32 time=24ms TTL=63
Reply from 50.151.184.1: bytes=32 time=1554ms TTL=63
Reply from 50.151.184.1: bytes=32 time=52ms TTL=63
Reply from 50.151.184.1: bytes=32 time=22ms TTL=63
Reply from 50.151.184.1: bytes=32 time=18ms TTL=63
Reply from 50.151.184.1: bytes=32 time=13ms TTL=63
Reply from 50.151.184.1: bytes=32 time=35ms TTL=63
Reply from 50.151.184.1: bytes=32 time=13ms TTL=63
Reply from 50.151.184.1: bytes=32 time=23ms TTL=63
Reply from 50.151.184.1: bytes=32 time=49ms TTL=63
Reply from 50.151.184.1: bytes=32 time=13ms TTL=63
Reply from 50.151.184.1: bytes=32 time=14ms TTL=63
Reply from 50.151.184.1: bytes=32 time=178ms TTL=63
Reply from 50.151.184.1: bytes=32 time=247ms TTL=63
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.117: Destination host unreachable.
Reply from 192.168.1.117: Destination host unreachable.
Reply from 192.168.1.117: Destination host unreachable.
Reply from 192.168.1.117: Destination host unreachable.
Reply from 192.168.1.117: Destination host unreachable.
Reply from 192.168.1.117: Destination host unreachable.
Reply from 192.168.1.117: Destination host unreachable.
Reply from 192.168.1.117: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.117: Destination host unreachable.
Request timed out.
Request timed out.
Reply from 192.168.1.117: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 50.151.184.1: bytes=32 time=22ms TTL=63
Reply from 50.151.184.1: bytes=32 time=92ms TTL=63
Reply from 50.151.184.1: bytes=32 time=15ms TTL=63
Reply from 50.151.184.1: bytes=32 time=32ms TTL=63
Reply from 50.151.184.1: bytes=32 time=12ms TTL=63
Reply from 50.151.184.1: bytes=32 time=17ms TTL=63
Reply from 50.151.184.1: bytes=32 time=16ms TTL=63
Reply from 50.151.184.1: bytes=32 time=12ms TTL=63
Reply from 50.151.184.1: bytes=32 time=21ms TTL=63
Reply from 50.151.184.1: bytes=32 time=202ms TTL=63
Reply from 50.151.184.1: bytes=32 time=24ms TTL=63
Reply from 50.151.184.1: bytes=32 time=11ms TTL=63
I spent 18 months or so fighting to fix a line that turned out to be a squirrel chew. This doesn't look the same. This looks like the service just stops routing on occasion.