Forum Discussion

skyler's avatar
skyler
New Contributor
7 years ago

recentpacket loss issues every evening

I've noticed a service degradation over the last couple of nights. It is really noticeable when online gaming.  

After running continuous pings to cox.com and google.com, there seems to be a pretty consistant intermitent packet loss problem.

Running a few tracerts to cox.com reveals the following...

C:\Users\skyle>tracert cox.com

Tracing route to cox.com [45.60.45.167]
over a maximum of 30 hops:

1 3 ms 1 ms 1 ms 192.168.0.1
2 9 ms 8 ms 8 ms 10.36.112.1
3 8 ms 11 ms 9 ms 100.127.73.156
4 30 ms 9 ms 18 ms 100.120.100.6
5 * * 14 ms lag-103.bear2.Phoenix1.Level3.net [4.14.52.225]
6 * * * Request timed out.
7 20 ms 23 ms 22 ms 4.7.26.34
8 24 ms 22 ms 54 ms 45.60.45.167

Trace complete.

C:\Users\skyle>tracert cox.com

Tracing route to cox.com [45.60.45.167]
over a maximum of 30 hops:

1 8 ms 3 ms 1 ms 192.168.0.1
2 8 ms 9 ms 7 ms 10.36.112.1
3 11 ms 12 ms 14 ms 100.127.73.156
4 89 ms 40 ms 29 ms 100.120.100.6
5 10 ms 11 ms 11 ms lag-103.bear2.Phoenix1.Level3.net [4.14.52.225]
6 * * * Request timed out.
7 19 ms 19 ms 21 ms 4.7.26.34
8 21 ms 24 ms 22 ms 45.60.45.167

Trace complete.

C:\Users\skyle>tracert cox.com

Tracing route to cox.com [45.60.45.167]
over a maximum of 30 hops:

1 5 ms 5 ms 1 ms 192.168.0.1
2 12 ms 13 ms 16 ms 10.36.112.1
3 17 ms 14 ms 29 ms 100.127.73.156
4 12 ms 12 ms 9 ms 100.120.100.6
5 8 ms 9 ms 11 ms lag-103.bear2.Phoenix1.Level3.net [4.14.52.225]
6 * 20 ms 19 ms ae-1-3512.ear4.LosAngeles1.Level3.net [4.69.211.210]
7 119 ms 42 ms 21 ms 4.7.26.34
8 25 ms 55 ms 26 ms 45.60.45.167

and one to google.com

C:\Users\skyle>tracert google.com

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

1 3 ms 1 ms 1 ms 192.168.0.1
2 7 ms 10 ms 22 ms 10.36.112.1
3 10 ms 12 ms 12 ms 100.127.73.156
4 11 ms 11 ms 9 ms 100.120.100.6
5 38 ms 22 ms 24 ms 68.1.4.252
6 * 54 ms * 72.215.224.173
7 * * * Request timed out.
8 90 ms 104 ms 63 ms 72.14.239.120
9 51 ms 47 ms 155 ms 108.170.247.244
10 486 ms 56 ms 136 ms 108.170.230.121
11 38 ms 48 ms 50 ms 108.170.230.126
12 36 ms 32 ms 21 ms 108.170.247.161
13 37 ms 37 ms 36 ms 108.170.225.69
14 37 ms 35 ms 37 ms lax28s15-in-f14.1e100.net [172.217.11.174]

Trace complete.

I understand that this is the internet and a lot of people are responsible for keeping it up and working, I would just appreciate my service being restored to an enjoyable experience. 

bad service
coxsupport
packet loss
  • TrenchfootGamin's avatar
    TrenchfootGamin
    New Contributor
    7 years ago

    I've had the same issues for months and finally got fed up enough to do something tonight.  I downloaded Pingplotter,  https://www.pingplotter.com/download/ plugged in my games server IP and found this: Screenshot

    Packet loss from 50 to 90 percent.  Both of those servers are owned by "level 3 llc"  bought by Century Link recently.  I called Level 3 and was informed that since Cox was the customer in this instance, Cox would have to start a support ticket with them.  I called Cox back, shared that same screenshot with a tier 2 support rep and he is supposed to be forwarding it to engineers that can take a look and get it sorted out. 

    • ChrisL's avatar
      ChrisL
      Former Moderator
      7 years ago
      @TrenchfoodGaming

      Looking at your results I don't believe Level3 to be an issue. See http://bit.ly/2xxVEqI for more information on how ICMP de-prioritization works. I am concerned however that you're showing packet loss at the 1st hop which is usuall your home router. I'd suggest trying again connected directly to the modem and see if your results change.

      -Chris
      • 402PrimeTime's avatar
        402PrimeTime
        New Contributor III
        7 years ago

        PingPlotter always shows PL at the router. Have many screenshots to prove this out with multiple routers. 

    • qly227's avatar
      qly227
      New Contributor
      7 years ago

      I am having the same problem.  But my trace routes are fluctuating between level3 and getting this:

      Tracing route to cox.net [45.60.106.167]
      over a maximum of 30 hops:

      1 8 ms 4 ms 9 ms [192.168.2.1]
      2 3 ms 4 ms 4 ms  [192.168.1.1]
      3 15 ms 11 ms 12 ms 10.128.64.1
      4 12 ms 14 ms 13 ms 100.127.74.138
      5 12 ms 12 ms 13 ms 100.120.100.22
      6 58 ms 56 ms 56 ms chgobprj01-ae0.0.rd.ch.cox.net [68.1.4.42]
      7 57 ms 64 ms 74 ms bx4-chicagodt_tengige0-13-0-0 [184.150.181.134]
      8 126 ms 124 ms 118 ms tcore4-chicagocp_bundle-ether1.net.bell.ca [64.230.79.74]
      9 120 ms 121 ms 119 ms tcore4-toronto12_hundredgige1-2-0-0.net.bell.ca [64.230.79.156]
      10 126 ms 126 ms 125 ms tcore4-vancouver_hundredgige0-1-0-0.net.bell.ca [64.230.79.67]
      11 120 ms 119 ms 118 ms dis17-vancouver_7-0-0.net.bell.ca [64.230.123.251]
      12 120 ms 118 ms 122 ms 67.69.211.102
      13 120 ms 118 ms 118 ms 45.60.106.167

      Trace complete.

      • qly227's avatar
        qly227
        New Contributor
        7 years ago

        seems like there's some weird routing issues.

  • Tikerz's avatar
    Tikerz
    New Contributor II
    7 years ago

    I have the same problem.  Loss to lag-103.bear2.Phoenix1.Level3.net and ae-1-51.ear1.LosAngeles6.Level3.net.