Forum Discussion

RgnCajun27's avatar
RgnCajun27
New Contributor

South Louisiana - Bad lag and packet loss in the evening

Hi I'm in the New Iberia area and for the past few weeks my connection has been really poor at night. I'm using a Wired Ethernet  Connection and I've having really bad lag in online games and others have told me that my VOIP output has been distorted.

This only seems to start between 7-8 pm at night and persist throughout the night.

A person on cox online chat told me to replace my modem; I did that and it did not help.

I've also tried:

Power Cycling, Connecting directly to Modem, Changing Ethernet Cable, Checking Drivers, Checking Firewall Settings

Nothing seems to work and I'm pretty sure the problem isn't on my end.

While my neighborhood was not effected by the recent flooding down here, I'm wondering if it could have damaged something down the line.

I hope someone here can give me some info

Thanks

connection issues

13 Replies

Sort By
Most LikedOldestNewest
Replies have been turned off for this discussion
  • RgnCajun27's avatar
    RgnCajun27
    New Contributor

    Here's a traceroute from last night when the issue was occuring.

    Tracing route to 199.108.62.157 over a maximum of 30 hops

      0  DESKTOP-T17STUU [192.168.1.81]
      1  router.asus.com [192.168.1.1]
      2  10.30.136.1
      3  184.189.159.132
      4  ip24-249-36-18.br.br.cox.net [24.249.36.18]
      5  ip24-249-36-18.br.br.cox.net [24.249.36.18]
      6  dalsbprj02-ae2.0.rd.dl.cox.net [68.1.2.121]
      7  xe-5-1-0.edge5.Dallas3.Level3.net [4.59.32.93]
      8     *        *        *     
    Computing statistics for 175 seconds...
                Source to Here   This Node/Link
    Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
      0                                           DESKTOP-T17STUU [192.168.1.81]
                                    0/ 100 =  0%   |
      1    0ms     0/ 100 =  0%     0/ 100 =  0%  router.asus.com [192.168.1.1]
                                    8/ 100 =  8%   |
      2    8ms    11/ 100 = 11%     3/ 100 =  3%  10.30.136.1
                                    0/ 100 =  0%   |
      3    9ms    12/ 100 = 12%     4/ 100 =  4%  184.189.159.132
                                    0/ 100 =  0%   |
      4   13ms    13/ 100 = 13%     5/ 100 =  5%  ip24-249-36-18.br.br.cox.net [24.249.36.18]
                                    0/ 100 =  0%   |
      5   14ms     8/ 100 =  8%     0/ 100 =  0%  ip24-249-36-18.br.br.cox.net [24.249.36.18]
                                    1/ 100 =  1%   |
      6  ---     100/ 100 =100%    91/ 100 = 91%  dalsbprj02-ae2.0.rd.dl.cox.net [68.1.2.121]
                                    0/ 100 =  0%   |
      7   25ms     9/ 100 =  9%     0/ 100 =  0%  xe-5-1-0.edge5.Dallas3.Level3.net [4.59.32.93]

    Trace complete.


    And here's one from an hour ago when everything was fine.

    Tracing route to 199.108.62.157 over a maximum of 30 hops

      0  DESKTOP-T17STUU [192.168.1.81]
      1  router.asus.com [192.168.1.1]
      2  10.30.136.1
      3  184.189.159.132
      4  ip24-249-36-18.br.br.cox.net [24.249.36.18]
      5  ip24-249-36-18.br.br.cox.net [24.249.36.18]
      6  dalsbprj02-ae2.0.rd.dl.cox.net [68.1.2.121]
      7  xe-5-1-0.edge5.Dallas3.Level3.net [4.59.32.93]
      8     *        *        *     
    Computing statistics for 175 seconds...
                Source to Here   This Node/Link
    Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
      0                                           DESKTOP-T17STUU [192.168.1.81]
                                    0/ 100 =  0%   |
      1    0ms     0/ 100 =  0%     0/ 100 =  0%  router.asus.com [192.168.1.1]
                                    0/ 100 =  0%   |
      2    7ms     0/ 100 =  0%     0/ 100 =  0%  10.30.136.1
                                    0/ 100 =  0%   |
      3    8ms     0/ 100 =  0%     0/ 100 =  0%  184.189.159.132
                                    0/ 100 =  0%   |
      4   11ms     0/ 100 =  0%     0/ 100 =  0%  ip24-249-36-18.br.br.cox.net [24.249.36.18]
                                    0/ 100 =  0%   |
      5   12ms     0/ 100 =  0%     0/ 100 =  0%  ip24-249-36-18.br.br.cox.net [24.249.36.18]
                                    0/ 100 =  0%   |
      6  ---     100/ 100 =100%   100/ 100 =100%  dalsbprj02-ae2.0.rd.dl.cox.net [68.1.2.121]
                                    0/ 100 =  0%   |
      7   23ms     0/ 100 =  0%     0/ 100 =  0%  xe-5-1-0.edge5.Dallas3.Level3.net [4.59.32.93]

    Trace complete.

    As you can see the packet loss is really bad in primetime

  • RgnCajun27's avatar
    RgnCajun27
    New Contributor

    Still having this issue, starts between 7-8 like clockwork.

  • ChrisL's avatar
    ChrisL
    Former Moderator
    @RgnCajun27

    I'm definitely seeing packet loss to the modem when I look from this end. Are there any cable splitters you can try bypassing to see if that helps?

  • RgnCajun27's avatar
    RgnCajun27
    New Contributor

    no cablesplitter, it goes straight to the modem. also, as I said, it only seems to happen at night so I don't think it's on my end

  • ChrisL's avatar
    ChrisL
    Former Moderator
    @RgnCajun27

    Looking from this end I'm not convinced this is a nighttime event only. I checked this morning and saw the packet loss. It may be time to see about having a technician come out and troubleshoot further.

  • RgnCajun27's avatar
    RgnCajun27
    New Contributor

    I will call tonight and schedule a tech if I still have the problem.

    I only notice it in the evenings with gaming. Sometime between 7-8 every night I can watch my ping in WoW or Overwatch start to climb and then horrible lag sets in. Prior to this everything is fine pings in the 50s and no lag.

  • RgnCajun27's avatar
    RgnCajun27
    New Contributor

    I have a tech coming out tomorrow but I'm not sure they will notice anything.

    Here's a new pathping I just did on my lunch break.


    Tracing route to 199.108.62.157 over a maximum of 30 hops

      0  DESKTOP-T17STUU [192.168.1.81]
      1  router.asus.com [192.168.1.1]
      2  10.30.136.1
      3  184.189.159.132
      4  ip24-249-36-18.br.br.cox.net [24.249.36.18]
      5  ip24-249-36-18.br.br.cox.net [24.249.36.18]
      6  dalsbprj02-ae2.0.rd.dl.cox.net [68.1.2.121]
      7  xe-5-1-0.edge5.Dallas3.Level3.net [4.59.32.93]
      8     *        *     ae-2-3615.ear2.Chicago2.Level3.net [4.69.148.254]
      9  192.205.37.149
     10  cr1.cgcil.ip.att.net [12.122.133.162]
     11  12.123.251.17
     12     *        *        *     
    Computing statistics for 275 seconds...
                Source to Here   This Node/Link
    Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
      0                                           DESKTOP-T17STUU [192.168.1.81]
                                    0/ 100 =  0%   |
      1    0ms     0/ 100 =  0%     0/ 100 =  0%  router.asus.com [192.168.1.1]
                                    0/ 100 =  0%   |
      2    7ms     0/ 100 =  0%     0/ 100 =  0%  10.30.136.1
                                    0/ 100 =  0%   |
      3    8ms     0/ 100 =  0%     0/ 100 =  0%  184.189.159.132
                                    0/ 100 =  0%   |
      4   12ms     0/ 100 =  0%     0/ 100 =  0%  ip24-249-36-18.br.br.cox.net [24.249.36.18]
                                    0/ 100 =  0%   |
      5   11ms     0/ 100 =  0%     0/ 100 =  0%  ip24-249-36-18.br.br.cox.net [24.249.36.18]
                                    0/ 100 =  0%   |
      6   22ms     0/ 100 =  0%     0/ 100 =  0%  dalsbprj02-ae2.0.rd.dl.cox.net [68.1.2.121]
                                    0/ 100 =  0%   |
      7   23ms     0/ 100 =  0%     0/ 100 =  0%  xe-5-1-0.edge5.Dallas3.Level3.net [4.59.32.93]
                                    0/ 100 =  0%   |
      8   41ms     0/ 100 =  0%     0/ 100 =  0%  ae-2-3615.ear2.Chicago2.Level3.net [4.69.148.254]
                                    0/ 100 =  0%   |
      9   45ms     0/ 100 =  0%     0/ 100 =  0%  192.205.37.149
                                  100/ 100 =100%   |
     10  ---     100/ 100 =100%     0/ 100 =  0%  cr1.cgcil.ip.att.net [12.122.133.162]
                                    0/ 100 =  0%   |
     11  ---     100/ 100 =100%     0/ 100 =  0%  12.123.251.17

    Trace complete.

    No packet loss at 11:15 am

  • ChrisL's avatar
    ChrisL
    Former Moderator
    @RgnCajun27

    Intermittent issues can be difficult to isolate. What I'm seeing from this end is packet loss at the modem suggesting a signal or equipment problem.

  • RgnCajun27's avatar
    RgnCajun27
    New Contributor

    The tech came and found a splitter outside the house. He bypassed that.

    Once again everything was fine until about 30 minutes ago, 7:30 Central, but now I'm having high pings and lag.