Diablo® III

Australia - Sydney - TPG : Latency really bad

Since the patch 1.0.6, the game becoming really lagging(network wise). I am located at Sydney with TPG. Before the patch , always around 230ms - 280ms(Green). Since the patch rolled out, i am having 600ms - 1203ms(Red) during the sydney day time from 8am - 10pm. Getting back to playable latency (around 300ms - 400ms) after 10pm till 8am the next day morning.

Anyone has the same issues here?
Reply Quote
I just decided to venture into the forum to check if I was alone. I'm kinda glad I'm not.

TPG Sydney here and problem started about 3 hours ago. I was doing my usual Ubers runs and suddenly got DCed. When I came back it was completely unplayable with ping reaching over 2k ms.

I rang TPG after doing a power cycle that did nothing, and they ran they usual tests. Results were all fine but still can't play at all.

I'm also having issues watching NBA TV which won stream above 400 kbps at all.

Something is seriously wrong but I just don't know what it is.

At least now I know the problem isn't simply at my end.
Reply Quote
TPG +1
Lag started in the afternoon and gotten worst at night, unplayable now . My friend is with internode and he's having no problems : (
Reply Quote
Tpg Adelaide Lag makes unplayable about 2 hours now
Reply Quote
Lag up to 2300ms TPG Adelaide
Reply Quote
Thanks for the confirm mate, Glad i am not the only one.
Reply Quote
Pretty bad now, around 2000ms + , can't really do anything. Called TPG as well and did all those stupid "ISOLATION TEST" by simply restart router .etc.
Reply Quote
Let's hope the problem magically solves itself tomorrow because otherwise I will have to look into changing ISP.
Reply Quote
+1 same issues all afternoon, cant play at all :( hope its fixed tomorrow
Reply Quote
Well the problem persists. What now?
Reply Quote
Just died 4 times in succession due to lag >1300. I'm with Bigpond so maybe changing ISPs from TPG won't fix anything. Seems to be a game issue that keeps coming back to haunt us in Oz.
Reply Quote
Interesting. Did you Bigpond issue also start yesterday evening?

It's not just limited to Diablo3 though. I also can't stream properly anymore from NBA.TV

I wonder if it's some DNS issue?
Reply Quote
Interesting. Did you Bigpond issue also start yesterday evening?

It's not just limited to Diablo3 though. I also can't stream properly anymore from NBA.TV

I wonder if it's some DNS issue?

Yesterday was fine and seems ok again now. Lag issues are very intermittent (and one of the reasons I gave up playing hardcore).
Reply Quote
Then your problem is different. I had zero lag spikes for over 8 months and it suddenly became unplayable.
Reply Quote
Well... I did 2 things and the problem is now solved. Not sure which one fixed it:

1 - Installed all critical Windows Updates

2 - Undone my IPV4 settings which I had set to 8.8.8.8 when that error 3007 started with new patch. Changed it back to auto detect DNS

I have a feeling it was solved by the latter but just do both.

Good luck!
Reply Quote
Well... I did 2 things and the problem is now solved. Not sure which one fixed it:

1 - Installed all critical Windows Updates

2 - Undone my IPV4 settings which I had set to 8.8.8.8 when that error 3007 started with new patch. Changed it back to auto detect DNS

I have a feeling it was solved by the latter but just do both.

Good luck!

Thanks for the advice. I had already changed my IPV4 settings back but will check windows updates later. Problem only occurred this morning with one elite pack which was a bit strange.
Reply Quote
Never mind. It only solved the NBA.TV problem.

Somehow D3 is still laggy.
Reply Quote
TPG, Sydney. Lag is bad for me too, its around 2000ms at the moment, usually its around 200-300
Reply Quote
Hi, just thought I'd chip in and say I've had terrible latency (>1s), only started today, never had anything like it before. TPG Adelaide.
Reply Quote
Hello, I agree this issue is happening since the patch 1.0.6, but not necessarily with a specific ISP (such as TPG).

I am currently with TPG, but don’t see any major latency from the last TPG hop(avg 380ms).

Hoping the blizzard support team to address this issue asap. Just to isolate the root cause, I am posting the followings:

C:\Windows\system32>netstat -b

Active Connections

Proto Local Address Foreign Address State
TCP 10.10.10.29:52154 12.130.244.193:1119 ESTABLISHED
[Diablo III.exe]
TCP 10.10.10.29:52162 12.130.247.17:1119 ESTABLISHED
[Diablo III.exe]

C:\Windows\system32>tracert 12.130.244.193

Tracing route to 12.130.244.193 over a maximum of 30 hops

1 1 ms 1 ms 2 ms 10.*.*.*
2 4 ms 2 ms 2 ms 192.*.*.*
3 24 ms 16 ms 17 ms 10.*.*.*
4 23 ms 18 ms 17 ms syd-pwk-dym-csw1-ge-1-16.tpgi.com.au [203.26.20.105]
5 16 ms 17 ms 16 ms 203.29.135.181
6 38 ms 27 ms 41 ms 203-26-22-065.static.tpgi.com.au [203.26.22.65]
7 379 ms 379 ms 380 ms te0-0-0-19.ccr21.lax04.atlas.cogentco.com [38.104.210.9]
8 * 381 ms 382 ms te0-3-0-7.ccr21.lax01.atlas.cogentco.com [154.54.1.9]
9 379 ms 383 ms * te0-6-0-4.ccr21.lax05.atlas.cogentco.com [154.54.82.150]
10 381 ms * 381 ms te0-7-0-35.ccr22.lax05.atlas.cogentco.com [154.54.28.70]
11 418 ms 410 ms 407 ms 192.205.37.157
12 453 ms 429 ms 418 ms cr1.la2ca.ip.att.net [12.122.84.202]
13 419 ms * * gar20.la2ca.ip.att.net [12.122.128.181]
14 422 ms * 413 ms 12.122.251.190
15 456 ms 441 ms 455 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
16 * * * Request timed out.
^C
C:\Windows\system32>
Edited by chocobo#6591 on 12/28/2012 12:40 AM PST
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]