Forum Discussion

jameslance's avatar
jameslance
New Contributor II
6 years ago

Packet Loss and Modem Resets

Hello, I am experiencing really bad packet loss and modem resets during normal business hours (e.g. 8am - 4pm). Internet works, but drops every few minutes. I've had two techs out. The first repl...
packet loss
ChrisL's avatar
ChrisL
Former Moderator
6 years ago
@jameslance

When I look from this end I'm not seeing anything that would indicate connection trouble. Do you have any trace routes showing the packet loss you're seeing?

-Chris
  • jameslance's avatar
    jameslance
    New Contributor II
    6 years ago

    Chris, thank you for checking. It is an intermittant problem. It has been fine for the last few days, but is awful at the moment. 

    If I ping google.com, it looks like this:

    Request timed out.
    Request timed out.
    Reply from 172.217.0.46: bytes=32 time=87ms TTL=252
    Reply from 172.217.0.46: bytes=32 time=49ms TTL=252
    Reply from 172.217.0.46: bytes=32 time=30ms TTL=252
    Reply from 172.217.0.46: bytes=32 time=61ms TTL=252
    Reply from 172.217.0.46: bytes=32 time=53ms TTL=252
    Reply from 172.217.0.46: bytes=32 time=85ms TTL=252
    Reply from 172.217.0.46: bytes=32 time=29ms TTL=252
    Reply from 172.217.0.46: bytes=32 time=794ms TTL=252
    Reply from 172.217.0.46: bytes=32 time=47ms TTL=252
    Reply from 172.217.0.46: bytes=32 time=143ms TTL=252
    Request timed out.
    Request timed out.
    Reply from 172.217.0.46: bytes=32 time=65ms TTL=252
    Reply from 172.217.0.46: bytes=32 time=148ms TTL=252
    Request timed out.
    Request timed out.
    Reply from 172.217.0.46: bytes=32 time=113ms TTL=252
    Reply from 172.217.0.46: bytes=32 time=116ms TTL=252
    Reply from 172.217.0.46: bytes=32 time=35ms TTL=252
    Reply from 172.217.0.46: bytes=32 time=63ms TTL=252
    Reply from 172.217.0.46: bytes=32 time=152ms TTL=252
    Reply from 172.217.0.46: bytes=32 time=92ms TTL=252
    Reply from 172.217.0.46: bytes=32 time=125ms TTL=252
    Request timed out.
    Reply from 172.217.0.46: bytes=32 time=90ms TTL=252
    Reply from 172.217.0.46: bytes=32 time=92ms TTL=252
    Reply from 172.217.0.46: bytes=32 time=28ms TTL=252

  • jameslance's avatar
    jameslance
    New Contributor II
    6 years ago

    And heres a trace route:

    C:\Users\jlanc>tracert google.com

    Tracing route to google.com [108.177.122.100]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.0.1
    2 10 ms 9 ms 12 ms 10.113.124.1
    3 27 ms 11 ms 13 ms 100.127.73.32
    4 * * * Request timed out.
    5 1419 ms 160 ms 89 ms langbprj02-ae1.0.rd.la.cox.net [68.1.1.14]
    6 52 ms 68 ms 82 ms 72.215.224.175
    7 * * * Request timed out.
    8 85 ms 103 ms 42 ms 74.125.252.74
    9 * 38 ms 40 ms 108.170.247.148
    10 22 ms 23 ms 21 ms 108.170.234.38
    11 254 ms * * 209.85.251.128
    12 134 ms 129 ms 131 ms 209.85.240.17
    13 83 ms * 91 ms 108.170.230.67
    14 77 ms 83 ms 90 ms 108.170.232.167
    15 * * * Request timed out.
    16 * * * Request timed out.
    17 * * * Request timed out.
    18 * * * Request timed out.
    19 * * * Request timed out.
    20 * ip68-228-203-63.ph.ph.cox.net [68.228.203.63] reports: Destination host unreachable.

    Trace complete.