Diablo® III

Latency Issues

(Locked)

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 7 ms 7 ms 7 ms 142.254.196.61
3 15 ms 15 ms 16 ms cpe-024-031-209-138.sc.res.rr.com [24.31.209.138]
4 26 ms 34 ms 28 ms 24.93.64.16
5 37 ms 40 ms 37 ms 107.14.19.20
6 37 ms 37 ms 31 ms ae0.pr1.dca10.tbone.rr.com [107.14.17.200]
7 45 ms 32 ms 34 ms ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
8 53 ms 50 ms 51 ms 192.205.34.245
9 105 ms 103 ms 103 ms cr2.wswdc.ip.att.net [12.122.134.186]
10 108 ms 108 ms 107 ms cr1.cgcil.ip.att.net [12.122.18.21]
11 106 ms 114 ms 116 ms cr2.dvmco.ip.att.net [12.122.31.85]
12 173 ms 137 ms 112 ms cr1.slkut.ip.att.net [12.122.30.25]
13 109 ms 106 ms 108 ms cr2.la2ca.ip.att.net [12.122.30.30]
14 104 ms 105 ms 102 ms gar20.la2ca.ip.att.net [12.122.128.181]
15 107 ms 105 ms 104 ms 12-122-254-234.attens.net [12.122.254.234]
16 104 ms 110 ms 103 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54]
17 113 ms 109 ms 104 ms 12.129.209.68

Trace complete.
Support Forum Agent
djw78,

Let's try running a pathping of your connection to see what that shows us. For the most accurate results, try running the pathping when the connection issue that you are experiencing is at its worst.

Here's a support article that will help with that: Running A Pathping Test

Once you have the pathping, go ahead and post it into your next reply.

***The pathping report is two parts. Once you get to where it says, "Computing statistics for X amount of seconds, you will want to wait about 10 minutes before the second part of the report is complete.***
______________________________________________________
I'm available Monday through Friday from 11AM to 8PM Pacific Time
Support Contact Information

Got some feedback?
Tracing route to 12.129.209.68 over a maximum of 30 hops

0 Don-PC [192.168.0.10]
1 192.168.0.1
2 142.254.196.61
3 cpe-024-031-209-138.sc.res.rr.com [24.31.209.138]
4 24.93.64.16
5 107.14.19.20
6 ae0.pr1.dca10.tbone.rr.com [107.14.17.200]
7 ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
8 192.205.34.245
9 cr2.wswdc.ip.att.net [12.122.134.186]
10 cr1.cgcil.ip.att.net [12.122.18.21]
11 cr2.dvmco.ip.att.net [12.122.31.85]
12 cr1.slkut.ip.att.net [12.122.30.25]
13 cr2.la2ca.ip.att.net [12.122.30.30]
14 gar20.la2ca.ip.att.net [12.122.128.181]
15 12-122-254-234.attens.net [12.122.254.234]
16 mdf001c7613r0002.lax1.attens.net [206.16.68.54]
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 Don-PC [192.168.0.10]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 11ms 0/ 100 = 0% 0/ 100 = 0% 142.254.196.61
0/ 100 = 0% |
3 18ms 0/ 100 = 0% 0/ 100 = 0% cpe-024-031-209-138.sc.res.rr.com [24.31.209.138]
0/ 100 = 0% |
4 31ms 0/ 100 = 0% 0/ 100 = 0% 24.93.64.16
0/ 100 = 0% |
5 34ms 0/ 100 = 0% 0/ 100 = 0% 107.14.19.20
0/ 100 = 0% |
6 39ms 0/ 100 = 0% 0/ 100 = 0% ae0.pr1.dca10.tbone.rr.com [107.14.17.200]
0/ 100 = 0% |
7 35ms 47/ 100 = 47% 47/ 100 = 47% ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
0/ 100 = 0% |
8 42ms 0/ 100 = 0% 0/ 100 = 0% 192.205.34.245
1/ 100 = 1% |
9 --- 100/ 100 =100% 99/ 100 = 99% cr2.wswdc.ip.att.net [12.122.134.186]
0/ 100 = 0% |
10 --- 100/ 100 =100% 99/ 100 = 99% cr1.cgcil.ip.att.net [12.122.18.21]
0/ 100 = 0% |
11 --- 100/ 100 =100% 99/ 100 = 99% cr2.dvmco.ip.att.net [12.122.31.85]
0/ 100 = 0% |
12 --- 100/ 100 =100% 99/ 100 = 99% cr1.slkut.ip.att.net [12.122.30.25]
0/ 100 = 0% |
13 --- 100/ 100 =100% 99/ 100 = 99% cr2.la2ca.ip.att.net [12.122.30.30]
0/ 100 = 0% |
14 --- 100/ 100 =100% 99/ 100 = 99% gar20.la2ca.ip.att.net [12.122.128.181]
0/ 100 = 0% |
15 --- 100/ 100 =100% 99/ 100 = 99% 12-122-254-234.attens.net [12.122.254.234]
0/ 100 = 0% |
16 --- 100/ 100 =100% 99/ 100 = 99% mdf001c7613r0002.lax1.attens.net [206.16.68.54]
0/ 100 = 0% |
17 107ms 1/ 100 = 1% 0/ 100 = 0% 12.129.209.68

Trace complete.
same here
Tracing route to 12.129.209.68 over a maximum of 30 hops

0 ross-PC [192.168.1.9]
1 192.168.1.1
2 96.165.168.1
3 68.85.251.17
4 68.85.244.57
5 he-3-7-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.91.249]
6 be-11-pe02.1950stemmons.tx.ibone.comcast.net [68.86.82.134]
7 as7018-pe01.1950stemmons.tx.ibone.comcast.net [75.149.230.162]
8 cr2.dlstx.ip.att.net [12.123.16.110]
9 cr2.la2ca.ip.att.net [12.122.28.178]
10 gar29.la2ca.ip.att.net [12.122.129.241]
11 12-122-254-234.attens.net [12.122.254.234]
12 mdf001c7613r0002.lax1.attens.net [206.16.68.54]
13 12.129.209.68

Computing statistics for 325 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 ross-PC [192.168.1.9]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 8ms 0/ 100 = 0% 0/ 100 = 0% 96.165.168.1
0/ 100 = 0% |
3 11ms 1/ 100 = 1% 1/ 100 = 1% 68.85.251.17
0/ 100 = 0% |
4 12ms 1/ 100 = 1% 1/ 100 = 1% 68.85.244.57
0/ 100 = 0% |
5 20ms 0/ 100 = 0% 0/ 100 = 0% he-3-7-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.91.249]
0/ 100 = 0% |
6 18ms 0/ 100 = 0% 0/ 100 = 0% be-11-pe02.1950stemmons.tx.ibone.comcast.net [68.86.82.134]
0/ 100 = 0% |
7 20ms 0/ 100 = 0% 0/ 100 = 0% as7018-pe01.1950stemmons.tx.ibone.comcast.net [75.149.230.162]
0/ 100 = 0% |
8 --- 100/ 100 =100% 100/ 100 =100% cr2.dlstx.ip.att.net [12.123.16.110]
0/ 100 = 0% |
9 --- 100/ 100 =100% 100/ 100 =100% cr2.la2ca.ip.att.net [12.122.28.178]
0/ 100 = 0% |
10 --- 100/ 100 =100% 100/ 100 =100% gar29.la2ca.ip.att.net [12.122.129.241]
0/ 100 = 0% |
11 --- 100/ 100 =100% 100/ 100 =100% 12-122-254-234.attens.net [12.122.254.234]
0/ 100 = 0% |
12 --- 100/ 100 =100% 100/ 100 =100% mdf001c7613r0002.lax1.attens.net [206.16.68.54]
0/ 100 = 0% |
13 50ms 0/ 100 = 0% 0/ 100 = 0% 12.129.209.68

Trace complete.
Having problems as well. Figured I'd post in this thread instead of making a new one since my pathping goes through similar hops to the original poster. Getting a ton of "rubber-banding" during peak hours. Latency is pretty constant (albeit slightly higher during these times than in the morning), but the lag spikes occur every 5-15seconds. I use an ability and/or move my character and ~1sec later I will lag back to the location I was moving from and fire the first skill along with the skill I am currently using. Any help would be appreciated since it's been ongoing for about a week.

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 brgordon-PC [192.168.0.100]
1 192.168.0.1
2 142.254.200.29
3 gi12-0-0-2041.gnboncsg-rtr1.triad.rr.com [24.28.225.117]
4 ge-3-1-0.rlghncpop-rtr1.southeast.rr.com [24.93.64.178]
5 107.14.19.20
6 so-1-1-1.c1.buf00.tbone.rr.com [66.109.1.113]
7 ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
8 192.205.34.245
9 cr2.wswdc.ip.att.net [12.122.134.186]
10 cr1.cgcil.ip.att.net [12.122.18.21]
11 cr2.dvmco.ip.att.net [12.122.31.85]
12 cr1.slkut.ip.att.net [12.122.30.25]
13 cr2.la2ca.ip.att.net [12.122.30.30]
14 gar20.la2ca.ip.att.net [12.122.128.181]
15 12.122.251.190
16 206.16.68.46
17 12.129.199.178
18 12.129.209.68

Computing statistics for 450 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 *-PC [192.168.0.100]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 23ms 0/ 100 = 0% 0/ 100 = 0% 142.254.200.29
0/ 100 = 0% |
3 27ms 0/ 100 = 0% 0/ 100 = 0% gi12-0-0-2041.gnboncsg-rtr1.triad.rr.com [24.28.225.117]
0/ 100 = 0% |
4 29ms 0/ 100 = 0% 0/ 100 = 0% ge-3-1-0.rlghncpop-rtr1.southeast.rr.com [24.93.64.178]
0/ 100 = 0% |
5 42ms 0/ 100 = 0% 0/ 100 = 0% 107.14.19.20
0/ 100 = 0% |
6 39ms 0/ 100 = 0% 0/ 100 = 0% so-1-1-1.c1.buf00.tbone.rr.com [66.109.1.113]
0/ 100 = 0% |
7 39ms 50/ 100 = 50% 50/ 100 = 50% ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
0/ 100 = 0% |
8 48ms 0/ 100 = 0% 0/ 100 = 0% 192.205.34.245
3/ 100 = 3% |
9 --- 100/ 100 =100% 97/ 100 = 97% cr2.wswdc.ip.att.net [12.122.134.186]
0/ 100 = 0% |
10 --- 100/ 100 =100% 97/ 100 = 97% cr1.cgcil.ip.att.net [12.122.18.21]
0/ 100 = 0% |
11 --- 100/ 100 =100% 97/ 100 = 97% cr2.dvmco.ip.att.net [12.122.31.85]
0/ 100 = 0% |
12 --- 100/ 100 =100% 97/ 100 = 97% cr1.slkut.ip.att.net [12.122.30.25]
0/ 100 = 0% |
13 --- 100/ 100 =100% 97/ 100 = 97% cr2.la2ca.ip.att.net [12.122.30.30]
0/ 100 = 0% |
14 --- 100/ 100 =100% 97/ 100 = 97% gar20.la2ca.ip.att.net [12.122.128.181]
0/ 100 = 0% |
15 --- 100/ 100 =100% 97/ 100 = 97% 12.122.251.190
0/ 100 = 0% |
16 --- 100/ 100 =100% 97/ 100 = 97% 206.16.68.46
0/ 100 = 0% |
17 --- 100/ 100 =100% 97/ 100 = 97% 12.129.199.178
0/ 100 = 0% |
18 119ms 3/ 100 = 3% 0/ 100 = 0% 12.129.209.68

Trace complete.
I'm also having the same issue as OP.. lots of rubberbanding and just lag spiking..

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 Solaris-PC.phub.net.cable.rogers.com [192.168.0.102]
1 192.168.0.2
2 7.11.163.53
3 69.63.242.121
4 gw02.mtnk-6-1-2.mtnk.phub.net.cable.rogers.com [69.63.248.1]
5 69.63.248.89
6 xe-7-1-2.edge8.NewYork1.Level3.net [4.31.30.57]
7 ae-4-90.edge3.NewYork1.Level3.net [4.69.155.209]
8 att-level3.newyork1.level3.net [4.68.63.142]
9 cr1.n54ny.ip.att.net [12.122.131.102]
10 cr2.cgcil.ip.att.net [12.122.1.2]
11 cr1.cgcil.ip.att.net [12.122.2.53]
12 cr2.dvmco.ip.att.net [12.122.31.85]
13 cr1.slkut.ip.att.net [12.122.30.25]
14 cr2.la2ca.ip.att.net [12.122.30.30]
15 gar20.la2ca.ip.att.net [12.122.128.181]
16 12.122.251.190
17 mdf001c7613r0002.lax1.attens.net [206.16.68.54]
18 12.129.209.68

Computing statistics for 450 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Solaris-PC.phub.net.cable.rogers.c
om [192.168.0.102]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.2
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% 7.11.163.53
0/ 100 = 0% |
3 10ms 37/ 100 = 37% 37/ 100 = 37% 69.63.242.121
0/ 100 = 0% |
4 --- 100/ 100 =100% 100/ 100 =100% gw02.mtnk-6-1-2.mtnk.phub.net.cable.rogers.com [69.63.248.1]
0/ 100 = 0% |
5 --- 100/ 100 =100% 100/ 100 =100% 69.63.248.89
0/ 100 = 0% |
6 25ms 0/ 100 = 0% 0/ 100 = 0% xe-7-1-2.edge8.NewYork1.Level3.net[4.31.30.57]
0/ 100 = 0% |
7 28ms 0/ 100 = 0% 0/ 100 = 0% ae-4-90.edge3.NewYork1.Level3.net[4.69.155.209]
1/ 100 = 1% |
8 --- 100/ 100 =100% 99/ 100 = 99% att-level3.newyork1.level3.net [4.68.63.142]
0/ 100 = 0% |
9 --- 100/ 100 =100% 99/ 100 = 99% cr1.n54ny.ip.att.net [12.122.131.102]
0/ 100 = 0% |
10 --- 100/ 100 =100% 99/ 100 = 99% cr2.cgcil.ip.att.net [12.122.1.2]
0/ 100 = 0% |
11 --- 100/ 100 =100% 99/ 100 = 99% cr1.cgcil.ip.att.net [12.122.2.53]
0/ 100 = 0% |
12 --- 100/ 100 =100% 99/ 100 = 99% cr2.dvmco.ip.att.net [12.122.31.85]
0/ 100 = 0% |
13 --- 100/ 100 =100% 99/ 100 = 99% cr1.slkut.ip.att.net [12.122.30.25]
0/ 100 = 0% |
14 --- 100/ 100 =100% 99/ 100 = 99% cr2.la2ca.ip.att.net [12.122.30.30]
0/ 100 = 0% |
15 --- 100/ 100 =100% 99/ 100 = 99% gar20.la2ca.ip.att.net [12.122.128.181]
0/ 100 = 0% |
16 --- 100/ 100 =100% 99/ 100 = 99% 12.122.251.190
0/ 100 = 0% |
17 --- 100/ 100 =100% 99/ 100 = 99% mdf001c7613r0002.lax1.attens.net [
206.16.68.54]
0/ 100 = 0% |
18 92ms 1/ 100 = 1% 0/ 100 = 0% 12.129.209.68

Trace complete.
Support Forum Agent
djw78

7 35ms 47/ 100 = 47% 47/ 100 = 47% ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]


It looks like your connection is experiencing a 47% data loss when it reaches the server located at hop 7, which looks to be part of the TATA Communications network. TATA Communications is a peering partner being used by your ISP, so you will want to contact your ISP to have them look into this.
______________________________________________________
I'm available Monday through Friday from 11AM to 8PM Pacific Time
Support Contact Information

Got some feedback?
Support Forum Agent
Luckyone,

3 11ms 1/ 100 = 1% 1/ 100 = 1% 68.85.251.17
0/ 100 = 0% |
4 12ms 1/ 100 = 1% 1/ 100 = 1% 68.85.244.57
0/ 100 = 0% |


Your connection is losing 1% data when it reaches hops 3 and 4. Both of those hops are part of the Comcast network. You will want to contact your ISP about this. When contacting them, you will want to request to speak to a tier 3 tech representative since they should be more familiar with reading tracerts.
______________________________________________________
I'm available Monday through Friday from 11AM to 8PM Pacific Time
Support Contact Information

Got some feedback?
Support Forum Agent
Orangeaccord,

7 39ms 50/ 100 = 50% 50/ 100 = 50% ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]


Like the OP, your connection is also losing data when it reaches the server at hop 7, which is part of the TATA Communications network. You are going to want to contact your ISP so they can look further into this for you.
______________________________________________________
I'm available Monday through Friday from 11AM to 8PM Pacific Time
Support Contact Information

Got some feedback?
90 Human Warlock
8810
I got lagspike as well again :(



0 Patrick-PC [192.168.1.182]
1 router.asus.com [192.168.1.1]
2 172.20.128.1
3 172.30.9.141
4 172.30.14.177
5 xe-3-1-0.mtl10.ip4.tinet.net [173.241.130.13]
6 xe-7-2-0.nyc20.ip4.tinet.net [141.136.107.126]
7 192.205.37.37
8 cr1.n54ny.ip.att.net [12.122.81.106]
9 cr2.cgcil.ip.att.net [12.122.1.2]
10 cr1.cgcil.ip.att.net [12.122.2.53]
11 cr2.dvmco.ip.att.net [12.122.31.85]
12 cr1.slkut.ip.att.net [12.122.30.25]
13 cr2.la2ca.ip.att.net [12.122.30.30]
14 gar20.la2ca.ip.att.net [12.122.128.181]
15 12.122.251.190
16 mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
17 12.129.199.178
18 12.129.209.68

Traitement des statistiques pendant 450 secondes...
Source vers ici Ce noud/lien
Saut RTT Perdu/Envoy‚ = % Perdu/Envoy‚ = % Adresse
0 Patrick-PC [192.168.1.182]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% router.asus.com [192.168.1.1]
0/ 100 = 0% |
2 8ms 0/ 100 = 0% 0/ 100 = 0% 172.20.128.1
0/ 100 = 0% |
3 14ms 0/ 100 = 0% 0/ 100 = 0% 172.30.9.141
0/ 100 = 0% |
4 21ms 0/ 100 = 0% 0/ 100 = 0% 172.30.14.177
0/ 100 = 0% |
5 16ms 0/ 100 = 0% 0/ 100 = 0% xe-3-1-0.mtl10.ip4.tinet.net [173.241.130.13]
0/ 100 = 0% |
6 26ms 0/ 100 = 0% 0/ 100 = 0% xe-7-2-0.nyc20.ip4.tinet.net [141.136.107.126]
0/ 100 = 0% |
7 45ms 1/ 100 = 1% 1/ 100 = 1% 192.205.37.37
0/ 100 = 0% |
8 --- 100/ 100 =100% 100/ 100 =100% cr1.n54ny.ip.att.net [12.122.81.106]
0/ 100 = 0% |
9 --- 100/ 100 =100% 100/ 100 =100% cr2.cgcil.ip.att.net [12.122.1.2]
0/ 100 = 0% |
10 --- 100/ 100 =100% 100/ 100 =100% cr1.cgcil.ip.att.net [12.122.2.53]
0/ 100 = 0% |
11 --- 100/ 100 =100% 100/ 100 =100% cr2.dvmco.ip.att.net [12.122.31.85]
0/ 100 = 0% |
12 --- 100/ 100 =100% 100/ 100 =100% cr1.slkut.ip.att.net [12.122.30.25]
0/ 100 = 0% |
13 --- 100/ 100 =100% 100/ 100 =100% cr2.la2ca.ip.att.net [12.122.30.30]
0/ 100 = 0% |
14 --- 100/ 100 =100% 100/ 100 =100% gar20.la2ca.ip.att.net [12.122.128.181]
0/ 100 = 0% |
15 --- 100/ 100 =100% 100/ 100 =100% 12.122.251.190
0/ 100 = 0% |
16 --- 100/ 100 =100% 100/ 100 =100% mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
0/ 100 = 0% |
17 --- 100/ 100 =100% 100/ 100 =100% 12.129.199.178
0/ 100 = 0% |
18 95ms 0/ 100 = 0% 0/ 100 = 0% 12.129.209.68


edit: btw why it only happen to everyone on diablo 3 only? I mean all of us having lags here doesn't lags anywhere else.
Edited by snurfy#1559 on 4/10/2014 7:40 PM PDT
Support Forum Agent
3 10ms 37/ 100 = 37% 37/ 100 = 37% 69.63.242.121


7 28ms 0/ 100 = 0% 0/ 100 = 0% ae-4-90.edge3.NewYork1.Level3.net[4.69.155.209]
1/ 100 = 1% |


It looks like the main issue with your connection starts at hop 3 where the connection is losing 37% data. That hop is part of the Rogers network, so contacting your ISP would be the best thing to do here. Also, the link between hop 7 and 8 is losing 1% data. That could be happening because of the earlier data loss, or it may be a separate issue, but it's also something that the ISP will need to look at.
______________________________________________________
I'm available Monday through Friday from 11AM to 8PM Pacific Time
Support Contact Information

Got some feedback?
Yikes, 100%. ISP issue I'll assume.

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 Josh-PC [192.168.1.3]
1 192.168.1.1
2 cpe-98-156-96-1.kc.res.rr.com [98.156.96.1]
3 tge7-1.shwnks12-cer1.kc.rr.com [65.28.16.98]
4 tge0-10-0-8.ksczmogn01r.kc.rr.com [98.156.43.84]
5 ae30.dllatxl3-cr01.kc.rr.com [98.156.42.0]
6 107.14.19.92
7 ae0.pr1.dfw10.tbone.rr.com [107.14.17.232]
8 ix-23-0.tcore2.DT8-Dallas.as6453.net [66.110.57.97]
9 * if-2-2.tcore1.DT8-Dallas.as6453.net [66.110.56.5]
10 192.205.36.205
11 cr2.dlstx.ip.att.net [12.122.100.90]
12 cr2.la2ca.ip.att.net [12.122.28.178]
13 gar29.la2ca.ip.att.net [12.122.129.241]
14 12-122-254-234.attens.net [12.122.254.234]
15 mdf001c7613r0002.lax1.attens.net [206.16.68.54]
16 12.129.209.68

Computing statistics for 400 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Josh-PC [192.168.1.3]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 17ms 0/ 100 = 0% 0/ 100 = 0% cpe-98-156-96-1.kc.res.rr.com [98.156.96.1]
0/ 100 = 0% |
3 19ms 0/ 100 = 0% 0/ 100 = 0% tge7-1.shwnks12-cer1.kc.rr.com [65.28.16.98]
0/ 100 = 0% |
4 17ms 0/ 100 = 0% 0/ 100 = 0% tge0-10-0-8.ksczmogn01r.kc.rr.com
[98.156.43.84]
0/ 100 = 0% |
5 29ms 0/ 100 = 0% 0/ 100 = 0% ae30.dllatxl3-cr01.kc.rr.com [98.156.42.0]
0/ 100 = 0% |
6 29ms 0/ 100 = 0% 0/ 100 = 0% 107.14.19.92
0/ 100 = 0% |
7 31ms 2/ 100 = 2% 2/ 100 = 2% ae0.pr1.dfw10.tbone.rr.com [107.14.17.232]
0/ 100 = 0% |
8 29ms 0/ 100 = 0% 0/ 100 = 0% ix-23-0.tcore2.DT8-Dallas.as6453.net [66.110.57.97]
0/ 100 = 0% |
9 27ms 0/ 100 = 0% 0/ 100 = 0% if-2-2.tcore1.DT8-Dallas.as6453.net [66.110.56.5]
0/ 100 = 0% |
10 30ms 0/ 100 = 0% 0/ 100 = 0% 192.205.36.205
0/ 100 = 0% |
11 --- 100/ 100 =100% 100/ 100 =100% cr2.dlstx.ip.att.net [12.122.100.90]
0/ 100 = 0% |
12 --- 100/ 100 =100% 100/ 100 =100% cr2.la2ca.ip.att.net [12.122.28.178]
0/ 100 = 0% |
13 --- 100/ 100 =100% 100/ 100 =100% gar29.la2ca.ip.att.net [12.122.129.241]
0/ 100 = 0% |
14 --- 100/ 100 =100% 100/ 100 =100% 12-122-254-234.attens.net [12.122.254.234]
0/ 100 = 0% |
15 --- 100/ 100 =100% 100/ 100 =100% mdf001c7613r0002.lax1.attens.net [206.16.68.54]
0/ 100 = 0% |
16 61ms 0/ 100 = 0% 0/ 100 = 0% 12.129.209.68

Trace complete.
I'm not sure why everyone's ISP or Routers are being called out with this. There are numerous posts of people experiencing the same effect - hitches, loot lag, rubber banding, delayed ability use, and it all started happening very recently (since Tuesday). With many people reporting the same stuff through ping thing, could it be possible it does not have to do with our connections?
Yup same since Tuesday Lag every time I run in to a large pack of mobs or elites. I know my ISP sucks so no sense in running a trace to be called out saying contact my ISP... Finally get my guy geared up to run some Torment and now the Lag kills me every damn time! It's really sucking the fun out of this game.
MVP - Technical Support
View profile
04/11/2014 12:12 AMPosted by moose
With many people reporting the same stuff through ping thing, could it be possible it does not have to do with our connections?


Of course anything is possible, but as you can see from the pathpings here with major packet loss, connection is the most common reason. Over the past couple weeks we have seen:

-bad network cards
-incorrect router settings
-bad routers
-bad modem
-damaged or lose network cables
-Local ISP issues (TWC, Comcast, Cox, Bell, are just a few that had outtages)
-Level 3 backbone issues (AT&T, XO Communications, TATA as in this thread)
-A damaged undersea cable that impacted most of SEA for weeks
-the crazy DC issue with Bliz yesterday/today that was Blizzard's fault

If people just assume everything is Blizzard's fault they miss the chance to troubleshoot, find, and fix what is most likely the cause of the issue. Blizzard issues tend to be easy to tell - they result in 40 page threads in an hour and the forums get flooded.
Then why did all the lag start when the last patch went up? It was fine before that and all other games are fine... you're right must be every ones server started losing packets since Tuesday! Damn you world ISP! I did the Fix for the curser lag (setting the display to 100%) and that seemed to help some but still getting Lag deaths a plenty!
so here's mine

0 Gregory-PC [192.168.1.14]
1 192.168.1.1
2 c-50-182-22-1.hsd1.nj.comcast.net [50.182.22.1]
3 xe-0-2-0-32767-sur01.turnersville.nj.panjde.comcast.net [68.85.129.93]
4 xe-4-0-0-0-ar03.audubon.nj.panjde.comcast.net [68.85.63.57]
5 he-3-8-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.95.157]
6 pos-0-2-0-0-pe01.ashburn.va.ibone.comcast.net [68.86.86.70]
7 192.205.37.41
8 cr2.wswdc.ip.att.net [12.122.134.186]
9 cr1.cgcil.ip.att.net [12.122.18.21]
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 206.16.68.46
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 Gregory-PC [192.168.1.14]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 43ms 0/ 100 = 0% 0/ 100 = 0% c-50-182-22-1.hsd1.nj.comcast.net
[50.182.22.1]
0/ 100 = 0% |
3 40ms 0/ 100 = 0% 0/ 100 = 0% xe-0-2-0-32767-sur01.turnersville.
nj.panjde.comcast.net [68.85.129.93]
0/ 100 = 0% |
4 39ms 1/ 100 = 1% 1/ 100 = 1% xe-4-0-0-0-ar03.audubon.nj.panjde.
comcast.net [68.85.63.57]
0/ 100 = 0% |
5 33ms 0/ 100 = 0% 0/ 100 = 0% he-3-8-0-0-cr01.ashburn.va.ibone.c
omcast.net [68.86.95.157]
1/ 100 = 1% |
6 32ms 1/ 100 = 1% 0/ 100 = 0% pos-0-2-0-0-pe01.ashburn.va.ibone.
comcast.net [68.86.86.70]
0/ 100 = 0% |
7 30ms 1/ 100 = 1% 0/ 100 = 0% 192.205.37.41
0/ 100 = 0% |
8 --- 100/ 100 =100% 99/ 100 = 99% cr2.wswdc.ip.att.net [12.122.134.1
86]
0/ 100 = 0% |
9 --- 100/ 100 =100% 99/ 100 = 99% cr1.cgcil.ip.att.net [12.122.18.21
]
0/ 100 = 0% |
10 --- 100/ 100 =100% 99/ 100 = 99% cr2.dvmco.ip.att.net [12.122.31.85
]
0/ 100 = 0% |
11 --- 100/ 100 =100% 99/ 100 = 99% cr1.slkut.ip.att.net [12.122.30.25
]
0/ 100 = 0% |
12 --- 100/ 100 =100% 99/ 100 = 99% cr2.la2ca.ip.att.net [12.122.30.30
]
0/ 100 = 0% |
13 --- 100/ 100 =100% 99/ 100 = 99% gar20.la2ca.ip.att.net [12.122.128
.181]
0/ 100 = 0% |
14 --- 100/ 100 =100% 99/ 100 = 99% 12-122-254-234.attens.net [12.122.
254.234]
0/ 100 = 0% |
15 --- 100/ 100 =100% 99/ 100 = 99% 206.16.68.46
0/ 100 = 0% |
16 --- 100/ 100 =100% 99/ 100 = 99% 12.129.199.178
0/ 100 = 0% |
17 113ms 1/ 100 = 1% 0/ 100 = 0% 12.129.209.68

Trace complete.

C:\Users\Gregory>

i lose it at hop 8, judging from earlier replies, that's blizz server right? any help is appreciated. my router has the right ports open and i also only started getting these spikes since the patch. thanks for your time.
MVP - Technical Support
View profile
04/11/2014 03:54 AMPosted by emu
i lose it at hop 8, judging from earlier replies, that's blizz server right? any help is appreciated. my router has the right ports open and i also only started getting these spikes since the patch. thanks for your time.


Hop 8 is where you hit the security masking so it appears to lose packets when it is not. This is covered here https://us.battle.net/support/en/article/running-a-pathping-test
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.


04/11/2014 03:54 AMPosted by emu
4 39ms 1/ 100 = 1% 1/ 100 = 1% xe-4-0-0-0-ar03.audubon.nj.panjde.
comcast.net [68.85.63.57]


This is more likely the cause of some lag, especially if it gets worse. We have a few comcast folks in the past 24 hours actually. Similar packet loss.

04/11/2014 02:07 AMPosted by Shamash
Then why did all the lag start when the last patch went up? It was fine before that and all other games are fine... you're right must be every ones server started losing packets since Tuesday! Damn you world ISP! I


Your choice is to point the finger at Blizzard or do some troubleshooting and see if there is anything on your end or the ISP. I will just point you to a thread from last night on 4 days of lag http://us.battle.net/d3/en/forum/topic/12471477576 Had the player assumed it was Blizzard or the patch he would never have fixed it.
If people just assume everything is Blizzard's fault they miss the chance to troubleshoot, find, and fix what is most likely the cause of the issue. Blizzard issues tend to be easy to tell - they result in 40 page threads in an hour and the forums get flooded.[/quote]

Not sure y

04/11/2014 01:21 AMPosted by MissCheetah
04/11/2014 12:12 AMPosted by moose
With many people reporting the same stuff through ping thing, could it be possible it does not have to do with our connections?


Of course anything is possible, but as you can see from the pathpings here with major packet loss, connection is the most common reason. Over the past couple weeks we have seen:

-bad network cards
-incorrect router settings
-bad routers
-bad modem
-damaged or lose network cables
-Local ISP issues (TWC, Comcast, Cox, Bell, are just a few that had outtages)
-Level 3 backbone issues (AT&T, XO Communications, TATA as in this thread)
-A damaged undersea cable that impacted most of SEA for weeks
-the crazy DC issue with Bliz yesterday/today that was Blizzard's fault

If people just assume everything is Blizzard's fault they miss the chance to troubleshoot, find, and fix what is most likely the cause of the issue. Blizzard issues tend to be easy to tell - they result in 40 page threads in an hour and the forums get flooded.


Not sure if you decided to troll or not, but this is obviously not us. This is on blizzards side. You can't really expect to be our fault when they release a new expanions/patch and all of a sudden everyones connection breaks/lags for many reasons and from many different ISP companies. How can you even think that? This happened over a patch/expansion. Not casually.
MVP - Technical Support
View profile
04/11/2014 04:57 AMPosted by Xivia
Not sure if you decided to troll or not, but this is obviously not us. This is on blizzards side. You can't really expect to be our fault when they release a new expanions/patch and all of a sudden everyones connection breaks/lags for many reasons and from many different ISP companies. How can you even think that? This happened over a patch/expansion. Not casually.


The DC mess is Blizzard's fault. The general latency this thread is about is not. Read the link I posted above for another player who started getting lag 4 days ago. He could blame it on Blizzard OR post...and found out it was a software update Comcast pushed to his router causing massive packet loss. Reset to defaults and reboot fixed it. Had he not posted a pathping and asked for help, he would be sitting there angry and not playing. Instead he is probably off running rifts.

This thread was about general latency, not your specific issue with lag when engaging in very specific activities.
Edited by MissCheetah#1661 on 4/11/2014 5:28 AM PDT
This topic is locked.

Please report any Code of Conduct violations, including:

Threats of violence. We take these seriously and will alert the proper authorities.

Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.

Harassing or discriminatory language. This will not be tolerated.

Forums Code of Conduct

Report Post # written by

Reason
Explain (256 characters max)
Submit Cancel

Reported!

[Close]