Diablo® III

Error 3007

Anyone else not able to log in?
Reply Quote
Same here error 3007
Reply Quote
Im not happy. keeps "timing out"
Reply Quote
Yes, same here. They did have scheduled maintenance for PDT 3am-11pm.
Reply Quote
yeah, i was able to log in at 10:30am est strangely enough, but came back home at 2pm and get the 3007 error upon trying to login. probably just a hiccup, glad its not just me
Reply Quote
I was able to log in ~10 minutes ago then I had to exit the game to switch from Entertainment Mode to Game mode for my sound card then got Error 3007 when I tried to log in again.
Reply Quote
Same cant log in zzzzz
Reply Quote
Same here
Reply Quote
Same, getting the evil 3007 and de ja vu of launch day.
Reply Quote
Same here.
Reply Quote
same, WoW is also having a similar issue
Reply Quote
Same here.
Reply Quote
Yes, I was scouring for solutions, glad it's not just me.
Reply Quote
Same here "Error 3007"
Reply Quote
Service status: manteniance has not concluded yet.

/thread
Reply Quote
90 Human Priest
14220
Posts: 272
help
Reply Quote
same here
Reply Quote
Except, many players are/have been connected for a while.. In other news:


Tracing route to 12.129.209.68 over a maximum of 30 hops

1 1 ms 1 ms 1 ms MyRouter.Home [192.168.254.254]
2 9 ms 9 ms 9 ms h1.176.89.75.dynamic.ip.windstream.net [75.89.176.1]
3 8 ms 8 ms 17 ms h14.40.141.67.dynamic.ip.windstream.net [67.141.40.14]
4 14 ms 14 ms 13 ms h224.222.90.75.static.ip.windstream.net [75.90.222.224]
5 12 ms 14 ms 14 ms adsl-75-16-80-26.dsl.irvnca.sbcglobal.net [75.16.80.26]
6 31 ms 35 ms 34 ms h118.80.16.72.dynamic.ip.windstream.net [72.16.80.118]
7 32 ms 34 ms 34 ms 12.88.174.133
8 65 ms 67 ms 66 ms cr2.dlstx.ip.att.net [12.122.138.42]
9 65 ms 68 ms 67 ms cr2.la2ca.ip.att.net [12.122.28.178]
10 66 ms 64 ms 64 ms gar29.la2ca.ip.att.net [12.122.129.241]
11 64 ms 64 ms 63 ms 12-122-254-238.attens.net [12.122.254.238]
12 66 ms 64 ms 64 ms 206.16.68.46
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
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.


Fix your servers blizz. Thanks.
Reply Quote
Same here error 3007
but Zone asia & EU . i can login .
Reply Quote
MVP - Technical Support
Posts: 16,259
View profile
This issue with logins started about an hour ago based on all the posts over in WoW TS and CS. They have been asking players for locations, ISPs, and tracerts. Results are that seems to impact more folks on the West coast. It is affecting both WoW and, from the looks of it, D3. Not sure about SC2. They are actively working on it as of the last update 9 mins ago. Hopefully the WoW login and D3 login issues are related and the fix helps both sets of players.
Edited by MissCheetah#1661 on 4/30/2013 12:39 PM PDT
Reply Quote

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]