Diablo® III

AT&T is killing your latency, graphs inside

You're simply hitting servers which don't support ICMP, that's what the timeouts are. Try a pathping instead, more informative.
Reply Quote
If I pathping to the same address it really tells me nothing. I probably fudged it, but you can be the judge of that...

C:\Users\***>pathping 12.130.244.193

Tracing route to 12.130.244.193 over a maximum of 30 hops

0 ***-PC.gateway.2wire.net [YAY MY IP ADDRESS]
1 home [YAY MY IP ADDRESS]
2 76-219-252-3.lightspeed.sndgca.sbcglobal.net [76.219.252.3]
3 * * *
Computing statistics for 50 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 ***-PC.gateway.2wire.net [YAY MY IP ADDRESS]
1/ 100 = 1% |
1 6ms 1/ 100 = 1% 0/ 100 = 0% home [YAY MY IP ADDRESS]
4/ 100 = 4% |
2 34ms 5/ 100 = 5% 0/ 100 = 0% 76-219-252-3.lightspeed.sndgca.sbc
global.net [76.219.252.3]

Trace complete.
Reply Quote
I've also been having problems with latency "rubberbanding", started for me since patch 1.02c. Doesn't ALWAYS happen, but almost always, especially during peak hours. Jumps back and forth between 200ms and well over 1000ms
Reply Quote
- Technical Support
View profile
Hamcraft this thread requires data. Do you have data for this thread? Tasty tasty data?
Reply Quote
Well guess what. Ignore my post, my problem was completely different. Just needed a router power cycle. Can't believe it took me over a week to figure that out. Sorry
Reply Quote
I'm going to purchase a new network card for my computer and see if it makes a difference since they are relatively cheap! Why do we have to go through this!
Reply Quote
Pathping is useless for identifying problems inside ATT/Blizzard's network. It will only show if you have loss somewhere in between.

Also, the in-game latency meter is useless for looking at your actual/delivered performance until Blizzard straightens out whatever is going on.

At 3pm I get 120ms (really good!) but lots of laggy/unresponsive controls (really bad!).
At 3am I get 100ms (even better!) but get crisp, responsive control.

There's no way 20ms is making the difference. It really feels like I'm going from 300ms to 100ms.

This is gar29's ongoing performance btw:

http://imgur.com/wpOoi
Reply Quote
I tried calling at&t today. As expected it was a waste of time and effort but I still tried to report the bad host.
Reply Quote
This has been my issue since launch. Unfortunately for me the bad AT&T nodes cause error 3007 disconnects for me along with the latency issues. I ran multiple tracerts several months ago and sent them to Blizzard, but never got a response back so I stopped playing the game.
Reply Quote
Same thing here, Scizyr. I really enjoy the brief moments of gameplay I experience, before I get a lag spike/stutter/rubberbanding/whatever you want to call it. These often result in death. Not fun.

As with many, I had hoped 1.04 would address the issue. Silly really, as it does not appear to be a client issue.

Here's more dataz;

Tracing route to 12.130.244.193 over a maximum of 30 hops

1 2 ms 1 ms 1 ms 192.168.1.1
2 124 ms 108 ms 109 ms 74.198.64.254
3 127 ms 178 ms 119 ms 172.25.199.81
4 * 93 ms * 10.118.23.22
5 92 ms 88 ms 129 ms 10.118.20.77
6 127 ms 99 ms 100 ms 192.168.1.75
7 159 ms 106 ms 139 ms 192.168.1.18
8 107 ms 108 ms 129 ms 172.25.192.176
9 107 ms 210 ms 99 ms 10.118.2.209
10 84 ms 79 ms 99 ms 74.198.64.34
11 97 ms 138 ms 99 ms 69.63.248.133
12 117 ms 118 ms 159 ms 69.63.249.165
13 136 ms 138 ms 279 ms 64.71.240.110
14 * 215 ms 345 ms tengigabitethernet3-4.ar4.nyc1.gblx.net [64.208.169.149]
15 193 ms 188 ms 192 ms 192.205.34.65
16 257 ms 199 ms 198 ms cr2.la2ca.ip.att.net [12.122.129.98]
17 205 ms 179 ms 171 ms gar29.la2ca.ip.att.net [12.122.129.241]
18 196 ms 200 ms 198 ms 12-122-254-238.attens.net [12.122.254.238]
19 196 ms 199 ms 238 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
Reply Quote

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]