Diablo3 is suddenly lagging real bad

Aus/NZ General Discussion
hey everyone i just wanted to get an idea if theres any other Aussies experiencing this?

Im with DoDo adsl2 ive never had a problem playing Diablo 3 lag wise u until about 3 or 4 days ago now its unplayable its just choppy as then after bout a minute it just lags out for 30 seconds at a time...Anything getting the same??
Yeah I can't play either
has this only just happeed to you as well?
been happening for a couple of weeks on and off since there has been that issue with the international cable to singapore.
But I agree today is one of the worst days. been lagging since midday everytime i checked... and its my day off too :(
Where are you guys living? I know with the floods Queensland is having net issues in many places.

But if outside of Qld you may want to check your routing by doing a trace route, see where it's lagging.

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'
For the first time the game is unplayable for me due to lag, I'm in NSW with bigpond.
Yeah, me too. I'm regularly getting latency > 400 ms. Last night it was sometimes over a second. Makes playing a HC character a bit interesting...

Newcastle, NSW. Telstra. Gaming PC plugged into router. Top end machine all up to date.
Yeah, me too. I'm regularly getting latency > 400 ms. Last night it was sometimes over a second. Makes playing a HC character a bit interesting...

Newcastle, NSW. Telstra. Gaming PC plugged into router. Top end machine all up to date.


If you want ring the tech support which i coach to enquire on 133933 this goes to the phillipines but if trained properly they should understand how to look up your network element if this fails ask them to raise a escalation and give you a case reference number which i can follow up from my end.

Services outside of QLD in NSW affected by the weather conditions is Tweed Heads, Byron Bay and Bilambil Heights off the top of my head from todays outage report no ETR yet and those sites are inhanded with the global operations centre. From what i last remembered as those exchanges had their main power cut off from the exchange node devices and ports.

I am willing to assist Bigpond customers with their enquiries for other ISPs policy and process prohibits me to directly handle unless the ISP escalates it to Telstra themselves.
Well, I am unsure if this is Aus/NZ only issue. I am a player in a country that close to yours and also noticed high-latency while playing in U.S. server 4 days ago (also that 3007 error).
It differs from service to service and broadband type, with ADSL benchmarking the service is always un-equal because network wise the last mile is subjective with cable run distance, signal lost and all sorts of faults.

I barely have the issues people here complain about but i did have the same issues when i was with ADSL, i switched to HFC (hybrid fibre coaxial) with bigpond and never had a issue since as it doesn't have the same weakness as adsl and has fibre speeds of up to 100mbits. my ping over the weekend has been a constant 180-195ms with one other player in the same house at the same time.

If possible try to request a RVOP test result from your service providor as well it can give more insight to your service parameters normal traceroutes don't.
I'm in Rockhampton, QLD, where Telstra were affected by the floods. Internet and communications services are back up however, and seems to be at normal speeds.

D3 has been frequently jumping to latencies of 400+ for up to 30 seconds, before dropping to under 300ms.

There are also still congestion issues in the network. The fixes put in recently were temporary. A permanent fix will be put in soon.
Yeah Im getting stuttering here in SYD NSW, using Telstra 4g service, has been choppy for the last 3 days, I would not initailly think this is an ISP as the AH issue seemed to be tied to choppy game play.

Hey Narull isn't there maintenance today?
yes the lag is so bad I sometimes cant pick up gold or drops
Yeah Im getting stuttering here in SYD NSW, using Telstra 4g service, has been choppy for the last 3 days, I would not initailly think this is an ISP as the AH issue seemed to be tied to choppy game play.

Hey Narull isn't there maintenance today?


I logged in just now to check i have between 183-195 ping not reaching 200 at all so im pretty stable,

From a professional opinion, mobile wireless broadband is not recommended for gaming and i know they sell it that way to customers unfortunately mobile broadband is pretty much up in the air literally at times of spikes and congestion they have zero guarantee of stability because the service is not a fixed line signal. I know in terms of coverage and mobile towers Telstras 4G is second to none thats because they have the most coverage and have higher bandwidth capacity compared to the 4G optus is rolling out on their towers.

I work on TIO escalations from a back end for broadband issues on a daily basis including technology involved with networks from exchange equipment based on alcatel next gen which is pretty much deployed nationally for adsl , Fibre to the node, and fibre to the premises. many times people have misconceptions about adsl faults and services including our very own offshore tech support. Especailly how two people paying for a the same bigpond plan on ADSL2+ etc could get getting different speeds from their ends. First of all bad latency is fractionally due to because servers are offshore but not all the blame is on that. If your serious about low latency the options is to consider is.

Top two options
HFC / Cable network connection delivers highest bandwidth without the issue fixed phone like ADSL. This is preferred if you have network coverage in your area.. see who has foxtel cable down your street or call up to enquire.

FTTP (Fibre to the premises) / NBN (National Broadband Network)
The new technology a hair strand of glass coated with a reflective barrier to emit signals at the speed of light.
The global standard of broadband which australia is just starting to adopt, Fibre does not share the same weakness as adsl copper networks, can feed to a distance of 22km of fibre cable run from distribution port and for now at a capped speed of up to 100mbits bitrate thats more than 4 times of peak ADSL2+. Unfortunately only selected areas have rollouts and the NBN is taking it sweet time to replace all copper ADSL network nationally.

ADSL2+*
- now this is subjective ADSL2+ advertises up to 24mbits, you notice it says UP TO because ADSL2+ signals rely on being closer to your port or exchange to be really strong the further your house is away from the source the more signal lost , drop outs and slow speeds you get, so for example if you have the same ADSL2+ broadband as a friend and benchmark it however your friend practically lives next to the exchange and you live about 4 kms of cable run away your service will only reach a maximum of maybe 3-5mbits bitrate while your friend next to the local exchange gets 20mbits and yet you both pay the same plan and price. Much too often i see this concept never fully explained to the public but its the dirty dirty secret of selling the service to those not technically savvy in broadband techs. On top of that ADSL is heavily affected by congestion especailly on peak periods when everyones home and also copper network faults outside on the street when the pipes are flood and gel joints are wet. If you ever ring up your service provider and if they have consultants trained in network frequency and testing they can provide you a inside of how far your service is exactly from your exchange normally most adsl are poor from 4-5kms of cable run. This is a exception to telstra TOPhats which are fibre to the nodes technically bringing out the exchange closer to your house in a way.
latency issues kicked in shortly this afternoon, went from an average 300ms to now a spiking 2500 ms and an average of 800-1000ms. On BigPond Cable, checked the service status they are as follows for my area in Sydney 2220, so shouldn't be affecting myself.

State: New South Wales
Service: ADSL
Description: Some ADSL services may be unavailable.
Time start: 28-01-2013 15:30
Time end:
Hello Hello. Welcome to (GAME OF LAG 3) Nothing new to see here.
anyone actually took narulls advice on running the trace route to provide foundation that blizzard need to take a look at. I'm all for fist pumping and stomping when i have a complaint but sometimes you gotta back it up.

if your using windows 7 its easy bring up command prompt and type in
tracert 12.129.209.68 > desktop\tracert.txt

a file will appear on your desktop with the results

for example mine is
Tracing route to 12.129.209.68 over a maximum of 30 hops

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
5 32 ms 12 ms 23 ms bundle-ether13.chw53.sydney.telstra.net [110.142.193.145]
6 15 ms 24 ms 11 ms bundle-ether9.chw-core2.sydney.telstra.net [203.50.11.26]
7 22 ms 23 ms 23 ms bundle-ether4.ken-core4.sydney.telstra.net [203.50.6.41]
8 17 ms 12 ms 15 ms bundle-ether1.pad-gw2.sydney.telstra.net [203.50.6.29]
9 21 ms 11 ms 13 ms tengigabitethernet2-0.sydp-core02.sydney.reach.com [203.50.13.50]
10 152 ms 148 ms 164 ms i-0-4-0-0.paix-core01.bx.telstraglobal.net [202.84.140.37]
11 164 ms 160 ms 152 ms i-0-0-0-2.paix02.bi.telstraglobal.net [202.84.251.101]
12 167 ms 171 ms 172 ms 206.24.240.149
13 176 ms 169 ms 169 ms er2-xe-3-1-0.SanJoseEquinix.savvis.net [204.70.200.197]
14 169 ms 169 ms 172 ms pr2-ge-7-0-0.SanJoseEquinix.savvis.net [204.70.203.22]
15 173 ms 174 ms 175 ms savvis-gw.sffca.ip.att.net [192.205.36.5]
16 185 ms 171 ms 175 ms cr1.sffca.ip.att.net [12.122.137.126]
17 174 ms 180 ms 171 ms cr1.la2ca.ip.att.net [12.122.3.122]
18 172 ms 181 ms 177 ms gar20.la2ca.ip.att.net [12.122.128.181]
19 182 ms 172 ms 170 ms 12-122-254-238.attens.net [12.122.254.238]
20 171 ms 178 ms 171 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.

As you can see my results are in the green at the 170-185 ms at the blizzard side on attens.net the rest of the results towards the end times out due to defence mechanisms which is already explained on the link narull gave.

to test ISP end and your network termination point request your service provider to run a service test and email you the result in sync parameter values for attenuation , bitrate , noise margin, expected attenuation as per SQ cable run for ADSL services

High attenuation values = poor service
ADSL fails at 56dB and drops out intermittently
Noise margin for ADSL 2/2+ should be 6dB and above

Also request them to run a lines test on the outside network for
Foreign battery, Resistance to Ground and imbalance all which affects service quality on adsl which are most noticible in low latency demand games and high data streaming movies.

It seems people that don't encounter lag issue will never come in here to testify so blizzard will never use it as a equal gauge that there is a problem unless people start posting test results on both user end and trace routes.

Just wondering what the result you guys get in here.

I'm in sydney, inner suburbs 2166 on Hybrid fiber-coaxial bigpond with a wideband capacity of 100mbits max. Not seeing the issues you guys are and playing on american servers as well that traceroute is the IP of the american servers
To give some positive feedback, I'm in AKL NZ and not having any major problems.
In fact I actually run better when not using something like pingzapper.
I did have a problem for a day last week, but pingzapper cleared that up until things settled down more.
latency really bad this week guys. lag kills all the time!

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 11 ms 12 ms 19 ms 10.213.160.1
2 18 ms 7 ms 9 ms CPE-58-175-61-14.vic.bigpond.net.au [58.175.61.14]
3 14 ms 10 ms 10 ms 58.160.7.226
4 19 ms 23 ms 35 ms 172.18.240.105
5 23 ms 23 ms 11 ms bundle-ether10.lon76.melbourne.telstra.net [110.142.226.45]
6 18 ms 21 ms 11 ms bundle-ether6.exi-core1.melbourne.telstra.net [203.50.11.56]
7 30 ms 23 ms 34 ms bundle-ether12.chw-core2.sydney.telstra.net [203.50.11.74]
8 32 ms 34 ms 35 ms bundle-ether4.ken-core4.sydney.telstra.net [203.50.6.41]
9 24 ms 35 ms 36 ms bundle-ether1.pad-gw2.sydney.telstra.net [203.50.6.29]
10 28 ms 27 ms 34 ms 203.50.13.118
11 173 ms 186 ms 168 ms i-0-4-0-0.paix-core01.bx.telstraglobal.net [202.84.140.37]
12 163 ms 165 ms 191 ms i-0-0-0-3.paix02.bi.telstraglobal.net [202.84.251.94]
13 222 ms 223 ms 218 ms 206.24.240.149
14 197 ms 198 ms 234 ms er2-xe-3-1-0.SanJoseEquinix.savvis.net [204.70.200.197]
15 200 ms 200 ms 211 ms pr2-ge-7-0-0.SanJoseEquinix.savvis.net [204.70.203.22]
16 176 ms 182 ms 198 ms savvis-gw.sffca.ip.att.net [192.205.36.5]
17 294 ms 204 ms 204 ms cr1.sffca.ip.att.net [12.122.137.126]
18 199 ms 204 ms 204 ms cr1.la2ca.ip.att.net [12.122.3.122]
19 213 ms 203 ms 207 ms gar20.la2ca.ip.att.net [12.122.128.181]
20 180 ms 177 ms 200 ms 12-122-254-234.attens.net [12.122.254.234]
21 177 ms 193 ms 189 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
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.

Join the Conversation

Return to Forum