Request Timed out error 3006

Technical Support
I get this error in 'retrieving hero list', and when I am lucky and it goes to my hero and I can play everything is extremely slow and I can do nothing.

I have checked my internet connection and speed and everything is normal, I have reset my router many times nothing works.

Am I the only one with this problem? Is there something I can do to fix this?

Thank You
Yeah ive had the same problem for the last 2 days and before that when i did log on successfully the latency was extremely bad.
WTF is going on I cant get in the whole day pls sort this out!!!!! or at least let us know whats going on!!!!!
Ok so it is not just me. I have this problem for about 3 or 4 days now it really sucks
Amazing. Tried for over 2 hours to get into the game without success.

Time that I had to actually play the game was spend trying to get INTO the game.

No notice. No support. Nothing.

Awesome customer support guys. Truly
Please try power-cycling your router and see if that helps Silveria. If the issue persists, please post the following information for review:

  • Country you are playing from.
  • Name of ISP you use.
  • Connection type (WiFi, cable etc.).
  • Router make and model.
  • Router firmware version.
  • Does the same happen when playing in other regions?

19/03/2015 18:44Posted by AshaBellanar
Awesome customer support guys. Truly

Let's be fair here Silveria , you haven't actually contacted our support team about this (from this Battle.net account at least) so we haven't had a chance to help. This forum is not a support channel, it's a place where players can discuss any ingame technical issues they may be experiencing with other members of the community.

Many thanks.
-------------------------------------------------------------
Please click here to give me your feedback on this post!
South Africa
cabled
D-link DSL-2750U
no this only happens when i try log onto eu where all my data is. I am able to log onto other regions
Hey again RoyalFlush.

First, could you check that your router's firmware is fully up to date? Next, restart your computer completely and temporarily disable any anti-virus/firewall/security programs you have running in the background and then run the Battle.net Desktop as Administrator and try logging in to Diablo III.

Let us know how you get on.
-------------------------------------------------------------
Please click here to give me your feedback on this post!
People at one point were able to log in and then they weren't and you ask for router firmware??? Really?? I played today and now I cant log in because of that timeout. You want to know my router firmware in order to check if some weird update was made in the past 30 min??

You want players to test the patches before launch but dont give them the right environment to do so. Great job, as always...
Same here, getting the 3006 when loading character screen, i click ok and can then select character, press ok and another 3006, over and over until i try to exit and game crashes. Im gonna stick my neck out and say something is not working correct here :P
Same
Is this "local" ? I also play from Sweden, as I guess Skyggalisa is as well.
Great job Blizzard!!! Let the players help find bugs by NOT LETTING THEM PLAY!!! Please fix those !@#$ty servers of yours.
13/11/2015 21:32Posted by Stefan
Same
Is this "local" ? I also play from Sweden, as I guess Skyggalisa is as well.


Nah it seems like everyone is having problems, just found a thread on US forum stating that they are applying a hotfix to nerf legacy of nightmares from 800% damage to 100% damage, maybe thats whats going on atm.
Blizzard doesn't even provide enough hosting power cause it's 1 time payment game.
Best stick to free arpg at this rate..
why until now still have the TIMED OUT ERROR 3006 problem!? what i need to do to solve it?
09/04/2016 03:11Posted by WhiteLeaf
why until now still have the TIMED OUT ERROR 3006 problem!? what i need to do to solve it?

First of all, make sure you follow all the instructions in this article, including the advanced steps:
battle.net/support/article/611

If the issue persists after this, please provide us with the following information so we can look into it:

- Details of issue:
- Date/time it started:
- City/Country:
- Internet Provider:
- Traceroute (right after a disconnection or whenever you're experiencing the issue)
- Pathping (right after a disconnection or whenever you're experiencing the issue)
- Looking Glass report (right after a disconnection or whenever you're experiencing the issue)

______________________________________________________
Got feedback about the support I'm providing? Leave your comments here!
- Details of issue: Problems retrieving heroes list on Diablo 3
- Date/time it started: 10/22/2016
- City/Country: El TIgre, Venezuela
- Internet Provider: CANTV
- Traceroute (right after a disconnection or whenever you're experiencing the issue)
Tracing route to 24.105.30.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 21 ms 20 ms 20 ms 190-78-96-1.dyn.dsl.cantv.net [190.78.96.1]
3 22 ms 20 ms 20 ms 172.16.96.3
4 80 ms 80 ms 79 ms 10.150.0.189
5 74 ms 76 ms 75 ms 10.82.0.5
6 79 ms 79 ms 79 ms 10.150.0.210
7 149 ms 148 ms 149 ms so-5-0-0.mia13.ip4.gtt.net [199.168.63.129]
8 151 ms 147 ms 148 ms xe-5-2-3.cr0-mia1.ip4.gtt.net [89.149.180.185]
9 155 ms 153 ms 154 ms 192.205.32.93
10 209 ms 210 ms 210 ms igs1.fldfl.ip.att.net [12.122.155.170]
11 * * * Request timed out.
12 207 ms 207 ms 209 ms cr1.ormfl.ip.att.net [12.122.5.185]
13 213 ms 207 ms 209 ms cr2.hs1tx.ip.att.net [12.122.1.5]
14 212 ms 211 ms 213 ms cr1.hs1tx.ip.att.net [12.122.5.189]
15 211 ms 213 ms 208 ms cr2.dlstx.ip.att.net [12.122.2.121]
16 209 ms 210 ms 208 ms 12.122.2.82
17 233 ms 241 ms 238 ms gar29.la2ca.ip.att.net [12.122.129.241]
18 207 ms 206 ms 206 ms 12.122.251.190
19 213 ms 216 ms 284 ms 206.16.68.46
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 (right after a disconnection or whenever you're experiencing the issue)
Tracing route to 24.105.30.129 over a maximum of 30 hops

0 DESKTOP-IADOFR5 [192.168.250.4]
1 192.168.1.1
2 190-78-96-1.dyn.dsl.cantv.net [190.78.96.1]
3 172.16.96.3
4 10.150.0.189
5 10.82.0.5
6 10.150.0.210
7 so-5-0-0.mia13.ip4.gtt.net [199.168.63.129]
8 xe-5-2-3.cr0-mia1.ip4.gtt.net [89.149.180.185]
9 192.205.32.93
10 igs1.fldfl.ip.att.net [12.122.155.170]
11 * * *
Computing statistics for 250 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 DESKTOP-IADOFR5 [192.168.250.4]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 24ms 0/ 100 = 0% 0/ 100 = 0% 190-78-96-1.dyn.dsl.cantv.net [190.78.96.1]
0/ 100 = 0% |
3 --- 100/ 100 =100% 100/ 100 =100% 172.16.96.3
0/ 100 = 0% |
4 44ms 0/ 100 = 0% 0/ 100 = 0% 10.150.0.189
0/ 100 = 0% |
5 --- 100/ 100 =100% 100/ 100 =100% 10.82.0.5
0/ 100 = 0% |
6 76ms 2/ 100 = 2% 2/ 100 = 2% 10.150.0.210
0/ 100 = 0% |
7 150ms 0/ 100 = 0% 0/ 100 = 0% so-5-0-0.mia13.ip4.gtt.net [199.168.63.129]
2/ 100 = 2% |
8 146ms 2/ 100 = 2% 0/ 100 = 0% xe-5-2-3.cr0-mia1.ip4.gtt.net [89.149.180.185]
2/ 100 = 2% |
9 154ms 4/ 100 = 4% 0/ 100 = 0% 192.205.32.93
96/ 100 = 96% |
10 --- 100/ 100 =100% 0/ 100 = 0% igs1.fldfl.ip.att.net [12.122.155.170]

Trace complete.

- Looking Glass report:
TRACEROUTE:
traceroute to 190.78.110.72 (190.78.110.72), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.469 ms 0.599 ms 0.610 ms
2 * * *
3 37.244.0.102 (37.244.0.102) 2.847 ms 2.862 ms 2.867 ms
4 37.244.0.34 (37.244.0.34) 2.502 ms 2.540 ms 2.652 ms
5 te0-4-0-9.ccr41.lax05.atlas.cogentco.com (38.104.84.12) 37.591 ms 37.599 ms 39.006 ms
6 be3033.ccr22.lax01.atlas.cogentco.com (154.54.26.41) 37.171 ms 37.783 ms 37.881 ms
7 be2932.ccr22.phx02.atlas.cogentco.com (154.54.45.161) 36.984 ms 37.179 ms 37.178 ms
8 be2930.ccr21.elp01.atlas.cogentco.com (154.54.42.78) 37.020 ms 37.237 ms 37.235 ms
9 be2927.ccr21.iah01.atlas.cogentco.com (154.54.29.221) 37.468 ms 37.726 ms 37.318 ms
10 be2687.ccr41.atl01.atlas.cogentco.com (154.54.28.69) 51.487 ms 51.293 ms 51.393 ms
11 be2112.ccr41.dca01.atlas.cogentco.com (154.54.7.157) 62.761 ms 62.746 ms 63.192 ms
12 be2806.ccr41.jfk02.atlas.cogentco.com (154.54.40.105) 68.200 ms 68.204 ms 68.246 ms
13 be2056.ccr21.jfk10.atlas.cogentco.com (154.54.44.218) 69.294 ms 69.086 ms 69.062 ms
14 38.122.229.150 (38.122.229.150) 87.773 ms 87.524 ms 87.515 ms
15 200.16.69.46 (200.16.69.46) 87.945 ms 88.765 ms 88.762 ms

25/10/2016 01:07:23 UTC
--------------------
PING:
PING 190.78.110.72 (190.78.110.72) 56(84) bytes of data.

--- 190.78.110.72 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 4999ms

25/10/2016 01:07:23 UTC
--------------------
MTR:
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.5 0.6 0.4 1.2 0.2
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 37.244.0.102 0.0% 10 2.7 2.7 2.5 2.9 0.1
4. 37.244.0.34 0.0% 10 2.8 2.7 2.5 3.0 0.1
5. te0-4-0-9.ccr41.lax05.atlas.cogentco.com 0.0% 10 37.6 37.7 37.4 38.6 0.3
6. be3033.ccr22.lax01.atlas.cogentco.com 0.0% 10 37.3 37.2 37.1 37.5 0.1
7. be2932.ccr22.phx02.atlas.cogentco.com 0.0% 10 37.0 37.0 36.8 37.3 0.2
8. be2930.ccr21.elp01.atlas.cogentco.com 0.0% 10 37.8 37.2 37.0 37.8 0.2
9. be2927.ccr21.iah01.atlas.cogentco.com 0.0% 10 37.1 37.5 37.1 37.8 0.2
10. be2687.ccr41.atl01.atlas.cogentco.com 0.0% 10 51.6 51.2 51.0 51.6 0.2
11. be2112.ccr41.dca01.atlas.cogentco.com 0.0% 10 62.9 63.0 62.7 63.4 0.2
12. be2806.ccr41.jfk02.atlas.cogentco.com 0.0% 10 68.3 68.4 68.2 68.6 0.1
13. be2056.ccr21.jfk10.atlas.cogentco.com 0.0% 10 69.2 69.1 69.0 69.4 0.1
14. 38.122.229.150 0.0% 10 85.7 85.6 81.3 90.4 2.8
15. 200.16.69.46 0.0% 10 86.6 87.0 82.3 95.3 3.7
16. 200.16.71.78 0.0% 10 201.5 196.7 191.4 201.5 2.9
17. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

25/10/2016 01:07:23 UTC
--------------------
I got the same stupid 3006 error. I can log on EU and Asia servers, but not America's. I'm logging from Brazil and it's cable.

Join the Conversation

Return to Forum