Forum Discussion

MtnDew's avatar
MtnDew
New Contributor
6 years ago

Packet loss

Hello,

I have recently been noticing some screen freezing while watching youtube vidios or playing online games. The video or game would freeze for a couple of seconds then all of a sudden catch up (for lack of a better term). I have checked my computer out and run diagnostics on it and performed modem tests (I have no router) and found the computer and modem in good shape.

 

I have ran multiple traceroutes and pathpings and consistently find packet losses along the path such as the ones below which are not the worst I have seen in my testing for the last few weeks. If you need more let me know. There is nothing I know of that I can do to fix this since all the packet losses happen away from my computer and modem. If there is more information needed or if I need to contact anyone please let me know.

 

Microsoft Windows [Version 10.0.17134.228]

(c) 2018 Microsoft Corporation. All rights reserved.

 

C:\Users\XXXXX>pathping google.com

 

Tracing route to google.com [172.217.4.174]

over a maximum of 30 hops:

  0  DESKTOP-U78SEJO [192.168.0.2]

  1  10.33.40.1

  2  100.127.77.8

  3  100.120.100.36

  4  68.1.4.252

  5  72.215.224.173

  6     *        *        *

Computing statistics for 125 seconds...

            Source to Here   This Node/Link

Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address

  0                                           DESKTOP-U78SEJO [192.168.0.2]

                                3/ 100 =  3%   |

  1    8ms     3/ 100 =  3%     0/ 100 =  0%  10.33.40.1

                                0/ 100 =  0%   |

  2    9ms     3/ 100 =  3%     0/ 100 =  0%  100.127.77.8

                                0/ 100 =  0%   |

  3   15ms     3/ 100 =  3%     0/ 100 =  0%  100.120.100.36

                               97/ 100 = 97%   |

  4  ---     100/ 100 =100%     0/ 100 =  0%  68.1.4.252

                                0/ 100 =  0%   |

  5  ---     100/ 100 =100%     0/ 100 =  0%  72.215.224.173

 

Trace complete.

 

C:\Users\XXXXX>pathping google.com

 

Tracing route to google.com [172.217.5.78]

over a maximum of 30 hops:

  0  DESKTOP-U78SEJO [192.168.0.2]

  1  10.33.40.1

  2  100.127.77.10

  3  100.120.100.40

  4  langbprj02-ae1.0.rd.la.cox.net [68.1.1.14]

  5  72.14.196.240

  6  108.170.247.193

  7  108.170.237.113

  8  lax17s15-in-f14.1e100.net [172.217.5.78]

 

Computing statistics for 200 seconds...

            Source to Here   This Node/Link

Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address

  0                                           DESKTOP-U78SEJO [192.168.0.2]

                                0/ 100 =  0%   |

  1    9ms     0/ 100 =  0%     0/ 100 =  0%  10.33.40.1

                                0/ 100 =  0%   |

  2    9ms     0/ 100 =  0%     0/ 100 =  0%  100.127.77.10

                                0/ 100 =  0%   |

  3   13ms     0/ 100 =  0%     0/ 100 =  0%  100.120.100.40

                                0/ 100 =  0%   |

  4   24ms     0/ 100 =  0%     0/ 100 =  0%  langbprj02-ae1.0.rd.la.cox.net [68.1.1.14]

                                6/ 100 =  6%   |

  5  ---     100/ 100 =100%    94/ 100 = 94%  72.14.196.240

                                0/ 100 =  0%   |

  6   39ms     6/ 100 =  6%     0/ 100 =  0%  108.170.247.193

                                0/ 100 =  0%   |

  7  ---     100/ 100 =100%    94/ 100 = 94%  108.170.237.113

                                0/ 100 =  0%   |

  8   39ms     6/ 100 =  6%     0/ 100 =  0%  lax17s15-in-f14.1e100.net [172.217.5.78]

 

Trace complete.

5 Replies

Replies have been turned off for this discussion
  • Hi MtnDew, thank you for providing pathping data. The 3% packet loss at Hop 0 is concerning. Have you scheduled a service call or tested a different device since this packet loss began? -Becky, Cox Support Forums Moderator
  • MtnDew's avatar
    MtnDew
    New Contributor

    No I have not scheduled a service call.

    I am more concerned about the 100% packet losses

    C:\Users\jaspe>pathping cox.net
    Tracing route to cox.net [45.60.106.167]
    over a maximum of 30 hops:
      0  DESKTOP-U78SEJO [192.168.0.2]
      1  10.33.40.1
      2  100.127.77.10
      3  100.120.100.40
      4  chgobprj01-ae0.0.rd.ch.cox.net [68.1.4.42]
      5  bx4-chicagodt_tengige0-13-0-0 [184.150.181.134]
      6  tcore4-chicagocp_bundle-ether1.net.bell.ca [64.230.79.74]
      7  tcore4-toronto47_hundredgige1-2-0-0.net.bell.ca [64.230.79.158]
      8  tcore4-vancouver_hundredgige0-9-0-0.net.bell.ca [64.230.79.71]
      9  dis17-vancouver_7-0-0.net.bell.ca [64.230.123.251]
     10  67.69.211.102
     11  45.60.106.167
    Computing statistics for 275 seconds...
                Source to Here   This Node/Link
    Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
      0                                           DESKTOP-U78SEJO [192.168.0.2]
                                    1/ 100 =  1%   |
      1    8ms     1/ 100 =  1%     0/ 100 =  0%  10.33.40.1
                                    0/ 100 =  0%   |
      2    9ms     1/ 100 =  1%     0/ 100 =  0%  100.127.77.10
                                    0/ 100 =  0%   |
      3   12ms     1/ 100 =  1%     0/ 100 =  0%  100.120.100.40
                                    0/ 100 =  0%   |
      4   57ms     1/ 100 =  1%     0/ 100 =  0%  chgobprj01-ae0.0.rd.ch.cox.net [68.1.4.42]
                                    0/ 100 =  0%   |
      5   57ms     1/ 100 =  1%     0/ 100 =  0%  bx4-chicagodt_tengige0-13-0-0 [184.150.181.134]
                                    0/ 100 =  0%   |
      6  ---     100/ 100 =100%    99/ 100 = 99%  tcore4-chicagocp_bundle-ether1.net.bell.ca [64.230.79.74]
                                    0/ 100 =  0%   |
      7  ---     100/ 100 =100%    99/ 100 = 99%  tcore4-toronto47_hundredgige1-2-0-0.net.bell.ca [64.230.79.158]
                                    0/ 100 =  0%   |
      8  ---     100/ 100 =100%    99/ 100 = 99%  tcore4-vancouver_hundredgige0-9-0-0.net.bell.ca [64.230.79.71]
                                    0/ 100 =  0%   |
      9  ---     100/ 100 =100%    99/ 100 = 99%  dis17-vancouver_7-0-0.net.bell.ca [64.230.123.251]
                                    0/ 100 =  0%   |
     10  115ms     2/ 100 =  2%     1/ 100 =  1%  67.69.211.102
                                    0/ 100 =  0%   |
     11  116ms     1/ 100 =  1%     0/ 100 =  0%  45.60.106.167
    Trace complete.

    Microsoft Windows [Version 10.0.17134.228]

    (c) 2018 Microsoft Corporation. All rights reserved.

     

    C:\Users\XXXXX>pathping 137.221.105.2

     

    Tracing route to 137.221.105.2 over a maximum of 30 hops

     

      0  DESKTOP-U78SEJO [192.168.0.2]

      1  10.33.40.1

      2  100.127.77.10

      3  100.120.100.40

      4  68.1.4.252

      5  70.191.61.10

      6  ae1-br01-eqla1.as57976.net [137.221.68.33]

      7  et-0-0-2-br01-swlv10.as57976.net [137.221.65.69]

      8  et-0-0-31-pe02-swlv10.as57976.net [137.221.83.69]

      9  las-swlv10-ia-bons-04.as57976.net [137.221.66.23]

     10  137.221.105.2

     

    Computing statistics for 250 seconds...

                Source to Here   This Node/Link

    Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address

      0                                           DESKTOP-U78SEJO [192.168.0.2]

                                    0/ 100 =  0%   |

      1    8ms     0/ 100 =  0%     0/ 100 =  0%  10.33.40.1

                                    0/ 100 =  0%   |

      2    9ms     0/ 100 =  0%     0/ 100 =  0%  100.127.77.10

                                    0/ 100 =  0%   |

      3   11ms     0/ 100 =  0%     0/ 100 =  0%  100.120.100.40

                                    0/ 100 =  0%   |

      4   24ms     0/ 100 =  0%     0/ 100 =  0%  68.1.4.252

                                    0/ 100 =  0%   |

      5  ---     100/ 100 =100%   100/ 100 =100%  70.191.61.10

                                    0/ 100 =  0%   |

      6   24ms     0/ 100 =  0%     0/ 100 =  0%  ae1-br01-eqla1.as57976.net [137.221.68.33]

                                    0/ 100 =  0%   |

      7   30ms     0/ 100 =  0%     0/ 100 =  0%  et-0-0-2-br01-swlv10.as57976.net [137.221.65.69]

                                    0/ 100 =  0%   |

      8   27ms     0/ 100 =  0%     0/ 100 =  0%  et-0-0-31-pe02-swlv10.as57976.net [137.221.83.69]

                                    0/ 100 =  0%   |

      9  ---     100/ 100 =100%   100/ 100 =100%  las-swlv10-ia-bons-04.as57976.net [137.221.66.23]

                                    0/ 100 =  0%   |

     10   27ms     0/ 100 =  0%     0/ 100 =  0%  137.221.105.2

     

    Trace complete.

    ----------------------------------------------------------------------------------------------

    C:\Users\XXXXX>pathping 24.105.129 -q 10

     

    Tracing route to 24.105.0.129 over a maximum of 30 hops

     

      0  DESKTOP-U78SEJO [192.168.0.2]

      1  10.33.40.1

      2  100.127.77.8

      3  100.120.100.36

      4  68.1.4.252

      5  70.191.61.10

      6  ae1-br01-eqla1.as57976.net [137.221.68.33]

      7  be1-pe02-eqla1.as57976.net [137.221.68.69]

      8  lax-eqla1-ia-bons-03.as57976.net [137.221.66.5]

      9  24.105.30.147

     10     *        *        *

    Computing statistics for 22 seconds...

                Source to Here   This Node/Link

    Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address

      0                                           DESKTOP-U78SEJO [192.168.0.2]

                                    0/  10 =  0%   |

      1    8ms     0/  10 =  0%     0/  10 =  0%  10.33.40.1

                                    0/  10 =  0%   |

      2    8ms     0/  10 =  0%     0/  10 =  0%  100.127.77.8

                                    0/  10 =  0%   |

      3   13ms     0/  10 =  0%     0/  10 =  0%  100.120.100.36

                                    0/  10 =  0%   |

      4   24ms     0/  10 =  0%     0/  10 =  0%  68.1.4.252

                                    0/  10 =  0%   |

      5  ---      10/  10 =100%    10/  10 =100%  70.191.61.10

                                    0/  10 =  0%   |

      6   22ms     0/  10 =  0%     0/  10 =  0%  ae1-br01-eqla1.as57976.net [137.221.68.33]

                                    0/  10 =  0%   |

      7   23ms     0/  10 =  0%     0/  10 =  0%  be1-pe02-eqla1.as57976.net [137.221.68.69]

                                   10/  10 =100%   |

      8  ---      10/  10 =100%     0/  10 =  0%  lax-eqla1-ia-bons-03.as57976.net [137.221.66.5]

                                    0/  10 =  0%   |

      9  ---      10/  10 =100%     0/  10 =  0%  24.105.30.147

     

    Trace complete.

    ----------------------------------------------------------------------------------------------

    C:\Users\XXXXX>pathping 24.105.129 -q 150

     

    Tracing route to 24.105.0.129 over a maximum of 30 hops

     

      0  DESKTOP-U78SEJO [192.168.0.2]

      1  10.33.40.1

      2  100.127.77.8

      3  100.120.100.36

      4  68.1.4.252

      5  70.191.61.10

      6  ae1-br01-eqla1.as57976.net [137.221.68.33]

      7  be1-pe02-eqla1.as57976.net [137.221.68.69]

      8  lax-eqla1-ia-bons-03.as57976.net [137.221.66.5]

      9  24.105.30.147

     10     *        *        *

    Computing statistics for 337 seconds...

                Source to Here   This Node/Link

    Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address

      0                                           DESKTOP-U78SEJO [192.168.0.2]

                                    0/ 150 =  0%   |

      1    7ms     0/ 150 =  0%     0/ 150 =  0%  10.33.40.1

                                    0/ 150 =  0%   |

      2    8ms     0/ 150 =  0%     0/ 150 =  0%  100.127.77.8

                                    0/ 150 =  0%   |

      3   13ms     0/ 150 =  0%     0/ 150 =  0%  100.120.100.36

                                    0/ 150 =  0%   |

      4   25ms     0/ 150 =  0%     0/ 150 =  0%  68.1.4.252

                                    0/ 150 =  0%   |

      5  ---     150/ 150 =100%   150/ 150 =100%  70.191.61.10

                                    0/ 150 =  0%   |

      6   23ms     0/ 150 =  0%     0/ 150 =  0%  ae1-br01-eqla1.as57976.net [137.221.68.33]

                                    0/ 150 =  0%   |

      7   23ms     0/ 150 =  0%     0/ 150 =  0%  be1-pe02-eqla1.as57976.net [137.221.68.69]

                                  150/ 150 =100%   |

      8  ---     150/ 150 =100%     0/ 150 =  0%  lax-eqla1-ia-bons-03.as57976.net [137.221.66.5]

                                    0/ 150 =  0%   |

      9  ---     150/ 150 =100%     0/ 150 =  0%  24.105.30.147

     

    Trace complete.

    ------------------------------------------------------------------------------------------------

    Microsoft Windows [Version 10.0.17134.228]

    (c) 2018 Microsoft Corporation. All rights reserved.

     

    C:\Users\XXXXX>pathping 137.221.105.2

     

    Tracing route to 137.221.105.2 over a maximum of 30 hops

     

      0  DESKTOP-U78SEJO [192.168.0.2]

      1  10.33.40.1

      2  100.127.77.10

      3  100.120.100.40

      4  68.1.4.252

      5  70.191.61.10

      6  ae1-br01-eqla1.as57976.net [137.221.68.33]

      7  et-0-0-2-br01-swlv10.as57976.net [137.221.65.69]

      8  et-0-0-31-pe02-swlv10.as57976.net [137.221.83.69]

      9  las-swlv10-ia-bons-04.as57976.net [137.221.66.23]

     10  137.221.105.2

     

    Computing statistics for 250 seconds...

                Source to Here   This Node/Link

    Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address

      0                                           DESKTOP-U78SEJO [192.168.0.2]

                                    2/ 100 =  2%   |

      1    7ms     2/ 100 =  2%     0/ 100 =  0%  10.33.40.1

                                    0/ 100 =  0%   |

      2    8ms     2/ 100 =  2%     0/ 100 =  0%  100.127.77.10

                                    0/ 100 =  0%   |

      3   11ms     2/ 100 =  2%     0/ 100 =  0%  100.120.100.40

                                    0/ 100 =  0%   |

      4   24ms     2/ 100 =  2%     0/ 100 =  0%  68.1.4.252

                                    0/ 100 =  0%   |

      5  ---     100/ 100 =100%    98/ 100 = 98%  70.191.61.10

                                    0/ 100 =  0%   |

      6   25ms     2/ 100 =  2%     0/ 100 =  0%  ae1-br01-eqla1.as57976.net [137.221.68.33]

                                    1/ 100 =  1%   |

      7   30ms     3/ 100 =  3%     0/ 100 =  0%  et-0-0-2-br01-swlv10.as57976.net [137.221.65.69]

                                    1/ 100 =  1%   |

      8   26ms     4/ 100 =  4%     0/ 100 =  0%  et-0-0-31-pe02-swlv10.as57976.net [137.221.83.69]

                                    0/ 100 =  0%   |

      9  ---     100/ 100 =100%    96/ 100 = 96%  las-swlv10-ia-bons-04.as57976.net [137.221.66.23]

                                    0/ 100 =  0%   |

     10   27ms     4/ 100 =  4%     0/ 100 =  0%  137.221.105.2

     

    Trace complete.

    ----------------------------------------------------------------------------------------------

    C:\Users\XXXXX>pathping 24.105.62.129

     

    Tracing route to 24.105.62.129 over a maximum of 30 hops

     

      0  DESKTOP-U78SEJO [192.168.0.2]

      1  10.33.40.1

      2  100.127.77.10

      3  100.120.100.40

      4  68.1.4.252

      5  70.191.61.10

      6  ae1-br02-eqla1.as57976.net [137.221.68.35]

      7  et-0-0-3-br02-eqch2.as57976.net [137.221.65.5]

      8  be2-pe01-eqch2.as57976.net [137.221.69.71]

      9  chi-eqch2-ia-bons-02.as57976.net [137.221.66.11]

     10  24.105.62.129

     

    Computing statistics for 250 seconds...

                Source to Here   This Node/Link

    Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address

      0                                           DESKTOP-U78SEJO [192.168.0.2]

                                    2/ 100 =  2%   |

      1    7ms     4/ 100 =  4%     2/ 100 =  2%  10.33.40.1

                                    0/ 100 =  0%   |

      2    9ms     3/ 100 =  3%     1/ 100 =  1%  100.127.77.10

                                    0/ 100 =  0%   |

      3   11ms     3/ 100 =  3%     1/ 100 =  1%  100.120.100.40

                                    0/ 100 =  0%   |

      4   24ms     2/ 100 =  2%     0/ 100 =  0%  68.1.4.252

                                    0/ 100 =  0%   |

      5  ---     100/ 100 =100%    98/ 100 = 98%  70.191.61.10

                                    0/ 100 =  0%   |

      6   28ms     2/ 100 =  2%     0/ 100 =  0%  ae1-br02-eqla1.as57976.net [137.221.68.35]

                                    0/ 100 =  0%   |

      7   65ms     2/ 100 =  2%     0/ 100 =  0%  et-0-0-3-br02-eqch2.as57976.net [137.221.65.5]

                                    1/ 100 =  1%   |

      8   72ms     3/ 100 =  3%     0/ 100 =  0%  be2-pe01-eqch2.as57976.net [137.221.69.71]

                                    1/ 100 =  1%   |

      9  ---     100/ 100 =100%    96/ 100 = 96%  chi-eqch2-ia-bons-02.as57976.net [137.221.66.11]

                                    0/ 100 =  0%   |

     10   80ms     4/ 100 =  4%     0/ 100 =  0%  24.105.62.129

     

    Trace complete.

    I also have a lot more if you want them.

  • MtnDew's avatar
    MtnDew
    New Contributor

    No I have not scheduled anything. I tried showing some additional pathpings where there is 0 packet loss at hop 0 with 100% packet loss farther down the line but apparently that was considered spamming or abuse.

    I have plenty more if you want to see them.

    • Becky's avatar
      Becky
      Moderator
      Hi MtnDew, keep in mind that the only hop that matters is the final destination. If the final hop is showing 0% packet loss and acceptable latency, then all the hops before that can show all kinds of errors and it doesn't matter. Some servers (and some routers) may specifically block or down-prioritize ICMP echo requests. These routers might show 100% packet loss, or high packet loss and latency. If the destination isn't affected, all other latency and packet loss is an artifact of router configuration (or other device configuration), and there is no problem. -Becky, Cox Support Forums Moderator
    • Cox_User_Who_Ne's avatar
      Cox_User_Who_Ne
      Contributor

      No point in calling in a technician, Cox is "Fixing" this issue for the past year, and calling a technician will just end up in you getting a one day fix, and then back to normal. Oh yah, plus the bill.