Diablo® III

Diablo3 is suddenly lagging real bad

Super bad here in Newcastle NSW tonight, unplayable HC action.
Reply Quote
just did another one 1400 ms !!

Tracing route to 12.129.209.68 over a maximum of 30 hops
1 20 ms 8 ms 10 ms 10.213.160.1
2 10 ms 9 ms 10 ms CPE-58-175-61-14.vic.bigpond.net.au [58.175.61.14]
3 10 ms 10 ms 13 ms 58.160.7.226
4 19 ms 10 ms 11 ms 172.18.240.105
5 17 ms 23 ms 23 ms bundle-ether10.lon76.melbourne.telstra.net [110.142.226.45]
6 20 ms 11 ms 23 ms bundle-ether6.exi-core1.melbourne.telstra.net [203.50.11.56]
7 29 ms 35 ms 35 ms bundle-ether12.chw-core2.sydney.telstra.net [203.50.11.74]
8 29 ms 34 ms 35 ms bundle-ether4.ken-core4.sydney.telstra.net [203.50.6.41]
9 36 ms 34 ms 35 ms bundle-ether1.pad-gw2.sydney.telstra.net [203.50.6.29]
10 25 ms 25 ms 29 ms 203.50.13.118
11 170 ms 171 ms 169 ms i-0-4-0-0.paix-core01.bx.telstraglobal.net [202.84.140.37]
12 165 ms 164 ms 165 ms i-0-0-0-3.paix02.bi.telstraglobal.net [202.84.251.94]
13 225 ms 224 ms 223 ms 206.24.240.149
14 224 ms 197 ms 199 ms er2-xe-3-1-0.SanJoseEquinix.savvis.net [204.70.200.197]
15 199 ms 275 ms 202 ms pr2-ge-7-0-0.SanJoseEquinix.savvis.net [204.70.203.22]
16 180 ms 179 ms 177 ms savvis-gw.sffca.ip.att.net [192.205.36.5]
17 180 ms 180 ms 189 ms cr1.sffca.ip.att.net [12.122.137.126]
18 197 ms 188 ms 178 ms cr1.la2ca.ip.att.net [12.122.3.122]
19 262 ms 204 ms 204 ms gar20.la2ca.ip.att.net [12.122.128.181]
20 214 ms 204 ms 205 ms 12-122-254-234.attens.net [12.122.254.234]
21 228 ms * 1402 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.


now hop 21 there definitely shows something a spike compared to the first one you did.
Looking at your trace route is this ADSL as well?
Reply Quote
hi ...nah i'm using Telstra cable ...speedtest shows down @ 30mbps and up at 1mbps

like i said, it fluctuates but yesterday it was so bad i just shut down and watched TV.
Reply Quote
Game was fine earlier today but right now its completely unplayable, spikes over 1000ms and the game completely locks up sometimes only to unfreeze a few seconds later and of course I'm dead.

I can play the Crysis 3 beta or Bf3 multiplayer fine but I can't play this game single player!

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 52 ms 99 ms 100 ms BigPond.BigPond [10.0.0.138]
2 * 24 ms 27 ms 172.18.112.35
3 64 ms 38 ms 27 ms 172.18.66.14
4 108 ms * 32 ms 172.18.239.233
5 52 ms 28 ms 40 ms bundle-ether15.ken43.sydney.telstra.net [110.142.193.141]
6 41 ms 32 ms 34 ms bundle-ether9.ken-core4.sydney.telstra.net [203.50.11.30]
7 66 ms 40 ms 45 ms bundle-ether1.pad-gw2.sydney.telstra.net [203.50.6.29]
8 45 ms 49 ms 332 ms tengigabitethernet1-0.sydp-core02.sydney.reach.com [203.50.13.46]
9 171 ms 252 ms 172 ms i-0-5-0-0.paix-core01.bx.telstraglobal.net [202.84.144.157]
10 170 ms 171 ms 172 ms i-0-0-0-1.paix02.bi.telstraglobal.net [202.84.251.74]
11 182 ms 178 ms 176 ms 206.24.240.149
12 225 ms 216 ms 215 ms er2-xe-3-1-0.SanJoseEquinix.savvis.net [204.70.200.197]
13 307 ms 362 ms 274 ms pr2-ge-7-0-0.SanJoseEquinix.savvis.net [204.70.203.22]
14 313 ms 188 ms * savvis-gw.sffca.ip.att.net [192.205.36.5]
15 219 ms 378 ms 189 ms cr1.sffca.ip.att.net [12.122.137.122]
16 186 ms 205 ms 192 ms cr1.la2ca.ip.att.net [12.122.3.122]
17 194 ms 205 ms 195 ms gar20.la2ca.ip.att.net [12.122.128.181]
18 210 ms 205 ms 201 ms 12.122.251.190
19 198 ms 210 ms 189 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
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
bump +2c

ive done heaps of these traces and only managed to capture the lag once 1402ms
was playing today and latency was 2800ms...infact in game, even the latency meter is lagging, the meter was green @ 600ms but nothing was moving except me running around in circles

we've had lag issues before, and they says that "oh because you're so far away, and the route across the pacific,... etc"

fact of the matter is...its is a NEW issue. its been 3 weeks !

at least someone from Blizzard could respond and tell us "hey guys we diverted resources away for PTR and that's why your service is lagging"
Reply Quote
90 Draenei Priest
0
I ran a couple of traces while playing the other day (during terrible lag). I'm confused as to why D3 is the only online game I play that has these latency issues, very suspicious indeed.

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 33 ms 99 ms 99 ms 10.0.0.138
2 2379 ms 91 ms 92 ms 172.18.208.5
3 35 ms 34 ms 34 ms 172.18.66.170
4 39 ms 35 ms 35 ms 172.18.239.229
5 38 ms 35 ms 37 ms bundle-ether10.chw48.sydney.telstra.net [203.45.17.13]
6 45 ms 35 ms 35 ms bundle-ether6.chw-core2.sydney.telstra.net [203.50.6.153]
7 41 ms 35 ms 35 ms bundle-ether4.ken-core4.sydney.telstra.net [203.50.6.41]
8 46 ms 35 ms 35 ms bundle-ether1.pad-gw2.sydney.telstra.net [203.50.6.29]
9 115 ms 201 ms 1334 ms tengige10-0-0.sydp-core02.sydney.reach.com [203.50.13.94]
10 269 ms 353 ms 346 ms i-0-5-0-0.paix-core01.bx.telstraglobal.net [202.84.144.157]
11 188 ms 189 ms 188 ms i-0-4-0-3.paix02.bi.telstraglobal.net [202.84.251.106]
12 191 ms 191 ms 190 ms 206.24.240.149
13 190 ms 193 ms 221 ms er2-xe-11-1-0.sanfrancisco.savvis.net [204.70.206.58]
14 196 ms 192 ms 192 ms pr2-ge-7-0-0.SanJoseEquinix.savvis.net [204.70.203.22]
15 194 ms 193 ms 194 ms savvis-gw.sffca.ip.att.net [192.205.36.5]
16 236 ms 236 ms 235 ms cr1.sffca.ip.att.net [12.122.137.126]
17 238 ms 239 ms 236 ms cr1.la2ca.ip.att.net [12.122.3.122]
18 234 ms 244 ms 234 ms gar20.la2ca.ip.att.net [12.122.128.181]
19 233 ms 233 ms 234 ms 12-122-254-238.attens.net [12.122.254.238]
20 256 ms 235 ms 232 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54]
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.

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 3105 ms 298 ms 99 ms 10.0.0.138
2 34 ms 36 ms 36 ms 172.18.208.5
3 34 ms 34 ms 33 ms 172.18.66.170
4 35 ms 35 ms 36 ms 172.18.239.229
5 41 ms 46 ms 36 ms bundle-ether10.chw48.sydney.telstra.net [203.45.17.13]
6 45 ms 36 ms 34 ms bundle-ether6.chw-core2.sydney.telstra.net [203.50.6.153]
7 40 ms 35 ms 35 ms bundle-ether4.ken-core4.sydney.telstra.net [203.50.6.41]
8 37 ms 36 ms 35 ms bundle-ether1.pad-gw2.sydney.telstra.net [203.50.6.29]
9 36 ms 36 ms 34 ms tengige10-0-0.sydp-core02.sydney.reach.com [203.50.13.94]
10 189 ms 188 ms 191 ms i-0-5-0-0.paix-core01.bx.telstraglobal.net [202.84.144.157]
11 746 ms 232 ms 217 ms i-0-4-0-3.paix02.bi.telstraglobal.net [202.84.251.106]
12 203 ms 238 ms 217 ms 206.24.240.149
13 226 ms 216 ms 1483 ms er2-xe-11-1-0.sanfrancisco.savvis.net [204.70.206.58]
14 268 ms 215 ms 249 ms pr2-ge-7-0-0.SanJoseEquinix.savvis.net [204.70.203.22]
15 712 ms 433 ms 1101 ms savvis-gw.sffca.ip.att.net [192.205.36.5]
16 258 ms 1185 ms * cr1.sffca.ip.att.net [12.122.137.126]
17 1182 ms 749 ms 3506 ms cr1.la2ca.ip.att.net [12.122.3.122]
18 262 ms 233 ms 233 ms gar20.la2ca.ip.att.net [12.122.128.181]
19 233 ms 234 ms 234 ms 12-122-254-238.attens.net [12.122.254.238]
20 232 ms 233 ms 234 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54]
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.
Edited by Vitrium#1877 on 2/6/2013 6:54 AM PST
Reply Quote
I ran a couple of traces while playing the other day (during terrible lag). I'm confused as to why D3 is the only online game I play that has these latency issues, very suspicious indeed.

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 33 ms 99 ms 99 ms 10.0.0.138
2 2379 ms 91 ms 92 ms 172.18.208.5
3 35 ms 34 ms 34 ms 172.18.66.170
4 39 ms 35 ms 35 ms 172.18.239.229
5 38 ms 35 ms 37 ms bundle-ether10.chw48.sydney.telstra.net [203.45.17.13]
6 45 ms 35 ms 35 ms bundle-ether6.chw-core2.sydney.telstra.net [203.50.6.153]
7 41 ms 35 ms 35 ms bundle-ether4.ken-core4.sydney.telstra.net [203.50.6.41]
8 46 ms 35 ms 35 ms bundle-ether1.pad-gw2.sydney.telstra.net [203.50.6.29]
9 115 ms 201 ms 1334 ms tengige10-0-0.sydp-core02.sydney.reach.com [203.50.13.94]
10 269 ms 353 ms 346 ms i-0-5-0-0.paix-core01.bx.telstraglobal.net [202.84.144.157]
11 188 ms 189 ms 188 ms i-0-4-0-3.paix02.bi.telstraglobal.net [202.84.251.106]
12 191 ms 191 ms 190 ms 206.24.240.149
13 190 ms 193 ms 221 ms er2-xe-11-1-0.sanfrancisco.savvis.net [204.70.206.58]
14 196 ms 192 ms 192 ms pr2-ge-7-0-0.SanJoseEquinix.savvis.net [204.70.203.22]
15 194 ms 193 ms 194 ms savvis-gw.sffca.ip.att.net [192.205.36.5]
16 236 ms 236 ms 235 ms cr1.sffca.ip.att.net [12.122.137.126]
17 238 ms 239 ms 236 ms cr1.la2ca.ip.att.net [12.122.3.122]
18 234 ms 244 ms 234 ms gar20.la2ca.ip.att.net [12.122.128.181]
19 233 ms 233 ms 234 ms 12-122-254-238.attens.net [12.122.254.238]
20 256 ms 235 ms 232 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54]
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.

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 3105 ms 298 ms 99 ms 10.0.0.138
2 34 ms 36 ms 36 ms 172.18.208.5
3 34 ms 34 ms 33 ms 172.18.66.170
4 35 ms 35 ms 36 ms 172.18.239.229
5 41 ms 46 ms 36 ms bundle-ether10.chw48.sydney.telstra.net [203.45.17.13]
6 45 ms 36 ms 34 ms bundle-ether6.chw-core2.sydney.telstra.net [203.50.6.153]
7 40 ms 35 ms 35 ms bundle-ether4.ken-core4.sydney.telstra.net [203.50.6.41]
8 37 ms 36 ms 35 ms bundle-ether1.pad-gw2.sydney.telstra.net [203.50.6.29]
9 36 ms 36 ms 34 ms tengige10-0-0.sydp-core02.sydney.reach.com [203.50.13.94]
10 189 ms 188 ms 191 ms i-0-5-0-0.paix-core01.bx.telstraglobal.net [202.84.144.157]
11 746 ms 232 ms 217 ms i-0-4-0-3.paix02.bi.telstraglobal.net [202.84.251.106]
12 203 ms 238 ms 217 ms 206.24.240.149
13 226 ms 216 ms 1483 ms er2-xe-11-1-0.sanfrancisco.savvis.net [204.70.206.58]
14 268 ms 215 ms 249 ms pr2-ge-7-0-0.SanJoseEquinix.savvis.net [204.70.203.22]
15 712 ms 433 ms 1101 ms savvis-gw.sffca.ip.att.net [192.205.36.5]
16 258 ms 1185 ms * cr1.sffca.ip.att.net [12.122.137.126]
17 1182 ms 749 ms 3506 ms cr1.la2ca.ip.att.net [12.122.3.122]
18 262 ms 233 ms 233 ms gar20.la2ca.ip.att.net [12.122.128.181]
19 233 ms 234 ms 234 ms 12-122-254-238.attens.net [12.122.254.238]
20 232 ms 233 ms 234 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54]
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.


Your results show local latency issues not offshore, you may have to get telstra bigpond adsl a call on tech support for them to run a lines test as the spike seems to be from a distribution point from the very first hop itself on your 2nd traceroute there. 10.0.0.138 is the standard point of termination for a bigpond adsl modem. Most notably if they are competent they should identify faults from the copper network and the ADSL port, ask them for a Lines test and sync rate RVOP result if they can email you that i can analyse it
Reply Quote
was wondering if anyone could analyse my latency problem thanks :)

1 7 ms 108 ms 90 ms dsldevice.lan [192.168.1.254]
2 21 ms 21 ms 20 ms 10.20.22-31.tpgi.com.au [10.20.22.31]
3 22 ms 22 ms 22 ms syd-pwk-dym-csw2-ge-1-16.tpgi.com.au [203.26.20.109]
4 21 ms 21 ms 20 ms syd-pwk-dym-crt1-ge-5-0-0.tpgi.com.au [203.29.135.141]
5 204 ms 203 ms 203 ms 219.158.39.17
6 434 ms 428 ms 439 ms 219.158.25.21
7 455 ms * 447 ms 219.158.97.154
8 414 ms 415 ms 411 ms 12.118.130.85
9 421 ms 425 ms 413 ms cr84.la2ca.ip.att.net [12.122.129.50]
10 420 ms 416 ms 416 ms cr2.la2ca.ip.att.net [12.123.30.250]
11 598 ms 406 ms 416 ms gar29.la2ca.ip.att.net [12.122.129.241]
12 413 ms 415 ms 416 ms 12.122.251.190
13 415 ms 414 ms 432 ms 206.16.68.46
14 * * *
Reply Quote
was wondering if anyone could analyse my latency problem thanks :)

1 7 ms 108 ms 90 ms dsldevice.lan [192.168.1.254]
2 21 ms 21 ms 20 ms 10.20.22-31.tpgi.com.au [10.20.22.31]
3 22 ms 22 ms 22 ms syd-pwk-dym-csw2-ge-1-16.tpgi.com.au [203.26.20.109]
4 21 ms 21 ms 20 ms syd-pwk-dym-crt1-ge-5-0-0.tpgi.com.au [203.29.135.141]
5 204 ms 203 ms 203 ms 219.158.39.17
6 434 ms 428 ms 439 ms 219.158.25.21
7 455 ms * 447 ms 219.158.97.154
8 414 ms 415 ms 411 ms 12.118.130.85
9 421 ms 425 ms 413 ms cr84.la2ca.ip.att.net [12.122.129.50]
10 420 ms 416 ms 416 ms cr2.la2ca.ip.att.net [12.123.30.250]
11 598 ms 406 ms 416 ms gar29.la2ca.ip.att.net [12.122.129.241]
12 413 ms 415 ms 416 ms 12.122.251.190
13 415 ms 414 ms 432 ms 206.16.68.46
14 * * *


Looking at yours you have local problems too there's a spike in lag on your modem IP already, TPG in general usually deal with high latency due to their congested demand of data dl customers.
Reply Quote
last night for the first time I had constant latency problems making the game unplayable. As I said this has never happened to me before, except for the occasional problem when first entering the game. I am on ADSL2 with Westnet, who are of course iinet.

Hope it isnt going to become a common thing.
Reply Quote
Same problem here. Started yesterday, a little better today but game can freeze for 3-4 seconds at a time.
Reply Quote
hopefully tonight's maintenance will FIX the LAG issue !!!!!!!!!!
Reply Quote
LLLAAAGGGG !!!
Reply Quote
Terrible lag tonight, what the efff!
Reply Quote
have had terrible lag all day, crysis 3 multiplayer runs perfectly though....
Reply Quote
90 Orc Death Knight
5445
yeah me 2 :/
Reply Quote
I set a new record last night, spiking to 11,000ms! Constant lag (haven't seen a green bar in weeks), disconnections, and weird episodes where I'm still running around, but nothing happens for up to a few minutes, then it all happens at once! I've tried every fix I could find, and it's still the same. I'm out of ideas, any suggestions?

Here's the tracert:

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 121 ms 132 ms 160 ms mas801.ba.optusnet.com.au [198.142.128.103]
3 173 ms 146 ms 125 ms mas1-ge10-0.gw.optusnet.com.au [198.142.144.49]
4 25 ms 33 ms 34 ms mas3-ge0-0.gw.optusnet.com.au [211.29.125.237]
5 283 ms 304 ms 332 ms 203.208.174.85
6 270 ms 191 ms 241 ms xe-3-2-0.lax20.ip4.tinet.net [77.67.79.9]
7 248 ms 322 ms 290 ms xe-2-2-2.lax30.ip4.tinet.net [89.149.187.110]
8 267 ms 266 ms 262 ms as7018.lax30.ip4.tinet.net [77.67.79.174]
9 332 ms 315 ms 328 ms cr2.la2ca.ip.att.net [12.122.129.106]
10 291 ms 215 ms 319 ms gar29.la2ca.ip.att.net [12.122.129.241]
11 240 ms 192 ms 221 ms 12-122-254-238.attens.net [12.122.254.238]
12 303 ms 308 ms 418 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
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]