Diablo® III

Pretty bad lag & rubber banding

I don't know if we're still posting updates on this, or if anything is happening in this space. The further info thread above is closed, so I thought I'd post this here.

Played Sunday 18th, Tuesday 20th, and Wed 21st of November between 8PM and 10PM, and 7AM to 8AM (AEST, GMT+10)

Latency was 90% stable at 280ms; occasional jumps to yellow which lasted for a few minutes.

Rubberbanding was quite frequent. Mostly noticed yesterday when my latency showed green, but I began a fight in Act 2 with some Elite dude... the screen paused, then jittered, then fast forwarded to show me my death.

I can't pin point anything helpful, unfortunately, as to what/why it is happening. It just seems quite random, but annoyingly frequent.

Something to consider before starting a hardcore character, that's for sure. Or just see it as something that adds to the difficulties of hardcore. :)
Reply Quote
Still unable to play D3 atm. 4:57am GMT+10. Latency is fine when in town, but whenever I hit anywhere outside town, eg. Desolate Sands, the latency drops to red.

Ticket submitted.
Reply Quote
I've experienced the same thing over the last two days. Prior to that I haven't had lag issues at all.
Reply Quote
Exactly same boat, last few days insane lag and choppy lag spikes being in town or on a map its unplayable and rather disappointing since its been fine for the last time i was playing with no lag.
Reply Quote
C:\Windows\System32>tracert battle.net

Tracing route to battle.net [12.129.242.30]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway.home.gateway
2 29 ms 30 ms 71 ms 172.18.212.3
3 28 ms 28 ms 28 ms 172.18.69.110
4 33 ms 34 ms 33 ms 172.18.241.105
5 32 ms 34 ms 34 ms bundle-ether10-woo10.brisbane.telstra.net [110.1
42.226.13]
6 36 ms 34 ms 35 ms bundle-ether3.woo-core1.brisbane.telstra.net [20
3.50.11.52]
7 35 ms 29 ms 32 ms tengige0-8-0-5-1.cha-core4.brisbane.telstra.net
[203.50.6.217]
8 47 ms 46 ms 45 ms bundle-ether11.ken-core4.sydney.telstra.net [203
.50.11.72]
9 50 ms 47 ms 45 ms bundle-ether1.pad-gw2.sydney.telstra.net [203.50
.6.29]
10 45 ms 44 ms 45 ms tengigabitethernet11-0.sydp-core02.sydney.reach.
com [203.50.13.86]
11 194 ms 191 ms 192 ms i-0-4-2-0.paix-core01.bx.telstraglobal.net [202.
84.140.157]
12 193 ms 190 ms 192 ms i-4-2.paix01.bi.telstraglobal.net [202.84.251.10
6]
13 190 ms 190 ms 190 ms 206.24.240.149
14 215 ms 243 ms 213 ms er2-xe-11-1-0.sanfrancisco.savvis.net [204.70.20
6.58]
15 215 ms 221 ms 270 ms pr2-ge-7-0-0.SanJoseEquinix.savvis.net [204.70.2
03.22]
16 215 ms 217 ms 215 ms savvis-gw.sffca.ip.att.net [192.205.36.5]
17 238 ms 238 ms 234 ms cr1.sffca.ip.att.net [12.122.137.122]
18 239 ms 240 ms 239 ms cr1.la2ca.ip.att.net [12.122.3.122]
19 235 ms 237 ms 236 ms gar20.la2ca.ip.att.net [12.122.128.181]
20 234 ms 234 ms 236 ms 12-122-254-234.attens.net [12.122.254.234]
21 236 ms 237 ms 236 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.12
9.193.250]
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.
Reply Quote
Got a from Blizzard with things to try (Probably the standard email people get). Will try them all and update the ticket and keep people updated, whether they want to know or not. :)
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]