What is going on?

Aus/NZ General Discussion
I've been able to play this game pretty well for the last few months without many latency problems but the last week or so 90% of the time I want to play I am unable to because my latency will spike into the thousands and my game will lock up. I have seen many posts with similar problems but not many answers or solutions.

WTF is going on? Why can I play other online games fine but I can't play Diablo 3 single player?

I'm with Bigpond in NSW

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 57 ms 97 ms 99 ms BigPond.BigPond [10.0.0.138]
2 24 ms 24 ms 24 ms 172.18.208.11
3 96 ms 86 ms 34 ms 172.18.92.6
4 24 ms 36 ms 35 ms 172.18.239.233
5 25 ms 35 ms 35 ms bundle-ether15.ken43.sydney.telstra.net [110.142.193.141]
6 36 ms 34 ms 36 ms bundle-ether9.ken-core4.sydney.telstra.net [203.50.11.30]
7 29 ms 34 ms 36 ms bundle-ether1.pad-gw2.sydney.telstra.net [203.50.6.29]
8 29 ms 25 ms 26 ms tengigabitethernet0-x.sydp-core02.sydney.reach.com [203.50.13.70]
9 163 ms 164 ms 180 ms i-0-3-0-4.paix-core01.bx.telstraglobal.net [202.84.140.157]
10 177 ms 164 ms 175 ms i-0-0-0-3.paix02.bi.telstraglobal.net [202.84.251.94]
11 259 ms 274 ms 272 ms 206.24.240.149
12 213 ms 215 ms 224 ms er2-xe-7-3-0.sjq.savvis.net [206.28.98.118]
13 206 ms 223 ms 204 ms pr2-ge-7-0-0.SanJoseEquinix.savvis.net [204.70.203.22]
14 237 ms 215 ms 215 ms savvis-gw.sffca.ip.att.net [192.205.36.5]
15 179 ms 177 ms 176 ms cr1.sffca.ip.att.net [12.122.137.126]
16 179 ms 180 ms 202 ms cr1.la2ca.ip.att.net [12.122.3.122]
17 181 ms 175 ms 175 ms gar20.la2ca.ip.att.net [12.122.128.181]
18 177 ms 177 ms 177 ms 12-122-254-234.attens.net [12.122.254.234]
19 188 ms 177 ms 176 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54]
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.
Hook us up with a trace route for when you're lagging mate so can see where the ping goes bad.

https://us.battle.net/support/en/article/performing-a-traceroute
________________________________________________
Twitter: @Narull | ANZ Diablo III MVP
http://us.battle.net/d3/en/forum/topic/6490399005 - Narull's Hardcore Challenge.
http://www.blizzposts.com - Keep track of all Official Blizzard posts.
There not spelling mistakes, Im speaking 'Ye Old English'
These trace routes do not reflect my experience in game, I can have 500+ latency in game and run the trace at the same time and get this result.....

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 20 ms 99 ms 99 ms BigPond.BigPond [10.0.0.138]
2 50 ms 24 ms 24 ms 172.18.208.11
3 23 ms 24 ms 23 ms 172.18.92.6
4 35 ms 35 ms 24 ms 172.18.239.233
5 36 ms 35 ms 35 ms bundle-ether15.ken43.sydney.telstra.net [110.142.193.141]
6 30 ms 35 ms 23 ms bundle-ether9.ken-core4.sydney.telstra.net [203.50.11.30]
7 28 ms 35 ms 35 ms bundle-ether1.pad-gw2.sydney.telstra.net [203.50.6.29]
8 25 ms 23 ms 25 ms tengigabitethernet0-x.sydp-core02.sydney.reach.com [203.50.13.70]
9 165 ms 163 ms 163 ms i-0-3-0-4.paix-core01.bx.telstraglobal.net [202.84.140.157]
10 164 ms 162 ms 162 ms i-0-0-0-3.paix02.bi.telstraglobal.net [202.84.251.94]
11 206 ms 212 ms 205 ms 206.24.240.149
12 211 ms 223 ms 212 ms er2-xe-7-3-0.sjq.savvis.net [206.28.98.118]
13 204 ms 203 ms 203 ms pr2-ge-7-0-0.SanJoseEquinix.savvis.net [204.70.203.22]
14 214 ms 214 ms 214 ms savvis-gw.sffca.ip.att.net [192.205.36.5]
15 182 ms 178 ms 178 ms cr1.sffca.ip.att.net [12.122.137.126]
16 179 ms 176 ms 176 ms cr1.la2ca.ip.att.net [12.122.3.122]
17 174 ms 174 ms 174 ms gar20.la2ca.ip.att.net [12.122.128.181]
18 174 ms * 173 ms 12.122.251.190
19 176 ms 175 ms 175 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54]
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.
Your first hop on your trace route shows

1 20 ms 99 ms 99 ms BigPond.BigPond [10.0.0.138]

to your modem
99ms is too high for 10.0.0.138

either somethings running in background or something on your end isn't right

my first few hops are like this

1 11 ms 9 ms 18 ms 10.204.96.1
2 18 ms 15 ms 9 ms 58.160.15.8
3 17 ms 18 ms 15 ms 58.160.15.238
4 12 ms 11 ms 11 ms 172.18.239.105

ideally nothing past 20 - 30 ms locally before it hops to offshore
might wanna call bigpond to see if there's any line faults in your network outside your street or local exchange congestion

On a consensus for investigation SPEED faults with bigpond i found alot of people are unaware what is causing actual network issue, some are even unaware of the internal setup inside the house are incorrect, eg phoneline extensions to modems causing signal lost , incorrect adsl filtering, or simply windows 7 doing a ninja update download in the background which the users cannot see and this happens almost nightly unless they disable the automatic update feature in windows 7 , others have people sharing the bandwidth with other users streaming tv etc.

Join the Conversation

Return to Forum