Diablo® III

[NEW] 3/13 - Issues Creating Game / Latency Reports

(Locked)

Toronto, Canada, same issue as everyone else, HIGH latency 1300+ totally unplayable, its been a few days already!

Bell, Fibe

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 13 ms 13 ms 14 ms bas5-toronto21_lo0_SYMP.net.bell.ca [64.230.8.16
6]
3 13 ms 12 ms 12 ms agg3-toronto21_7-1-0_100.net.bell.ca [64.230.103
.96]
4 83 ms 25 ms 70 ms bx5-chicagodt_xe-0-0-3_0.net.bell.ca [64.230.186
.106]
5 24 ms 24 ms 23 ms 12.249.212.9
6 88 ms 93 ms 90 ms cr1.cgcil.ip.att.net [12.122.99.22]
7 90 ms 91 ms 88 ms cr2.dvmco.ip.att.net [12.122.31.85]
8 91 ms 86 ms 87 ms cr1.slkut.ip.att.net [12.122.30.25]
9 90 ms 95 ms 91 ms cr2.la2ca.ip.att.net [12.122.30.30]
10 148 ms 198 ms 88 ms gar20.la2ca.ip.att.net [12.122.128.181]
11 88 ms 89 ms 88 ms 12-122-254-234.attens.net [12.122.254.234]
12 87 ms 90 ms 90 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.12
9.193.254]
13 89 ms 89 ms 87 ms 12.129.209.68

Trace complete.
03/14/2014 06:46 PMPosted by Lylirra
03/14/2014 06:31 PMPosted by ZaPLaS
Freaking game is unplayable and they ask what kind of latency?


Not all players are experiencing latency. As a result, this means it's not a global issue (i.e. something affecting everyone who logs in) and will require more troubleshooting to identify the exact cause. This is what we're doing by asking for the kind of latency you're experiencing, where you're playing from, and what ISP you're using. The additional information provides us a clearer, more accurate understanding of what's happening, particularly in situations where not all players are having problems and where we're unable to replicate the scenario internally.

For some players, it seems that the increased latency may due to an issue with a specific ISP. (This may be something that's out of hands, but we're still seeing what we can do.) For others not on the same ISP, we're still troubleshooting. Latency isn't a binary kind of thing and can be caused by a litany of different sources. The extra info you all are providing in response to my questions certainly help. :)


Yes you got it, our ISP is conspiring to stop us playing D3 (but allowing us to use clan chat and party chat cause they feel sorry for us). They allow me to play any other game, they allow me to download 1 GB files in seconds, they allow me to play other Bliz games. But they are tired of D3 and its portrayal of hell as a pretty awesome place, so they are finally taking action on behalf of Christians everywhere!!!
Edited by Justinian#1480 on 3/14/2014 6:57 PM PDT
I have given it a few hours...well actually it has been five days now.

But my latency is 900+. I can be sitting in town, or trying to run with clan members. It doesn't matter.

I did the trace sent it off, and all the suggestions for fixes including dnsflush.

Cannot create or join games as of a few minutes ago, so my issue is getting worse not better.

Bell, Ontario Canada.

It is not my ISP. I can play other games, GW2, POE, I can play live on Xbox one.

I pre-ordered this game, despite the problems D3 had, because it looked like you were headed in the direction of fixing many of the issues. because I have always liked the Diablo franchise. I wanted to get my toons ready for expansion. But this week has been brutally bad, with the last two nights the worst. Now I am starting to feel like I have been duped into to continuing on with this game. It is unplayable, and the most recent blue post suggesting that it might be my ISP, when all other internet activities are just fine is just another low blow.
There seems to be a general issue for players within Ontario/Quebec, Canada. More specifically on ISP Bell Fibe.

I am curious about this quote "This may be something that's out of hands"

In my opinion this certainly isn't out of hands since I am not having any issues with my connection anywhere else. If the route between your servers and Bell Fibe has issues this has to be addressed by you since your customers are paying you for a game that has to be playable. I am paying Bell Fibe for a connection which IS working everywhere else.

I am aware these issues take time to resolve, just don't like the idea of you guys trying to blame someone else so it can be out of your hands.
Montreal, Canada as well and this is my tracert with a different ISP (Videotron). I'm not experiencing lag/latency/rubberbanding tonight but thought this might be useful since we're using the same routes.

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 * * * Request timed out.
3 10 ms 11 ms 11 ms 10.170.172.113
4 12 ms 10 ms 10 ms 216.113.126.66
5 125 ms 9 ms 9 ms 216.113.122.218
6 * * * Request timed out.
7 17 ms 29 ms 16 ms if-2-2.tcore2.NYY-New-York.as6453.net [64.86.226.14]
8 19 ms 16 ms 15 ms if-11-2.tcore1.NYY-New-York.as6453.net [216.6.99.2]
9 16 ms 16 ms 17 ms if-5-5.tcore1.NTO-New-York.as6453.net [216.6.90.6]
10 15 ms 17 ms 15 ms 63.243.128.70
11 18 ms 23 ms 19 ms 192.205.35.21
12 91 ms 91 ms 94 ms cr1.n54ny.ip.att.net [12.122.131.94]
13 88 ms 90 ms 87 ms cr2.cgcil.ip.att.net [12.122.1.2]
14 91 ms 89 ms 87 ms cr1.cgcil.ip.att.net [12.122.2.53]
15 110 ms 116 ms 121 ms cr2.dvmco.ip.att.net [12.122.31.85]
16 92 ms 91 ms 88 ms cr1.slkut.ip.att.net [12.122.30.25]
17 92 ms 91 ms 90 ms cr2.la2ca.ip.att.net [12.122.30.30]
18 88 ms 86 ms 91 ms gar20.la2ca.ip.att.net [12.122.128.181]
19 89 ms 89 ms 87 ms 12.122.251.190
20 88 ms 89 ms 87 ms 206.16.68.46
21 89 ms 89 ms 87 ms 12.129.199.178
22 87 ms 87 ms 88 ms 12.129.209.68

Trace complete.
Quebec/Canada
Bell

Called bell, they said they couldn't do anything about it.

So if I'm reading things right apperently everyone lags because XO communications are complete morons that can't re-routes elsewhere beside chicago AT&T.

Cool story.
i notice a serious trend it is with Bell internet.

I am also with bell and have these issues
ISP : China Telekom
Country : Shenzhen China

The problem i experienced are;

1. ping jumps from 250ms to 1900ms
2. screen stuck, need to leave game and rejoin (screen stuck 4-5 times during a 3 hours play)
3. rubberbanding monsters and skill ( i press attack button but nothing is dishing out, need to wait 10- 15 sec sometimes for the attack to work, if not i need to rejoin game)

P/S: i played D3 since it first launched and stoped for awhile untill this RoS was comming soon. I never encounter this crazy lag in the past. Yes i know, i am playing from far away and my ISP issue does concern and it's fine with me to play with 250 - 290 ms ping.

sorry for my bad english

Edit: traceroute

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 172.16.192.1
2 1 ms 1 ms 1 ms 192.168.133.5
3 2 ms 1 ms 1 ms 121.15.212.222
4 2 ms 2 ms 2 ms 58.60.24.185
5 9 ms 3 ms 5 ms 121.15.179.94
6 8 ms 7 ms 7 ms 121.34.242.230
7 6 ms 6 ms 6 ms 202.97.33.170
8 6 ms 7 ms 5 ms 202.97.34.94
9 178 ms 179 ms 179 ms 202.97.58.226
10 167 ms 167 ms 163 ms 202.97.50.26
11 239 ms 230 ms 229 ms 218.30.54.170
12 279 ms 280 ms 251 ms cr1.la2ca.ip.att.net [12.123.30.18]
13 271 ms 394 ms 275 ms gar20.la2ca.ip.att.net [12.122.128.181]
14 276 ms 274 ms 257 ms 12-122-254-234.attens.net [12.122.254.234]
15 257 ms 267 ms 273 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
16 239 ms 244 ms 253 ms 12.129.199.178
17 279 ms 256 ms 236 ms 12.129.209.68

Trace complete.
Edited by HaruuuX#6436 on 3/14/2014 7:10 PM PDT
Community Manager
03/14/2014 06:59 PMPosted by xander514
I am aware these issues take time to resolve, just don't like the idea of you guys trying to blame someone else so it can be out of your hands.


Given that we're looking into the reports from our end (not dismissing them) and reaching out to Bell, it's both unfair and inaccurate to say we're trying to pass the buck. I was just being transparent and very up front about the fact that there are some situations where we're unable to assist with ISP-based or -related issues. Hopefully, this isn't one of them and we can get that high latency for Bell users* resolved sooner rather than later.

*As noted previously, we're still troubleshooting possible causes of high latency for non-Bell users, too. Please keep providing your answers to my previous questions, as this can help quite a bit!
Edited by Lylirra on 3/14/2014 7:18 PM PDT
i just have talk with technical suport from bell and they config that dont come from they side all of my
speed on my connection is perfect.
And like i said earlier all other blizz game work perfectly WoW and heart stone.
Edited by dramatik#1909 on 3/14/2014 7:09 PM PDT
Im in Montreal, Canada with Bell fibe too and im pissed. It all started at patch 2.0.3
I am experiencing latency while I am playing the game, for example, casing spells and walking. And the latency makes me impossible to play the game anymore.

I am connecting from Boston, MA using Comcast as ISP.

Please help us :)
So Lylirra do u think Blizzard can fixed it for all Bell Fibe user staying in Québec and Ontario because for me all was ok before the patch 2.0.3 never had a problem with latency since this patch. So the problem is not here as per me. Confirm it plse.
it isnt just bell. I am a charter user
03/14/2014 07:01 PMPosted by Rancilkz
Quebec/Canada
Bell

Called bell, they said they couldn't do anything about it.

So if I'm reading things right apperently everyone lags because XO communications are complete morons that can't re-routes elsewhere beside chicago AT&T.

Cool story.


Are you an internetwork backbone engineer? What certifications do you have?
03/14/2014 07:06 PMPosted by Lylirra
03/14/2014 06:59 PMPosted by xander514
I am aware these issues take time to resolve, just don't like the idea of you guys trying to blame someone else so it can be out of your hands.


Given that we're looking into the reports from our end (not dismissing them) and reaching out to Bell, it's both unfair and inaccurate to say we're trying to pass the buck. I was just being transparent and very up front about the fact that there are some situations where we're unable to assist with ISP-based issues. Hopefully, this isn't one of them and we can get that high latency for Bell users* resolved sooner rather than later.

*As noted previously, we're still troubleshooting possible causes of high latency for non-Bell users, too. Please keep providing your answers to my previous questions, as this can help quite a bit!


well it should be fixable since this only started with the last patch
I am in Singapore, with M1 fibre and I am getting the insane latency problems too. The game is hardly playable. All these started after the patch. Obviously it ain't issues with the ISP if Blizz is willing to admit. If everything breaks after a patch, common sense would tell us that the problem lies with something within the patch.
Are you an internetwork backbone engineer? What certifications do you have?
No, I just read post on this thread and the other thread, and everything just seems to mess up once it reaches AT&T route in chicago.
Edited by Rancilkz#1515 on 3/14/2014 7:16 PM PDT
Latency starting to spike in-game again, going from 100ms stable spiking to 300-500 for about ten seconds, on and on and on.
This topic is locked.

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]