Diablo® III

iinet/WA lag

I thought it was just me, but the iinet looking glass is getting the same thing
normally get around 280ms which is only just playable, 350+ is not :(

http://looking-glass.iinet.net.au/lg/

Tracing the route to us.battle.net (12.129.242.40)

1 gi3-35.per-qv1-bdr1.iinet.net.au (203.215.4.43) 0 msec 4 msec 0 msec
2 ae6-10.cr1.per2.on.ii.net (150.101.33.90) 4 msec 0 msec 5 msec
3 ae0.cr1.per1.on.ii.net (150.101.33.12) 4 msec 0 msec 0 msec
4 ae3.br1.syd7.on.ii.net (150.101.33.30) 56 msec 56 msec 56 msec
5 te0-2-1-2.br1.sjc2.on.ii.net (150.101.33.147) 212 msec 213 msec 208 msec
6 sl-st31-sj-.sprintlink.net (144.232.191.193) 320 msec 325 msec 328 msec
7 144.232.1.70 293 msec 273 msec 268 msec
8 cr1.sffca.ip.att.net (12.122.200.10) 289 msec 301 msec 312 msec
9 cr1.la2ca.ip.att.net (12.122.3.122) 341 msec 336 msec 321 msec
10 gar20.la2ca.ip.att.net (12.122.128.181) 308 msec 364 msec 321 msec
11 12.122.251.190 304 msec
12-122-254-238.attens.net (12.122.254.238) 316 msec 313 msec
12 206.16.68.46 324 msec
mdf001c7613r0004-gig-10-1.lax1.attens.net (12.129.193.250) 325 msec
mdf001c7613r0002.lax1.attens.net (206.16.68.54) 316 msec

i can't tell from that if the routing path has changed.
anyone else from WA getting lag only just now?
Edited by brenzA#6648 on 10/7/2013 4:25 AM PDT
Reply Quote
Let me check.

Edit.

1 gi3-35.per-qv1-bdr1.iinet.net.au (203.215.4.43) 4 msec 0 msec 0 msec
2 ae6-10.cr1.per2.on.ii.net (150.101.33.90) 0 msec 4 msec 4 msec
3 ae0.cr1.per1.on.ii.net (150.101.33.12) 36 msec 16 msec 8 msec
4 ae3.br1.syd7.on.ii.net (150.101.33.30) 60 msec 56 msec 56 msec
5 te0-2-1-2.br1.sjc2.on.ii.net (150.101.33.147) 213 msec 212 msec 212 msec
6 sl-st31-sj-.sprintlink.net (144.232.191.193) 317 msec 316 msec 321 msec
7 144.232.1.70 292 msec 296 msec 305 msec
8 te0-2-1-2.br1.sjc2.on.ii.net (150.101.33.147) 208 msec
cr1.sffca.ip.att.net (12.122.200.10) 309 msec 308 msec
9 cr1.la2ca.ip.att.net (12.122.3.122) 333 msec 336 msec 333 msec
10 gar20.la2ca.ip.att.net (12.122.128.181) 332 msec 329 msec 333 msec
11 12.122.251.190 304 msec 305 msec
12-122-254-234.attens.net (12.122.254.234) 304 msec
12 mdf001c7613r0003-gig-12-1.lax1.attens.net (12.129.193.254) 328 msec
206.16.68.46 329 msec
mdf001c7613r0002.lax1.attens.net (206.16.68.54) 304 msec

320-350 ping is pretty normal for myself to battle.net
Edited by Asmodeous#1189 on 10/7/2013 5:25 AM PDT
Reply Quote
Better than the constant disconnects I was getting earlier (Brisbane).
Reply Quote
in rural wa, use TPG hardly ever goes over 300.
Reply Quote
Doesn't matter who you are with. If you live in Aus/NZ you will lag.
Reply Quote
The lag issues since the patch on Friday night are also impacting US based players; http://us.battle.net/d3/en/forum/topic/10196090525
Most of them are suffering consistent latency over 100ms!
This makes hardcore and group completely unplayable, there were even a few who posted trace routes showing pings over 250ms!! These poor souls have had to abandon playing altogether until Blizz fix their routing.
Reply Quote
The lag issues since the patch on Friday night are also impacting US based players; http://us.battle.net/d3/en/forum/topic/10196090525
Most of them are suffering consistent latency over 100ms!
This makes hardcore and group completely unplayable, there were even a few who posted trace routes showing pings over 250ms!! These poor souls have had to abandon playing altogether until Blizz fix their routing.

Been playing with 200~400ms pings forever. And the regular lag spikes on weekend evenings. Damn those lucky bastards.
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)

Reported!

[Close]