Targ100's profile

New Contributor

 • 

3 Messages

Closed

Path Ping issues

Currently everything works fine, except playing Diablo 3. I get lag playing that for seemingly no reason. I pathping The diablo server and it seems a Cox server in Atlanta is losing 90-100% of packets. Ive path pinged 6 times so far at different times and this one server always loses more than 90%. Contacting support did nothing as they dont seem to understand what I am referring to. Ill Post a couple pathpings here for (hopefully) someone intelligent in the cox employee group to forward to whoever is near the problem IP and sort it out.

The problem is:   6  ---     100/ 100 =100%    91/ 100 = 91%  chndbbrc01-pos0202.rd.ph.cox.net [68.1.0.242]

-PathPing2-


Tracing route to 12.129.209.68 over a maximum of 30 hops

  0  Korey-PC [192.168.1.100]
  1  192.168.1.1
  2  10.12.248.1
  3  172.22.60.230
  4  172.22.60.230
  5  68.10.8.225
  6  chndbbrc01-pos0202.rd.ph.cox.net [68.1.0.242]
  7     *     xe-11-2-2.edge2.Washington4.Level3.net [4.53.114.97]
  8     *        *        *     
Computing statistics for 175 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Korey-PC [192.168.1.100]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1
                                2/ 100 =  2%   |
  2    9ms     3/ 100 =  3%     1/ 100 =  1%  10.12.248.1
                                0/ 100 =  0%   |
  3   11ms     8/ 100 =  8%     6/ 100 =  6%  172.22.60.230
                                0/ 100 =  0%   |
  4   12ms     5/ 100 =  5%     3/ 100 =  3%  172.22.60.230
                                0/ 100 =  0%   |
  5   12ms     4/ 100 =  4%     2/ 100 =  2%  68.10.8.225
                                0/ 100 =  0%   |
  6  ---     100/ 100 =100%    98/ 100 = 98%  chndbbrc01-pos0202.rd.ph.cox.net [68.1.0.242]
                                0/ 100 =  0%   |
  7   20ms     2/ 100 =  2%     0/ 100 =  0%  xe-11-2-2.edge2.Washington4.Level3.net [4.53.114.97]

Trace complete.

-PathPing3-

Tracing route to 12.129.209.68 over a maximum of 30 hops

  0  Korey-PC [192.168.1.100]
  1  192.168.1.1
  2  10.12.248.1
  3  172.22.60.230
  4  172.22.60.230
  5  68.10.8.225
  6  chndbbrc01-pos0202.rd.ph.cox.net [68.1.0.242]
  7  xe-11-2-2.edge2.Washington4.Level3.net [4.53.114.97]
  8     *        *        *     
Computing statistics for 175 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Korey-PC [192.168.1.100]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1
                                0/ 100 =  0%   |
  2    8ms     0/ 100 =  0%     0/ 100 =  0%  10.12.248.1
                                0/ 100 =  0%   |
  3    9ms     0/ 100 =  0%     0/ 100 =  0%  172.22.60.230
                                0/ 100 =  0%   |
  4   10ms     0/ 100 =  0%     0/ 100 =  0%  172.22.60.230
                                0/ 100 =  0%   |
  5   10ms     0/ 100 =  0%     0/ 100 =  0%  68.10.8.225
                                0/ 100 =  0%   |
  6  ---     100/ 100 =100%   100/ 100 =100%  chndbbrc01-pos0202.rd.ph.cox.net [68.1.0.242]
                                0/ 100 =  0%   |
  7   18ms     0/ 100 =  0%     0/ 100 =  0%  xe-11-2-2.edge2.Washington4.Level3.net [4.53.114.97]

Trace complete.

-PathPing6-


Tracing route to 12.129.209.68 over a maximum of 30 hops

  0  Korey-PC [192.168.1.100]
  1  192.168.1.1
  2  10.12.248.1
  3  172.22.60.230
  4  172.22.60.230
  5  68.10.8.225
  6  chndbbrc01-pos0202.rd.ph.cox.net [68.1.0.242]
  7  xe-11-2-2.edge2.Washington4.Level3.net [4.53.114.97]
  8     *        *        *     
Computing statistics for 175 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Korey-PC [192.168.1.100]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1
                                3/ 100 =  3%   |
  2    9ms     3/ 100 =  3%     0/ 100 =  0%  10.12.248.1
                                0/ 100 =  0%   |
  3   10ms     3/ 100 =  3%     0/ 100 =  0%  172.22.60.230
                                5/ 100 =  5%   |
  4   11ms     8/ 100 =  8%     0/ 100 =  0%  172.22.60.230
                                1/ 100 =  1%   |
  5   10ms     9/ 100 =  9%     0/ 100 =  0%  68.10.8.225
                                0/ 100 =  0%   |
  6  ---     100/ 100 =100%    91/ 100 = 91%  chndbbrc01-pos0202.rd.ph.cox.net [68.1.0.242]
                                0/ 100 =  0%   |
  7   19ms     9/ 100 =  9%     0/ 100 =  0%  xe-11-2-2.edge2.Washington4.Level3.net [4.53.114.97]

Trace complete.

Former Moderator

 • 

7.1K Messages

Looking at the results you got I'd say you probably have an intermittent problem closer to home.  Are there any cable splitters you could try bypassing?

New Contributor

 • 

3 Messages

I have the exact same problem!!  It's been going on since then the night of September 9th and hasn't improved.  I also have extremely slow FTP speeds which makes working from home difficult.  I was on the phone with tech support for 20-minutes trying to resolve when they stopped the call and told me there was an outage in my area (Sahuarita.) 

Now it's two days later and I still have the issues.  They reset the modem, I've bypassed the router and nothing fixes it.  Here is my ping path as well... notice the huge loss percentage.

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             172.16.12.1 -    0 |  121 |  121 |    0 |    0 |    9 |    1 |
|                             10.97.100.1 -    4 |  105 |  101 |    5 |   12 |   24 |    7 |
|                             172.21.1.26 -   11 |   84 |   75 |    6 |   12 |  127 |   18 |
|          mcdldsrj01-ae2.0.rd.ph.cox.net -    9 |   89 |   81 |   10 |   16 |   34 |   10 |
|           ae57.bar2.Phoenix1.Level3.net -    8 |   91 |   84 |   11 |   20 |  140 |   32 |
|                   No response from host -  100 |   24 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   24 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   24 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   24 |    0 |    0 |    0 |    0 |    0 |
|    ae-208-3608.bar21.Tustin1.Level3.net -    4 |  105 |  101 |   22 |   32 |  198 |   24 |
|                          192.205.37.145 -    7 |   97 |   91 |   26 |   31 |   53 |   27 |
|                    cr2.la2ca.ip.att.net -    5 |  101 |   96 |   25 |   32 |  101 |   30 |
|                          12.123.132.209 -    7 |   97 |   91 |   25 |   45 |  138 |   89 |
|                          12.122.251.186 -    7 |   97 |   91 |   25 |   38 |  203 |   26 |
|                            206.16.68.42 -    8 |   93 |   86 |    0 |   37 |  236 |   28 |
|     paxonix-placeholder.lax1.attens.net -    4 |  100 |   96 |   26 |   32 |  155 |   28 |
|                           12.129.209.68 -    4 |  105 |  101 |   25 |   30 |   69 |   26 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Former Moderator

 • 

7.1K Messages

@sylance

I think something similar is going on in your case however upon taking a look I also see what whatever you currently have connected to the modem isn't capable of reaching Ultimate speeds only having a 100Mbps Ethernet port.  If you could post results of the same test without the router attached it may provide a better idea of where the problem may lie.