Diablo® III

ERROR 3007

Connection to battle.net service has timed out. please login again.

Last time i played was about 2 months ago and since it's a holiday today, i decided to get back in the game but couldn't even login...i don't think i have to add ports or re-configure my modem because it was working fine 2 months ago and there was nothing done to change the settings over the past 2 months.

Please email me at thomas_ang2436@yahoo.com for a fix. thanks!
Reply Quote
me too im getting error 3007. it was about a month since i last played... why? i can log in to asia and europe but not in americas. thats where my hero is... what happen here?
Reply Quote
Support Forum Agent
MilesMiles, can you run a trace route and pathping, and post them here?

After you paste everything into a post, highlight everything, and hit the "pre" button (It says "Code Blocks" when you hover your mouse over it). That'll make the information much more readable.
________________________________________________
Monday - Friday, 8 am - 5 pm PST
Reply Quote
Velnrak

I'm having this issue for around a week now. From Philippines, using PLDT DSL

Here's my tracert & pathping

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 12 ms 11 ms 11 ms 112.208.32.1.pldt.net [112.208.32.1]
2 12 ms 12 ms 12 ms 119.93.255.193
3 11 ms 12 ms 12 ms 210.213.131.50.static.pldt.net [210.213.131.50]
4 10 ms 12 ms 12 ms 210.213.131.89.static.pldt.net [210.213.131.89]
5 176 ms 177 ms 177 ms if-13-0.mcore5.LAA-LosAngeles.as6453.net [209.58.33.57]
6 188 ms 181 ms 178 ms if-9-0-1-0.tcore1.LVW-LosAngeles.as6453.net [66.110.59.25]
7 177 ms 179 ms 178 ms 66.110.59.42
8 173 ms 174 ms 172 ms cr2.la2ca.ip.att.net [12.122.84.218]
9 170 ms 170 ms 170 ms gar20.la2ca.ip.att.net [12.122.128.181]
10 170 ms 170 ms 170 ms 12.122.251.190
11 292 ms 218 ms 270 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
12 * * * Request timed out.
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.



Tracing route to 12.129.209.68 over a maximum of 30 hops

0 DellInspiron15R.mshome.net [192.168.0.103]
1 112.208.32.1.pldt.net [112.208.32.1]
2 119.93.255.193
3 210.213.131.50.static.pldt.net [210.213.131.50]
4 210.213.131.89.static.pldt.net [210.213.131.89]
5 if-13-0.mcore5.LAA-LosAngeles.as6453.net [209.58.33.57]
6 if-9-0-1-0.tcore1.LVW-LosAngeles.as6453.net [66.110.59.25]
7 66.110.59.42
8 cr1.la2ca.ip.att.net [12.122.84.202]
9 gar20.la2ca.ip.att.net [12.122.128.181]
10 12-122-254-234.attens.net [12.122.254.234]
11 mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
12 * * *
Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DellInspiron15R.mshome.net [192.168.0.103]
0/ 100 = 0% |
1 12ms 0/ 100 = 0% 0/ 100 = 0% 112.208.32.1.pldt.net [112.208.32.1]
0/ 100 = 0% |
2 13ms 0/ 100 = 0% 0/ 100 = 0% 119.93.255.193
0/ 100 = 0% |
3 13ms 0/ 100 = 0% 0/ 100 = 0% 210.213.131.50.static.pldt.net [210.213.131.50]
0/ 100 = 0% |
4 16ms 0/ 100 = 0% 0/ 100 = 0% 210.213.131.89.static.pldt.net [210.213.131.89]
0/ 100 = 0% |
5 180ms 0/ 100 = 0% 0/ 100 = 0% if-13-0.mcore5.LAA-LosAngeles.as6453.net [209.58.33.57]
0/ 100 = 0% |
6 221ms 0/ 100 = 0% 0/ 100 = 0% if-9-0-1-0.tcore1.LVW-LosAngeles.as6453.net [66.110.59.25]
0/ 100 = 0% |
7 224ms 0/ 100 = 0% 0/ 100 = 0% 66.110.59.42
100/ 100 =100% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr1.la2ca.ip.att.net [12.122.84.202]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% gar20.la2ca.ip.att.net [12.122.128.181]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-234.attens.net [12.122.254.234]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]

Trace complete.


* I haven't tried doing those DNS code thingy change
Edited by Xuvreil#1110 on 12/24/2012 9:54 PM PST
Reply Quote
I'm having also the same problem. Here's mine.

Trace route

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 9 ms 14 ms 13 ms 121.1.11.81
4 6 ms 7 ms 7 ms 121.54.9.81
5 10 ms 7 ms 13 ms 203.111.226.6
6 11 ms 13 ms 13 ms 203.87.132.5
7 12 ms 11 ms 13 ms 210.213.244.233.static.pldt.net [210.213.244.233]
8 13 ms 11 ms 12 ms 210.213.132.22.static.pldt.net [210.213.132.22]
9 8 ms 8 ms 13 ms 210.213.128.37.static.pldt.net [210.213.128.37]
10 11 ms 12 ms 10 ms 210.213.131.89.static.pldt.net [210.213.131.89]
11 169 ms 170 ms 171 ms if-13-0.mcore5.laa-losangeles.as6453.net [209.58.33.57]
12 164 ms 166 ms 167 ms if-9-3-1-13.tcore1.LVW-LosAngeles.as6453.net [209.58.33.138]
13 158 ms 162 ms 164 ms 66.110.59.42
14 160 ms 169 ms 172 ms cr1.la2ca.ip.att.net [12.122.84.202]
15 163 ms 169 ms 160 ms gar29.la2ca.ip.att.net [12.122.129.241]
16 166 ms 169 ms 167 ms 12-122-254-238.attens.net [12.122.254.238]
17 164 ms 175 ms 168 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
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.


Pathping:

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 bartolo-PC.smartbro.net [192.168.1.104]
1 192.168.1.1
2 * * *
Computing statistics for 25 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 bartolo-PC.smartbro.net [192.168.1.104]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1

Trace complete.

Reply Quote
There are people having trouble over at this thread also: http://us.battle.net/d3/en/forum/topic/7415493406

I tried again just before and still can't acces the Americas server, but no trouble with Asia and Europe. I don't really care if I need to use the Asia server from now on, but my level 60 (11) character is stuck over on the Americas server. I'd really like to get it back.
Reply Quote
Blizzard,
I'm also having the same problem. Whenever i connect in Americas server i get error 3007. Europe and Asia servers have no problems. Please help me with this.
Reply Quote
With many of us having the same problem. It's pretty safe to assume that the problem is not with our computers or connections.

I think Blizzard should look into this.
Reply Quote
i have the same problem... blizzard pls help
Reply Quote
i tried logging in to the europe and asia regions and i was able to log in... but my characters are in the americas region....

maybe the problem is with the americas region...

blizzard please advice me what to do.... my characters are all in the americas region
Reply Quote
Having the same problem, I'm trying to log in but I keep getting error 3007.

Help please.
Reply Quote
same problem. like mr. aioaio, i don't have a problem shifting from server to server except from the fact that all my items and lvl60 heroes are on The Americas Server. i have spend a great deal of time and energy on it, i just want it back. please help us out. thanks.
Reply Quote
Same problem here. I can log in the europe and asia but not in the americas where my characters are. please fix.
Reply Quote
A friend of mine found a fix:

Change your DNS.

We can probably give out an exact procedure once we test it out, but you can google it now.

He changed his DNS and then poof, he got in and played D3. Might help you guys out.
Reply Quote
i am at a blank wall here.... blizzard please help.... please please
Reply Quote
i would just like to ask if someone from blizzard is addressing this problem already... i was reading through the solutions provided by other players and im quire confused by it....

i can see from the other threads in the forum that this problem has been existing for quite sometime now.. some problem posts have been posted since may of this year.... and yet we are still getting the same problem... the others have problems of getting disconnected...

as for me.. i have a problem in getting connected.... if one solution is joining the general chat.. how can i join the general chat if i cant log in...

please please blizzard do something to help us.... this is quite frustrating...
Reply Quote
Please fix this!!
Reply Quote
I still have the same problem for over weeks already..
Reply Quote
Blizzard fix this problem please... i have my characters in that server...
Reply Quote
Blizzard support told me the problem is with my ISP and that it is common for ISPs in foreign countries to have problems accessing American servers......

The advice was to contact my ISP because that's where the problem lies.

From that I can only assume that Blizzard has washed its collective hands of the problem and decided to give up on people who can't access the Americas server due to changes Blizzard made. We are able to access the Asia and Europe servers and that's good enough for Blizzard. Forget your characters people, move on - there is no light at the end of the tunnel.
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]