Forum Discussion

SightCyan's avatar
SightCyan
New Contributor
2 years ago

Packet Loss

Experiencing significant and regular packet loss. Chat support suggested the best course of action was to pay a tech $75 to come out and confirm that an issue existed at all. I'm hoping the folks here can do better.

This has been an ongoing issue for me for several months, and I'd like to find some sort of way to fix this.

Three PingPlotter samples below. Discord, Valorant, and Google, with associated WinMTR results.

Discord

|------------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

|                             192.168.0.1 -    0 |  109 |  109 |    0 |    1 |   14 |    2 |

|                              10.71.84.1 -   10 |   77 |   70 |    7 |   11 |   22 |   10 |

|                         100.120.105.194 -   11 |   76 |   68 |    8 |   11 |   31 |   31 |

|                          100.120.104.12 -    8 |   81 |   75 |    8 |   14 |   43 |   10 |

|            langbprj01-ae1.rd.la.cox.net -    8 |   81 |   75 |   10 |   16 |   56 |   27 |

|                       hosted-by.i3d.net -   10 |   77 |   70 |    9 |   17 |   43 |   12 |

|                            66.22.226.20 -    8 |   81 |   75 |   10 |   15 |   39 |   13 |

|________________________________________________|______|______|______|______|______|______|

   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

VALORANT

|------------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

|                             192.168.0.1 -    0 |   70 |   70 |    0 |    1 |    4 |    1 |

|                              10.71.84.1 -    8 |   55 |   51 |    6 |   11 |   35 |   11 |

|                         100.120.105.194 -    6 |   59 |   56 |    8 |   13 |   39 |   13 |

|                          100.120.104.12 -    6 |   59 |   56 |    6 |   12 |   44 |    9 |

|            langbprj01-ae1.rd.la.cox.net -   10 |   51 |   46 |    0 |   12 |   30 |   13 |

|                           100.122.208.7 -   83 |   17 |    3 |    0 |   17 |   31 |   10 |

|                             98.187.76.3 -    6 |   59 |   56 |    8 |   14 |   40 |   11 |

|                   No response from host -  100 |   15 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   15 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   15 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   15 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   15 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   15 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   15 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   15 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   15 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   15 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   15 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   15 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   15 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   15 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   15 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   15 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   15 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   15 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   15 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   15 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   15 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   15 |    0 |    0 |    0 |    0 |    0 |

|                   No response from host -  100 |   15 |    0 |    0 |    0 |    0 |    0 |

|________________________________________________|______|______|______|______|______|______|

   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

bad service
packet loss

4 Replies

Sort By
  • JonathanJ's avatar
    JonathanJ
    Former Moderator
    2 years ago
    @SightCyan

    I completely understand the hassle of having packet loss. Depending on the root cause of the issue, there may be a $75 charge associated with the visit. If the issue is due to Cox equipment or signal delivery from outside, this fee will be waived. We would be happy to see if there is any packet loss from our end and if needed schedule a tech visit. Please email us your full name and complete address to cox.help@cox.com. Also include a link to this thread,


    Jonathan J
    Cox Moderator

  • Darkatt's avatar
    Darkatt
    Valued Contributor III
    2 years ago

    There are many reasons for pkt loss, and while one of the upstream channels is a bit out of spec, there may be more to the issue. A tech onsite is the best solution. The Cox Complete Care, is kinda like insurance. It's good to have when you need it, but you always hope you don't need it. It covers the cost of a tech out, IF the issue is something that would be billable. The line inside your home, from the demarcation point outside to your modem, is what would be billable if that's where the problem is. If the problem is your modem, again, billable, and CCC would keep you from having to fork over 75$. If the issue is delivery of the service UP to the demarc, that's Cox's responsibility, and they won't charge for repairs if it's on their side. 

    I hope that takes out some of the mystery.

    • JonathanJ's avatar
      JonathanJ
      Former Moderator
      2 years ago
      @WiderMouthOpen

      I apologize for sending a link that didn't work. Thanks for correcting that for me WiderMouthOpen.


      Jonathan J
      Cox Moderator