Diablo® III

Northeastern Connection Issues

03/01/2014 12:05 PMPosted by Kaltonis
Hi guys!

Are all of you in the northeast US? If so, you're probably affected by the regional Internet issue that started this morning. Post a [url="https://us.battle.net/support/en/article/performing-a-traceroute"]trace route[/url] and we'll look for commonality.


My ISP is not time warner. I have wide open west. Can log into wow and sc manually. Can not log into d3, and battle.net client can not connect with server. I live in Ohio. I have 2 friends in Vermont who have been able to log into d3 all day. I played last night for a while, they were not on at all.

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms . [192.168.2.1]
2 * * * Request timed out.
3 93 ms 94 ms 32 ms 10.35.25.170
4 13 ms 12 ms 11 ms 10.35.24.1
5 99 ms 108 ms 43 ms 10.35.11.13
6 105 ms 109 ms 62 ms xe-5-1-0.bar1.Cincinnati1.Level3.net [4.59.40.17]
7 21 ms 21 ms 22 ms ae-10-10.ebr2.Chicago1.Level3.net [4.69.136.214]
8 19 ms 18 ms 22 ms ae-5-5.ebr2.Chicago2.Level3.net [4.69.140.194]
9 109 ms 115 ms 114 ms ae-207-3607.edge4.Chicago2.Level3.net [4.69.158.153]
10 43 ms 44 ms 42 ms 192.205.37.149
11 91 ms 91 ms 87 ms cr1.cgcil.ip.att.net [12.122.133.34]
12 97 ms 91 ms 108 ms cr2.dvmco.ip.att.net [12.122.31.85]
13 88 ms 92 ms 91 ms cr1.slkut.ip.att.net [12.122.30.25]
14 91 ms 91 ms 97 ms cr2.la2ca.ip.att.net [12.122.30.30]
15 140 ms 122 ms 140 ms gar20.la2ca.ip.att.net [12.122.128.181]
16 155 ms 155 ms 146 ms 12-122-254-238.attens.net [12.122.254.238]
17 87 ms 89 ms 89 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
18 90 ms 90 ms 88 ms 12.129.209.68

Trace complete.
Edited by Taahoe1984#1806 on 3/1/2014 1:21 PM PST
Redid the tracer, Hope it helps to resolve the issue soon. Forgot to add.. Central new york. Time Warner.

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 9 ms gig1-2-8.ithcnycy-rtr002.cny.northeast.rr.com [2
4.24.16.48]
4 14 ms 14 ms 14 ms rdc-24-58-151-28.cny.east.twcable.com [24.58.151
.28]
5 15 ms 13 ms 13 ms rdc-24-58-149-254.cny.east.twcable.com [24.58.14
9.254]
6 55 ms 33 ms 36 ms be51.albynyyf00r.nyroc.rr.com [24.24.21.170]
7 31 ms 35 ms 26 ms be46.cr0.nyc30.tbone.rr.com [107.14.19.102]
8 30 ms 29 ms 25 ms 107.14.17.216
9 26 ms 30 ms 34 ms 209.220.18.33.ptr.us.xo.net [209.220.18.33]
10 26 ms 29 ms 25 ms 207.88.15.86.ptr.us.xo.net [207.88.15.86]
11 40 ms 27 ms 27 ms 206.111.13.246.ptr.us.xo.net [206.111.13.246]
12 92 ms 90 ms 89 ms cr1.n54ny.ip.att.net [12.122.81.106]
13 * * * Request timed out.
14 119 ms 109 ms 105 ms cr1.cgcil.ip.att.net [12.122.2.53]
15 90 ms 111 ms 111 ms cr2.dvmco.ip.att.net [12.122.31.85]
16 98 ms 92 ms 91 ms cr1.slkut.ip.att.net [12.122.30.25]
17 89 ms 87 ms 90 ms cr2.la2ca.ip.att.net [12.122.30.30]
18 87 ms 91 ms 88 ms gar20.la2ca.ip.att.net [12.122.128.181]
19 87 ms 90 ms 89 ms 12-122-254-234.attens.net [12.122.254.234]
20 85 ms 88 ms 98 ms 206.16.68.46
21 90 ms 88 ms 92 ms 12.129.199.178
22 86 ms 93 ms 87 ms 12.129.209.68

Trace complete.
Edited by Remmy#1128 on 3/1/2014 1:23 PM PST
90 Dwarf Paladin
12390
Posts: 113
Here's mine (Western NY using TWC)

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 48 ms 25 ms 22 ms cable-mac1.ntnwny17-ar4002.nyroc.rr.com [76.180.188.1]
2 12 ms 11 ms 17 ms 98.0.5.93
3 56 ms 11 ms 12 ms ae7-0.lncsnycd-rtr001.nyroc.rr.com [98.0.3.26]
4 31 ms 48 ms 35 ms bundle-ether6.rochnyei-rtr000.nyroc.rr.com [98.0.3.3]
5 27 ms 63 ms 27 ms be25.cr0.chi10.tbone.rr.com [107.14.19.28]
6 28 ms 33 ms 27 ms ae0.pr1.chi10.tbone.rr.com [107.14.17.192]
7 28 ms 28 ms 30 ms 216.1.94.65
8 30 ms 28 ms 42 ms 207.88.15.90.ptr.us.xo.net [207.88.15.90]
9 * * 253 ms 206.111.2.90.ptr.us.xo.net [206.111.2.90]
10 113 ms 88 ms 78 ms cr1.cgcil.ip.att.net [12.122.81.94]
11 85 ms 82 ms 81 ms cr2.dvmco.ip.att.net [12.122.31.85]
12 103 ms 81 ms 78 ms cr1.slkut.ip.att.net [12.122.30.25]
13 80 ms 78 ms 75 ms cr2.la2ca.ip.att.net [12.122.30.30]
14 74 ms 77 ms 77 ms gar20.la2ca.ip.att.net [12.122.128.181]
15 78 ms 75 ms 76 ms 12-122-254-234.attens.net [12.122.254.234]
16 * * * Request timed out.
17 75 ms 76 ms 76 ms 12.129.209.68

Trace complete.
Edited by SaintLuck#1946 on 3/1/2014 1:36 PM PST
90 Undead Rogue
0
Posts: 2
Potsdam, NY - Time Warner Cable.

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 22 ms 9 ms 9 ms 10.101.160.1
2 14 ms 9 ms 14 ms gig5-2-2.mssnny19-rtr001.cny.northeast.rr.com [2
4.24.19.22]
3 27 ms 16 ms 21 ms ae62.esyrnyaw-rtr001.cny.northeast.rr.com [24.58
.129.0]
4 43 ms 30 ms 30 ms be4.rochny-rtr000.cny.northeast.rr.com [24.58.14
9.252]
5 31 ms 31 ms 33 ms be35.cr0.chi10.tbone.rr.com [107.14.19.104]
6 35 ms 91 ms 29 ms ae0.pr1.chi10.tbone.rr.com [107.14.17.192]
7 31 ms 28 ms 28 ms 216.1.94.145
8 31 ms 35 ms 32 ms 207.88.15.90.ptr.us.xo.net [207.88.15.90]
9 89 ms 34 ms 56 ms 206.111.2.90.ptr.us.xo.net [206.111.2.90]
10 90 ms 82 ms 86 ms cr1.cgcil.ip.att.net [12.122.81.94]
11 81 ms 88 ms 78 ms cr2.dvmco.ip.att.net [12.122.31.85]
12 83 ms 78 ms 85 ms cr1.slkut.ip.att.net [12.122.30.25]
13 86 ms 83 ms 81 ms cr2.la2ca.ip.att.net [12.122.30.30]
14 79 ms 76 ms 83 ms gar20.la2ca.ip.att.net [12.122.128.181]
15 79 ms 81 ms 88 ms 12-122-254-234.attens.net [12.122.254.234]
16 78 ms 80 ms 79 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54]

17 78 ms 78 ms 78 ms 12.129.209.68

Trace complete.
Western NY TWC: Sigh my son is asleep and the only hour or two i'll have to play today... come on
Tracing route to 12.129.209.68 over a maximum of 30 hops

1 9 ms 1 ms <1 ms 192.168.1.1
2 30 ms 40 ms 30 ms cable-mac1.olenny24-ar4002.nyroc.rr.com [69.207.32.1]
3 18 ms 25 ms 19 ms 98.0.5.77
4 14 ms * 13 ms ae14-0.lncsnycd-rtr001.nyroc.rr.com [98.0.3.76]
5 30 ms 33 ms 33 ms bundle-ether6.rochnyei-rtr000.nyroc.rr.com [98.0.3.3]
6 31 ms 33 ms 29 ms ae-3-0.cr0.chi10.tbone.rr.com [66.109.6.72]
7 * * 30 ms ae1.pr1.chi10.tbone.rr.com [107.14.17.194]
8 * 25 ms 27 ms 216.1.94.65
9 36 ms 28 ms * 207.88.15.90.ptr.us.xo.net [207.88.15.90]
10 79 ms 29 ms 27 ms 206.111.2.90.ptr.us.xo.net [206.111.2.90]
11 79 ms 79 ms 78 ms cr1.cgcil.ip.att.net [12.122.81.94]
12 83 ms 81 ms 79 ms cr2.dvmco.ip.att.net [12.122.31.85]
13 78 ms 79 ms 78 ms cr1.slkut.ip.att.net [12.122.30.25]
14 77 ms 80 ms 79 ms cr2.la2ca.ip.att.net [12.122.30.30]
15 * * * Request timed out.
16 78 ms 76 ms 80 ms 12-122-254-234.attens.net [12.122.254.234]
17 * * * Request timed out.
18 122 ms 79 ms 79 ms 12.129.199.178
19 79 ms 79 ms 78 ms 12.129.209.68

Trace complete.
Edited by Black#1360 on 3/1/2014 1:43 PM PST
Orange County, CA.
Ten miles away from Blizzard.

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 2 ms 6 ms 7 ms 192.168.1.1
2 * * * Request timed out.
3 8 ms 11 ms 13 ms ip68-4-11-182.oc.oc.cox.net [68.4.11.182]
4 * 15 ms 28 ms ip68-4-11-229.oc.oc.cox.net [68.4.11.229]
5 19 ms 25 ms 17 ms ip68-4-11-228.oc.oc.cox.net [68.4.11.228]
6 2100 ms 99 ms 13 ms langbprj01-ae1.rd.la.cox.net [68.1.1.13]
7 13 ms 11 ms 15 ms xe-7-3-3.edge2.LosAngeles9.Level3.net [4.53.230.73]
8 26 ms 16 ms 15 ms vlan70.csw2.LosAngeles1.Level3.net [4.69.144.126]
9 15 ms 15 ms 12 ms ae-71-71.ebr1.LosAngeles1.Level3.net [4.69.137.5]
10 25 ms 32 ms 24 ms ae-6-6.ebr1.Tustin1.Level3.net [4.69.153.222]
11 16 ms 14 ms 12 ms ae-106-3506.bar2.Tustin1.Level3.net [4.69.158.102]
12 * * * Request timed out.
13 23 ms 19 ms 19 ms cr2.la2ca.ip.att.net [12.122.129.106]
14 107 ms 117 ms 15 ms gar29.la2ca.ip.att.net [12.122.129.241]
15 15 ms 50 ms 18 ms 12-122-254-238.attens.net [12.122.254.238]
16 * * * Request timed out.
17 15 ms 20 ms 16 ms 12.129.199.178
18 * Destination host unreachable.

Trace complete.
Kaltonis, or any blue, any update... or some type of ETA. This is really frustrating.
Ten Hours of downtime for many players and no updates is just a little unprofessional. Even a "still looking into the issue" would be nice.
Americas down (only Americas), blues... time to update us on the issue and an ETA.
Posts: 90
Could we get a note on the progress please?

Day off and couldn't play.
It probably isn't affecting enough people for them to act hastily to get the problem fixed. The problem may night even be on their end.
03/01/2014 02:18 PMPosted by Mog
Could we get a note on the progress please?

Day off and couldn't play.


Yeah, I got one day off in two weeks and all I wanted to do was play the new patch.
I'm seeing a lot of issues on Time Warner Cable's end. downdetector.com is showing Rochester NY as having issues
03/01/2014 02:23 PMPosted by Smiley
I'm seeing a lot of issues on Time Warner Cable's end. downdetector.com is showing Rochester NY as having issues
Michigan
Upstate, NY

Have been down since last night.

Time Warner Customer.

Help us blizz!!
just talked to Time Warner Cable and they are blaming Blizzard. They said that if I can access the internet and websites and even other games (PoE is working for me) then it isn't on their end and they are fulfilling their service requirement. I explained to him that my friend's list and party functions on my xbox are being screwy too and he said that I need to get ahold of Microsoft for that... I'm not being very SMILEY right now :(
It's just blizzard people. i'm having no issues with anything else but diablo 3.
C:\Windows\system32>tracert 12.129.209.68

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 3 ms 1 ms <1 ms 192.168.1.1
2 23 ms 979 ms 21 ms 10.97.112.1
3 371 ms 23 ms 9 ms ten1-2-2.wnslme07-rtr001.ne.northeast.rr.com [24.31.157.66]
4 1168 ms 91 ms 16 ms rdc-204-210-69-180.ne.northeast.rr.com [204.210.69.180]
5 53 ms 36 ms 39 ms rdc-204-210-69-49.ne.northeast.rr.com [204.210.69.49]
6 44 ms 71 ms 44 ms be26.cr0.nyc30.tbone.rr.com [107.14.19.26]
7 302 ms 984 ms 80 ms 107.14.17.216
8 544 ms 67 ms 35 ms 209.220.18.33.ptr.us.xo.net [209.220.18.33]
9 843 ms 37 ms 31 ms 207.88.15.86.ptr.us.xo.net [207.88.15.86]
10 1609 ms 71 ms 42 ms 206.111.13.246.ptr.us.xo.net [206.111.13.246]
11 * 1288 ms 105 ms cr1.n54ny.ip.att.net [12.122.81.106]
12 287 ms 98 ms 115 ms cr2.cgcil.ip.att.net [12.122.1.2]
13 100 ms 132 ms 106 ms cr1.cgcil.ip.att.net [12.122.2.53]
14 * * * Request timed out.
15 134 ms 122 ms 123 ms cr1.slkut.ip.att.net [12.122.30.25]
16 191 ms 115 ms * cr2.la2ca.ip.att.net [12.122.30.30]
17 351 ms 96 ms 166 ms gar20.la2ca.ip.att.net [12.122.128.181]
18 * 1052 ms 277 ms 12-122-254-238.attens.net [12.122.254.238]
19 267 ms 99 ms 97 ms 206.16.68.46
20 98 ms 102 ms 96 ms 12.129.199.178
21 * 97 ms 1222 ms 12.129.209.68

Trace complete.

C:\Windows\system32>
I'm curious how it's just blizzard people when 90% of Diablo players attempting to play can but certain areas of the country cannot.

a blue post would certainly clear it up
Edited by Smiley#1953 on 3/1/2014 2:59 PM PST
I am out in Charlotte, NC, Timewarner. Error 33.
This topic has reached its post limit. You may no longer post or reply to posts for this topic.

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]