AnsweredAssumed Answered

Pathping/traceroute issues

Question asked by ghostjelly on Apr 18, 2014
Latest reply on Apr 25, 2014 by corbin

I've recently been having issues while playing Diablo3 through my connection. I was using wireless without any problems but two days ago or so, something happened that just makes the game unplayable. I did switch to a hardline to the modem to help reduce the problem. Other people ARE having issues as well, but not all of them, across different ISPs. It's not specifically blizzards servers nor is it Shaw. However, my personal trace route and pathping both show losses / spikes in shaws part of the connection.

 

Just posting this before work, so if any other data is needed let me know.

I was just hoping you could look into this a bit, I haven't had any issues beforehand.

 

Tracing route to 12.129.209.68 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     8 ms    16 ms     9 ms  70.64.240.1
  3    30 ms    17 ms    16 ms  rd2ha-tge1-1-13.ss.shawcable.net [64.59.182.131]
  4    86 ms   204 ms   202 ms  rd1ha-tge2-1.ss.shawcable.net [66.163.73.5]
  5    25 ms    26 ms    24 ms  rc3sc-tge0-10-0-24.wp.shawcable.net [66.163.76.189]
  6    41 ms    44 ms    40 ms  rc4ec-hge0-9-0-0.il.shawcable.net [66.163.77.206]
  7    40 ms    43 ms    40 ms  chi-eqx-i1-link.telia.net [62.115.12.81]
  8    45 ms    44 ms    59 ms  att-ic-155020-chi-bb1.c.telia.net [213.248.87.254]
  9    82 ms    80 ms    80 ms  cr1.cgcil.ip.att.net [12.122.133.34]
10    93 ms    82 ms    93 ms  cr2.dvmco.ip.att.net [12.122.31.85]
11    81 ms    79 ms    89 ms  cr1.slkut.ip.att.net [12.122.30.25]
12    80 ms   102 ms    84 ms  cr2.la2ca.ip.att.net [12.122.30.30]
13    75 ms    75 ms    77 ms  gar20.la2ca.ip.att.net [12.122.128.181]
14   102 ms    91 ms    84 ms  12-122-254-234.attens.net [12.122.254.234]
15    82 ms    80 ms    76 ms  mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
16    83 ms   108 ms    80 ms  12.129.199.178
17    91 ms    79 ms    84 ms  12.129.209.68

Trace complete.


Tracing route to 12.129.209.68 over a maximum of 30 hops

  0  [192.168.0.11]
  1  192.168.0.1
  2  70.64.240.1
  3  rd2ha-tge1-1-13.ss.shawcable.net [64.59.182.131]
  4  rd1ha-tge2-1.ss.shawcable.net [66.163.73.5]
  5  rc3sc-tge0-10-0-24.wp.shawcable.net [66.163.76.189]
  6  rc4ec-hge0-9-0-0.il.shawcable.net [66.163.77.206]
  7  chi-eqx-i1-link.telia.net [62.115.9.77]
  8  att-ic-155020-chi-bb1.c.telia.net [213.248.87.254]
  9  cr1.cgcil.ip.att.net [12.122.133.34]
10  cr2.dvmco.ip.att.net [12.122.31.85]
11  cr1.slkut.ip.att.net [12.122.30.25]
12  cr2.la2ca.ip.att.net [12.122.30.30]
13  gar20.la2ca.ip.att.net [12.122.128.181]
14  12-122-254-234.attens.net [12.122.254.234]
15  mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
16  12.129.199.178
17  12.129.209.68

Computing statistics for 425 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Batcomputer [192.168.0.11]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.0.1
                                3/ 100 =  3%   |
  2   16ms     7/ 100 =  7%     4/ 100 =  4%  70.64.240.1
                                0/ 100 =  0%   |
  3   18ms     7/ 100 =  7%     4/ 100 =  4%  rd2ha-tge1-1-13.ss.shawcable.net [64.59.182.131]
                                0/ 100 =  0%   |
  4   22ms     4/ 100 =  4%     1/ 100 =  1%  rd1ha-tge2-1.ss.shawcable.net [66.163.73.5]
                                0/ 100 =  0%   |
  5   27ms     3/ 100 =  3%     0/ 100 =  0%  rc3sc-tge0-10-0-24.wp.shawcable.net [66.163.76.189]
                                2/ 100 =  2%   |
  6   41ms     6/ 100 =  6%     1/ 100 =  1%  rc4ec-hge0-9-0-0.il.shawcable.net [66.163.77.206]
                                0/ 100 =  0%   |
  7   45ms     9/ 100 =  9%     4/ 100 =  4%  chi-eqx-i1-link.telia.net [62.115.9.77]
                                0/ 100 =  0%   |
  8   51ms     5/ 100 =  5%     0/ 100 =  0%  att-ic-155020-chi-bb1.c.telia.net [213.248.87.254]
                                1/ 100 =  1%   |
  9  ---     100/ 100 =100%    94/ 100 = 94%  cr1.cgcil.ip.att.net [12.122.133.34]
                                0/ 100 =  0%   |
10  ---     100/ 100 =100%    94/ 100 = 94%  cr2.dvmco.ip.att.net [12.122.31.85]
                                0/ 100 =  0%   |
11  ---     100/ 100 =100%    94/ 100 = 94%  cr1.slkut.ip.att.net [12.122.30.25]
                                0/ 100 =  0%   |
12  ---     100/ 100 =100%    94/ 100 = 94%  cr2.la2ca.ip.att.net [12.122.30.30]
                                0/ 100 =  0%   |
13  ---     100/ 100 =100%    94/ 100 = 94%  gar20.la2ca.ip.att.net [12.122.128.181]
                                0/ 100 =  0%   |
14  ---     100/ 100 =100%    94/ 100 = 94%  12-122-254-234.attens.net [12.122.254.234]
                                0/ 100 =  0%   |
15  ---     100/ 100 =100%    94/ 100 = 94%  mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
                                0/ 100 =  0%   |
16  ---     100/ 100 =100%    94/ 100 = 94%  12.129.199.178
                                0/ 100 =  0%   |
17   84ms     6/ 100 =  6%     0/ 100 =  0%  12.129.209.68

Trace complete.

 

As taken from Blizzards site for your information about their servers:

"Look at the second block of data with the percentages. A clean pathping will have nothing but 0% from your computer to the last hop before our servers. Anything other than 0% indicates loss of packet integrity.

Our servers scramble pathping data once it reaches them. You can disregard any data which typically shows as 100% packet loss once the pathping reaches that point. To identify our servers, look for the following suffixes: attens.net, att.net, alter.net, telia.net."

Outcomes