Diablo® III

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

(Locked)

Massachusetts
Comcast
Issue: Can't create games (1/2 fail still)

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms The [192.168.1.1]
2 * * * Request timed out.
3 12 ms 11 ms 14 ms te-0-1-0-2-sur01.westroxbury.ma.boston.comcast.n
et [68.87.152.81]
4 11 ms 11 ms 11 ms be-20-ar01.needham.ma.boston.comcast.net [68.85.
106.21]
5 31 ms 26 ms 18 ms he-2-6-0-0-cr01.newyork.ny.ibone.comcast.net [68
.86.93.33]
6 * * * Request timed out.
7 19 ms 19 ms 19 ms 192.205.37.33
8 92 ms 91 ms 90 ms cr1.n54ny.ip.att.net [12.122.131.86]
9 92 ms 91 ms 91 ms cr2.cgcil.ip.att.net [12.122.1.2]
10 94 ms 91 ms 90 ms cr1.cgcil.ip.att.net [12.122.2.53]
11 92 ms 92 ms 90 ms cr2.dvmco.ip.att.net [12.122.31.85]
12 91 ms 91 ms 90 ms cr1.slkut.ip.att.net [12.122.30.25]
13 94 ms 90 ms 91 ms cr2.la2ca.ip.att.net [12.122.30.30]
14 132 ms 89 ms 90 ms gar20.la2ca.ip.att.net [12.122.128.181]
15 89 ms 88 ms 89 ms 12-122-254-234.attens.net [12.122.254.234]
16 89 ms 91 ms 235 ms 206.16.68.46
17 90 ms 90 ms 91 ms 12.129.199.178
18 90 ms 91 ms 89 ms 12.129.209.68
For the 11h45 PST update that requested trace route. Here's mine.

ISP: Bell Canada
St-Eustache, Quebec, Canada

Détermination de l'itinéraire vers 12.129.209.68 avec un maximum de 30 sauts.

1 1 ms 1 ms 2 ms monreseau.home [192.168.2.1]
2 28 ms 7 ms 13 ms 10.11.16.145
3 4 ms 3 ms 3 ms 10.178.206.136
4 10 ms 6 ms 2 ms 10.178.206.137
5 23 ms 24 ms 21 ms bx2-ashburn_xe5-1-1.net.bell.ca [64.230.79.176]
6 88 ms 25 ms 23 ms 12.89.71.9
7 409 ms * 406 ms cr81.mpsmn.ip.att.net [12.122.113.102]
8 97 ms 98 ms 100 ms cr1.cgcil.ip.att.net [12.122.18.21]
9 410 ms 413 ms 408 ms cr2.dvmco.ip.att.net [12.122.31.85]
10 413 ms 411 ms 411 ms cr1.slkut.ip.att.net [12.122.30.25]
11 98 ms 101 ms 96 ms cr2.la2ca.ip.att.net [12.122.30.30]
12 99 ms 96 ms 95 ms gar20.la2ca.ip.att.net [12.122.128.181]
13 97 ms 98 ms 99 ms 12-122-254-238.attens.net [12.122.254.238]
14 408 ms 408 ms 431 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
15 409 ms 409 ms 406 ms 12.129.209.68

Itinéraire déterminé.
Support Forum Agent
Posts: 856
We may not see a change in the status for the performance of the game yet for at least 30 minutes from the time of this post. If you continue to experience the listed issues, please give it about that long before running the trace and retesting. Thanks all!
Sorry where do I access that?
03/14/2014 12:34 PMPosted by Avalon
Sorry where do I access that?

On the first post in this thread, there will be a link the the Trace Route. Click there.

Or, click here: https://us.battle.net/support/en/article/performing-a-traceroute and follow the steps.
03/14/2014 12:26 PMPosted by Sherlock
For the 11h45 PST update that requested trace route. Here's mine.

ISP: Bell Canada
St-Eustache, Quebec, Canada


This. I live in the same town and everything, getting pretty annoyed, been since tuesday for me.

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 5 ms 3 ms 3 ms monreseau.home [192.168.2.1]
2 12 ms 5 ms 6 ms 10.11.16.145
3 6 ms 6 ms 6 ms 10.178.206.136
4 6 ms 7 ms 5 ms 10.178.206.137
5 29 ms 24 ms 24 ms bx2-ashburn_xe6-1-2.net.bell.ca [64.230.79.182]
6 28 ms 28 ms 27 ms 12.89.71.9
7 103 ms 103 ms 103 ms cr81.mpsmn.ip.att.net [12.122.113.102]
8 106 ms 101 ms 107 ms cr1.cgcil.ip.att.net [12.122.18.21]
9 103 ms 103 ms 104 ms cr2.dvmco.ip.att.net [12.122.31.85]
10 100 ms 104 ms 106 ms cr1.slkut.ip.att.net [12.122.30.25]
11 107 ms 106 ms 104 ms cr2.la2ca.ip.att.net [12.122.30.30]
12 101 ms 101 ms 100 ms gar20.la2ca.ip.att.net [12.122.128.181]
13 185 ms 99 ms 101 ms 12.122.251.190
14 100 ms 100 ms 98 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
15 118 ms 100 ms 101 ms 12.129.199.178
16 100 ms 100 ms 102 ms 12.129.209.68

Trace complete.
Edited by ShockValue#1973 on 3/14/2014 12:48 PM PDT
Ottawa,Canada
ISP: Bell

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 2 ms 2 ms 1 ms monreseau.home [192.168.2.1]
2 7 ms 7 ms 11 ms bas1-ottawa11_lo0_SYMP.net.bell.ca [64.230.200.134]
3 8 ms 26 ms 7 ms dis32-ottawa23_9-1-0_100.net.bell.ca [64.230.57.50]
4 25 ms 25 ms 25 ms bx2-ashburn_xe2-1-0.net.bell.ca [64.230.185.137]
5 28 ms 28 ms 26 ms 12.89.71.9
6 * 410 ms 407 ms cr81.mpsmn.ip.att.net [12.122.113.102]
7 102 ms 99 ms 99 ms cr1.cgcil.ip.att.net [12.122.18.21]
8 411 ms 409 ms 408 ms cr2.dvmco.ip.att.net [12.122.31.85]
9 408 ms 405 ms 408 ms cr1.slkut.ip.att.net [12.122.30.25]
10 98 ms 100 ms 99 ms cr2.la2ca.ip.att.net [12.122.30.30]
11 100 ms 95 ms 95 ms gar20.la2ca.ip.att.net [12.122.128.181]
12 98 ms 98 ms 98 ms 12-122-254-238.attens.net [12.122.254.238]
13 97 ms 97 ms 97 ms 206.16.68.46
14 98 ms 99 ms 99 ms 12.129.199.178
15 408 ms 411 ms 410 ms 12.129.209.68

Trace complete.
Hi guys, just to let you know, that this issue is also affecting both Diablo 3 and Hearthstone gameplay in Europe.

There is no chance to create or join any existing game.
Québec, Canada
ISP : Bell

1 1 ms 1 ms 1 ms 192.168.1.1
2 1 ms 1 ms 1 ms monreseau.home [192.168.2.1]
3 3 ms 19 ms 9 ms 10.11.16.17
4 5 ms 7 ms 7 ms 10.178.206.148
5 10 ms 3 ms 7 ms 10.178.206.149
6 34 ms 29 ms 29 ms bx2-ashburn_xe6-1-2.net.bell.ca [64.230.79.182]
7 28 ms 29 ms 29 ms 12.89.71.9
8 100 ms 107 ms 103 ms cr81.mpsmn.ip.att.net [12.122.113.102]
9 121 ms 103 ms 113 ms cr1.cgcil.ip.att.net [12.122.18.21]
10 102 ms 103 ms 107 ms cr2.dvmco.ip.att.net [12.122.31.85]
11 126 ms 108 ms 103 ms cr1.slkut.ip.att.net [12.122.30.25]
12 104 ms 107 ms 103 ms cr2.la2ca.ip.att.net [12.122.30.30]
13 112 ms 100 ms 105 ms gar20.la2ca.ip.att.net [12.122.128.181]
14 104 ms 105 ms 105 ms 12-122-254-234.attens.net [12.122.254.234]
15 287 ms 214 ms 421 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
16 108 ms 105 ms 105 ms 12.129.209.68

Trace complete.
I am having a hard time staying in games. I get an error that boots me out of the game and then another error that boots me out of the game client. This started happening about 30 minutes ago. and I've not been able to stay in a game longer than 3 minutes since then.
Old:

6 417 ms cr1.cgcil.ip.att.net [12.122.99.22]
7 421 ms cr2.dvmco.ip.att.net [12.122.31.85]
8 418 ms cr1.slkut.ip.att.net [12.122.30.25]

Now:

6 83 ms cr1.cgcil.ip.att.net [12.122.99.22]
7 80 ms cr2.dvmco.ip.att.net [12.122.31.85]
8 81 ms cr1.slkut.ip.att.net [12.122.30.25]

Hopefully this is because it got fixed, not because it is Friday and the traffic causing the problem has died down until Monday.

Perfectly playable.
Still having huge lag spikes. Not having any issues creating a game so far but they are almost unplayable.

ISP: Northwestel
City: Whitehorse, Yukon Territory, Canada

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 8 ms 7 ms 8 ms 10.132.255.254
3 7 ms 7 ms 9 ms ae-0-401-drt01-whthytxb.nwtel.org [198.135.216.217]
4 48 ms 46 ms 50 ms 10.1.5.213
5 53 ms 65 ms 51 ms 64.230.219.13
6 71 ms 72 ms 71 ms bx4-seattle_xe7-0-0_0.net.bell.ca [64.230.186.46]
7 378 ms * 379 ms 12.94.202.21
8 107 ms 107 ms 108 ms 12.122.111.14
9 105 ms 107 ms 108 ms cr2.sffca.ip.att.net [12.122.31.194]
10 418 ms 420 ms 418 ms cr2.la2ca.ip.att.net [12.122.31.133]
11 124 ms 108 ms 122 ms gar29.la2ca.ip.att.net [12.122.129.241]
12 411 ms 413 ms 411 ms 12.122.251.190
13 413 ms 413 ms 415 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
14 414 ms 411 ms 413 ms 12.129.209.68

Trace complete.
Edited by Qendain#1585 on 3/14/2014 1:23 PM PDT
Tracing route to 12.129.209.68 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms monreseau.home [192.168.2.1]
2 12 ms 12 ms 12 ms bas1-pickering62_lo0_SYMP.net.bell.ca [64.230.200.146]
3 12 ms 12 ms 12 ms agg3-toronto12_5-2-0_100.net.bell.ca [64.230.148.20]
4 23 ms 23 ms 23 ms bx5-chicagodt_xe1-0-0-0.net.bell.ca [64.230.186.242]
5 23 ms 23 ms 23 ms 12.249.212.9
6 87 ms 87 ms 88 ms cr1.cgcil.ip.att.net [12.122.99.22]
7 90 ms 90 ms 88 ms cr2.dvmco.ip.att.net [12.122.31.85]
8 88 ms 91 ms 88 ms cr1.slkut.ip.att.net [12.122.30.25]
9 396 ms 399 ms 397 ms cr2.la2ca.ip.att.net [12.122.30.30]
10 432 ms 395 ms 396 ms gar20.la2ca.ip.att.net [12.122.128.181]
11 86 ms 110 ms 86 ms 12.122.251.190
12 87 ms 87 ms 87 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
13 87 ms 87 ms 88 ms 12.129.209.68

Trace complete.
Barrie, ON, Canada

Bell Fibe

1 mynetwork.home 4.887 ms 1.274 ms 1.194 ms
2 10.11.0.33 (10.11.0.33) 7.859 ms 8.867 ms 8.072 ms
3 * 10.178.206.14 (10.178.206.14) 8.620 ms 6.939 ms
4 10.178.206.15 (10.178.206.15) 6.071 ms 6.053 ms 6.037 ms
5 bx5-chicagodt_xe5-0-2.net.bell.ca (64.230.186.78) 22.296 ms
bx5-chicagodt_xe3-1-0-0.net.bell.ca (64.230.186.246) 22.032 ms
bx5-chicagodt_xe0-1-0_0 (64.230.186.255) 21.906 ms
6 12.249.212.9 (12.249.212.9) 23.079 ms 24.395 ms 21.731 ms
7 cr1.cgcil.ip.att.net (12.122.99.22) 492.845 ms 511.881 ms 406.060 ms
8 cr2.dvmco.ip.att.net (12.122.31.85) 515.503 ms 445.206 ms 560.528 ms
9 cr1.slkut.ip.att.net (12.122.30.25) 512.456 ms 501.734 ms 513.788 ms
10 cr2.la2ca.ip.att.net (12.122.30.30) 85.281 ms 88.571 ms 88.028 ms
11 gar20.la2ca.ip.att.net (12.122.128.181) 82.225 ms 82.092 ms 81.942 ms
12 12-122-254-238.attens.net (12.122.254.238) 84.171 ms 82.551 ms 86.161 ms
13 mdf001c7613r0002.lax1.attens.net (206.16.68.54) 85.747 ms
mdf001c7613r0004-gig-10-1.lax1.attens.net (12.129.193.250) 460.005 ms
mdf001c7613r0003-gig-12-1.lax1.attens.net (12.129.193.254) 404.025 ms
Berthierville, Québec

Bell

(unable to log in one game without having enormous magical sensationnal latency)

1 1 ms 1 ms 1 ms home [192.168.2.1]
2 182 ms 100 ms 38 ms bas12-montreal02_lo0_SYMP.net.bell.ca [64.230.197.75]
3 14 ms 11 ms 13 ms agg1-montreal02_GE0-0-5_112.net.bell.ca [64.230.204.221]
4 27 ms 25 ms 25 ms bx2-ashburn_xe2-1-0.net.bell.ca [64.230.185.137]
5 29 ms 28 ms 28 ms 12.89.71.9
6 103 ms 104 ms 106 ms cr81.mpsmn.ip.att.net [12.122.113.102]
7 418 ms 417 ms 413 ms cr1.cgcil.ip.att.net [12.122.18.21]
8 107 ms 107 ms 106 ms cr2.dvmco.ip.att.net [12.122.31.85]
9 104 ms 106 ms 104 ms cr1.slkut.ip.att.net [12.122.30.25]
10 416 ms 421 ms * cr2.la2ca.ip.att.net [12.122.30.30]
11 * 413 ms 411 ms gar20.la2ca.ip.att.net [12.122.128.181]
12 131 ms 103 ms 101 ms 12.122.251.190
13 133 ms 136 ms 124 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
14 104 ms 103 ms 106 ms 12.129.209.68
been having an issue with the client disconnecting so here ya go
Tracing route to 12.129.209.68 over a maximum of 30 hops

1 12 ms 3 ms 5 ms 192.168.0.1
2 11 ms 16 ms 14 ms blk-222-64-1.eastlink.ca [24.222.64.1]
3 13 ms 16 ms 16 ms blk-212-126-129.eastlink.ca [173.212.126.129]
4 13 ms 12 ms 13 ms ns-hlfx-dr001.ns.eastlink.ca [24.222.79.57]
5 14 ms 13 ms 12 ms ns-hlfx-br001.ns.eastlink.ca [24.215.101.221]
6 18 ms 14 ms 13 ms ns-hlfx-br002.ns.eastlink.ca [24.215.102.10]
7 34 ms 32 ms 33 ms xe-0-3-0.mtl10.ip4.tinet.net [77.67.70.77]
8 33 ms 31 ms 32 ms xe-4-2-1.nyc20.ip4.tinet.net [89.149.184.73]
9 58 ms 62 ms 56 ms 192.205.37.37
10 106 ms 103 ms 103 ms cr1.n54ny.ip.att.net [12.122.81.106]
11 104 ms 107 ms 99 ms cr2.cgcil.ip.att.net [12.122.1.2]
12 103 ms 105 ms 109 ms cr1.cgcil.ip.att.net [12.122.2.53]
13 123 ms 99 ms 116 ms cr2.dvmco.ip.att.net [12.122.31.85]
14 107 ms 103 ms 101 ms cr1.slkut.ip.att.net [12.122.30.25]
15 105 ms 98 ms 98 ms cr2.la2ca.ip.att.net [12.122.30.30]
16 97 ms 97 ms 100 ms gar20.la2ca.ip.att.net [12.122.128.181]
17 165 ms 106 ms 100 ms 12-122-254-234.attens.net [12.122.254.234]
18 224 ms 201 ms 208 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
19 98 ms 105 ms 100 ms
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 <1 ms <1 ms <1 ms 192.168.2.1
3 8 ms 8 ms 8 ms bas13-quebec14_lo0_SYMP.net.bell.ca [64.230.200.9]
4 9 ms 8 ms 8 ms dis17-quebec14_GE10-5-1-0_100.net.bell.ca [64.230.87.236]
5 11 ms 12 ms 12 ms bx2-ashburn_xe4-0-3.net.bell.ca [64.230.79.233]
6 22 ms 22 ms 22 ms 12.89.71.9
7 413 ms 415 ms 415 ms cr81.mpsmn.ip.att.net [12.122.113.102]
8 407 ms 404 ms 406 ms cr1.cgcil.ip.att.net [12.122.18.21]
9 415 ms 413 ms 415 ms cr2.dvmco.ip.att.net [12.122.31.85]
10 * 416 ms 416 ms cr1.slkut.ip.att.net [12.122.30.25]
11 107 ms 106 ms 107 ms cr2.la2ca.ip.att.net [12.122.30.30]
12 103 ms 103 ms 103 ms gar20.la2ca.ip.att.net [12.122.128.181]
13 414 ms 413 ms 415 ms 12.122.251.190
14 413 ms * 413 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
15 415 ms 414 ms 412 ms 12.129.209.68

Trace complete.
This issue also affecting Asia region. I tried to logout and login again, and this time my Battle.Net Launch is not responding. Please resolve this ASAP, Blizzard Support Team
03/14/2014 01:03 PMPosted by simguy
Hopefully this is because it got fixed, not because it is Friday and the traffic causing the problem has died down until Monday.

Perfectly playable.


So much for it lasting ... back in the 400 ms + range with packet loss.
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]