Diablo® III

Random Disconnects

I have been disconnected three times within 30 minutes this morning.
Reply Quote
Been having the same problem, it does get very annoying, specially once you've gotten 5 stack, and then bang, disconnected. On some days, it wont do it, and others, it happens more than once an hour.... I am not using laptop, not using wireless network. Hopefully the problem will get fixed.....
Reply Quote
I am getting dc'd all the time as well and it only happens while playing d3.
Reply Quote
Happened to me twice today. Been having this issue for a few months now. Its sucks cuz I want to play Hardcore!
Reply Quote
Posts: 476
Me Too here,now just cant finish a single alkaiser run...
Reply Quote
D/C still happening, bump
Reply Quote
This has been happening to me also. It amazes me that this thread has been here for this many days and there isn't a single blue response.

Looks like I have to stop playing my Barbarian now since it's too frustrating getting disconnected all the time.
Reply Quote
Is anyone else getting booted from their games.

I thought it was a connection problem at the start, but that has been checked and checked again. All is actually fine. I play other games and have no problems at all.

My latency is fine.

It does not boot me out altogether, just to the Act Selection screen.
It really sucks when you have just got your 5 stack.


Me too, My latency are Fine.
The ratio of me completing the whole Act 3 run is about 1:12.
Meaning that 11 out of 12 games ends up being disconnected.

Its NOT only localize on Barb,
Im using Monk....
Edited by WhiteBootz#6395 on 3/22/2013 4:48 PM PDT
Reply Quote
Just to clarify, I am NOT using a Barb while getting booted from games!
Reply Quote
This issue has happened for me recently, starting last week. I have looked on the forums and found a myriad of suggestions, none that seem quick or easy. Here's what I've done so far that hasn't worked:
1. Power cycled the router and modem(though I'm sure my modem is on my MB so I just turned off my computer).
2. I erased cache files.
3. made sure my network adapter was updated.

Things to try
1. At&t is supposed to be coming today, that takes care of any ISP concerns.
2. updating anymore drivers?

update: while i typed this post I ran a trace route, Results -

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 2 ms 2 ms 1 ms dsldevice.att.net [192.168.1.254]
2 13 ms 11 ms 13 ms 99-107-92-3.lightspeed.stlsmo.sbcglobal.net [99.107.92.3]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 10 ms 11 ms 11 ms 12.83.40.5
7 61 ms 59 ms 61 ms gar29.la2ca.ip.att.net [12.122.129.241]
8 63 ms 61 ms 62 ms 12-122-254-238.attens.net [12.122.254.238]
9 62 ms 62 ms 62 ms 206.16.68.46
10 * * * Request timed out.
11 * * * Request timed out.
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.
Reply Quote
I have a business class internet and it takes me 3 hop to connect to google's server, But when i run a tracert report for Blizzards servers. I get bumped all over the country. And go through Costa mesa, to kansas, to chicago, back to multiple IPS in kansas...then finally to (-netstat server in game) which is in San Diego...
I live in Chicago. SO why do I hop to california then to kansas then to chicago then back to kansas, then to california??

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms (my ip here not going to display)
2 10 ms 8 ms 8 ms 64.145.107.1 (Costa Mesa)
3 18 ms 8 ms 8 ms 155.229.57.41 (Costa Mesa)
4 28 ms 124 ms 50 ms ge-3-7.car2.Chicago1.Level3.net [4.71.182.41] Chicago
5 51 ms 27 ms 27 ms ae-31-51.ebr1.Chicago1.Level3.net [4.69.138.30] Chicago
6 26 ms 26 ms 26 ms ae-6-6.ebr1.Chicago2.Level3.net [4.69.140.190] Chicago
7 26 ms 50 ms 51 ms 4.69.158.133 (Wichita, KS)
8 28 ms 27 ms 32 ms 192.205.37.149 (Wichita, KS)
9 64 ms 89 ms 66 ms cr1.cgcil.ip.att.net [12.122.133.34] (att=bnet, but location is still in KS)
10 64 ms 65 ms 78 ms cr2.dvmco.ip.att.net [12.122.31.85] (Wichita, KS)
11 67 ms 66 ms 67 ms cr1.slkut.ip.att.net [12.122.30.25] (Wichita, KS)
12 64 ms 81 ms 65 ms cr2.la2ca.ip.att.net [12.122.30.30] (Wichita, KS)
13 64 ms 85 ms 65 ms gar29.la2ca.ip.att.net [12.122.129.241] (Wichita, KS)
14 75 ms 64 ms 67 ms 12-122-254-234.attens.net [12.122.254.234] (Wichita, KS)
15 63 ms 64 ms 86 ms 12.129.193.254 SAN DIEGO


Trace complete.

Now here is to google:
Tracing route to www.google.com [173.194.75.105]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms (mine will not display)
2 29 ms 8 ms 8 ms 64.145.107.1
3 8 ms 8 ms 18 ms ge-0-1-2-0.chcgilgb-mxc1.bb.megapath.net [155.229.70.57]
4 8 ms 8 ms 42 ms ae0-0.chcgilgb-mxc2.bb.megapath.net [155.229.57.22]
5 37 ms 10 ms 10 ms 206.223.119.211
6 59 ms 74 ms 64 ms 216.239.48.183
7 * * * Request timed out.(google security)
8 40 ms 40 ms 40 ms ve-in-f105.1e100.net [173.194.75.105]

Trace complete.
Edited by Michael#13785 on 3/25/2013 2:12 PM PDT
Reply Quote
Not sure what this means but i did a tracert as well.

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 40 ms 28 ms 29 ms c-76-25-64-1.hsd1.co.comcast.net [76.25.64.1]
2 8 ms 9 ms 11 ms te-9-1-ur05.littleton.co.denver.comcast.net [68.85.107.217]
3 20 ms 11 ms 11 ms te-0-5-0-13-ar02.denver.co.denver.comcast.net [68.85.89.209]
4 13 ms 15 ms 16 ms pos-0-7-0-0-ar02.aurora.co.denver.comcast.net [68.86.128.246]
5 22 ms 16 ms 15 ms he-3-9-0-0-cr01.denver.co.ibone.comcast.net [68.86.92.21]
6 30 ms 28 ms 27 ms pos-0-7-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.89.198]
7 26 ms 43 ms 25 ms be-10-pe02.1950stemmons.tx.ibone.comcast.net [68.86.82.130]
8 32 ms 31 ms 27 ms as7018-pe01.1950stemmons.tx.ibone.comcast.net [75.149.230.162]
9 58 ms 54 ms 61 ms cr2.dlstx.ip.att.net [12.123.16.110]
10 59 ms 55 ms 54 ms cr2.la2ca.ip.att.net [12.122.28.178]
11 57 ms 61 ms 53 ms gar29.la2ca.ip.att.net [12.122.129.241]
12 52 ms 76 ms 54 ms 12-122-254-238.attens.net [12.122.254.238]
13 53 ms 52 ms 54 ms 206.16.68.54
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 * *
Reply Quote
This always happens to me and is really obnoxious. Why is this happening so much? Theres no excuse for something like this.
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]