Forum Discussion

Skeazy's avatar
Skeazy
New Contributor

Packet loss and connection drop - Only after 6pm

Greetings,

For about two months now I've experienced signficiant packet loss and occasional disconnects, but it only ever happens after around 6PM. I can send 500 pings and get every response back earlier in the day, but every single night it starts to drop(Averaging about 2-5packets per 200 pings)

This happens on my desktop, which is hardwired, as well as my XBox One, Laptop and Mobile devices over WiFi(2.4 and 5ghz)
I've bought a new modem/router(Nighthawk C7000) which did not fix the issue. I have no splitters in any of my lines inside the house.

I tried connecting my modem downstairs to a different coax line(which comes in completely seperate after the Cox Box outside, so I know there are no splitters somewhere in the house) and had the same issues.

When it happens, all my devices can ping to the router and each other flawlessly. As soon as you ping outside it starts dropping.

Call center support was unable to help, although did note an odd inability to connect to the router(even though it was online at the time.)

A tech came out today, but as it was in the morning, when everything was working fine, he naturally couldn't find anything wrong. All the lines from the junction box as well as in my house were good.

Here is a shot of my connection.

http://imgur.com/a/FOqEW This is with a 6db attenuator. Without the attenuator my power levels range from +0-10dBmV

The only thing I've been told so far is to try and schedule another tech to come out during their latest slot(5-7PM) so they can troubleshoot it while it happens.

 

connection
packetloss evening

10 Replies

Sort By
Most LikedOldestNewest
Replies have been turned off for this discussion
  • kburns10's avatar
    kburns10
    New Contributor
    I'm having the same issue. Around 8-9 pm like clockwork my internet slows to a crawl. I get great speeds during the day, but at night, it starts acting up. I've had techs come out, but unfortunately, no one is available to come out that late.
  • ChrisL's avatar
    ChrisL
    Former Moderator
    @Skeazy

    Looking from this end I don't see anything with the modem or the connection to it that suggests a problem. Can you try a wired connection and see if that is any better? Also can you try to get some trace routes that show the loss so we may take a look and see where the loss could be originating from?

  • Skeazy's avatar
    Skeazy
    New Contributor

    As stated in my post my desktop is wired and it happens on that, as well as my wifi devices. I will run some traceroutes. The reason you didn't see anything wrong is because you did it around noon, when there are no problems. It only happens in the evening and at night.

  • Skeazy's avatar
    Skeazy
    New Contributor

    Here are tracert results to various DNS. During this time(8:30PM) I was getting about 2-5 packets lost over 100 pings.

    http://pastebin.com/S8qUaTup

    I was still getting packet loss before, between, and during these tracerts, however.

  • ChrisL's avatar
    ChrisL
    Former Moderator
    @kburns10

    From this end all looks well with the modem. Could you try testing without the router and see if it's still slow?

  • ChrisL's avatar
    ChrisL
    Former Moderator
    @Skeazy

    I won't be able to access a pastebin from my location. Can you post the results here?

  • Skeazy's avatar
    Skeazy
    New Contributor

    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 9 ms 7 ms 8 ms 10.1.160.1
    3 9 ms 12 ms 7 ms 100.127.40.188
    4 9 ms 8 ms 7 ms 172.22.51.66
    5 13 ms 13 ms 17 ms ashbbprj01-ae2.rd.as.cox.net [68.1.0.242]
    6 14 ms 13 ms 13 ms 68.105.30.118
    7 75 ms 13 ms 16 ms 216.58.215.34
    8 18 ms 13 ms 15 ms 209.85.251.163
    9 21 ms 21 ms 22 ms 216.239.48.160
    10 34 ms 20 ms 22 ms 216.239.49.77
    11 * * * Request timed out.
    12 21 ms 21 ms 20 ms google-public-dns-a.google.com [8.8.8.8]

    Trace complete.
    Tracing route to star-mini.c10r.facebook.com [31.13.69.228]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.0.1
    2 8 ms * * 10.1.160.1
    3 8 ms 8 ms 10 ms 100.127.40.188
    4 8 ms 7 ms 10 ms 172.22.51.66
    5 13 ms 13 ms 13 ms ashbbprj02-ae2.0.rd.as.cox.net [68.1.4.139]
    6 21 ms 21 ms 14 ms ip70-167-150-14.at.at.cox.net [70.167.150.14]
    7 14 ms 15 ms 17 ms po102.psw01b.iad3.tfbnw.net [31.13.27.247]
    8 20 ms 14 ms 13 ms 173.252.67.79
    9 18 ms 12 ms 13 ms edge-star-mini-shv-01-iad3.facebook.com [31.13.69.228]

    Trace complete.
    Tracing route to www.wikipedia.org [208.80.154.224]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.0.1
    2 9 ms 6 ms 7 ms 10.1.160.1
    3 9 ms 7 ms 9 ms 100.127.41.124
    4 9 ms 8 ms 7 ms 172.22.51.96
    5 14 ms 13 ms 12 ms ashbbprj01-ae2.rd.as.cox.net [68.1.0.242]
    6 14 ms 14 ms 13 ms eqix-dc2.wikimedia.org [206.126.236.221]
    7 14 ms 15 ms 15 ms text-lb.eqiad.wikimedia.org [208.80.154.224]

    Trace complete.
    Tracing route to prod.reddit.map.fastlylb.net [151.101.33.140]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.0.1
    2 8 ms 7 ms 7 ms 10.1.160.1
    3 8 ms 7 ms 8 ms 100.127.40.188
    4 8 ms 7 ms 8 ms 172.22.51.66
    5 14 ms 14 ms 17 ms ashbbprj02-ae2.0.rd.as.cox.net [68.1.4.139]
    6 13 ms 16 ms 13 ms 199.27.73.34
    7 * * * Request timed out.
    8 13 ms 13 ms 12 ms 151.101.33.140

    Trace complete.

  • ChrisL's avatar
    ChrisL
    Former Moderator
    @Sleazy

    Thanks for sharing. So far all of those results look to be in order. We can tell there's no loss as how the hops after the ones of obvious concern do not show the same loss. If the issue is time sensitive it may be necessary to try this again when the problem is occurring.

  • Skeazy's avatar
    Skeazy
    New Contributor

    Chlis,

    I performed all the traceroutes while I was experiencing the packet loss. I know it's bizarre to be getting packet loss on pings but not on traceroutes. I did about a dozen traceroutes back to back and they all came back fine. 

  • ChrisL's avatar
    ChrisL
    Former Moderator
    @Skeazy

    If finding the loss via a trace route is proving difficult another tool called pingplotter may be helpful.