Constant disconnects

Technical Support
Today I've been experiencing constant disconnects from World of Warcraft. I can stay connected to the server at times for around 20 minutes sometimes an instant DC after loading into the game. World of warcraft seems to be the only unstable problem I'm seeing, I live in Washington St. if that matters.
It sounds like a temporary issue in your area, Toxxel. Usually it's just a matter of time before the connection goes back to normal. Do you know if any of your guildmates in Celestial Vanguard are disconnecting too?
________________________________________________
Account and Technical Services
If the Forum isn't helping, contact a Support Rep directly: http://us.blizzard.com/en-us/company/about/contact.html
'Black holes are where God divided by zero.'
Rate Me! https://www.surveymk.com/s/R6BG5YS
Since I downed the boss in BH, the moment I got that achievement, I've been getting DC'ed from the game servers every 10-15 minutes, with 83ms, no connection issues in tracert, ping, antivirus scans, and all addons are uninstalled at the moment. Was doing fine prior to downing the boss, but since after I killed him, it's been constant; Whether I'm in Stormwind, or if I'm in the oh-so-empty Ferelas. This, strangely, has only been occurring when I'm on the Twisting Nether server.

Am I just a victim of RNG packet losses to the server, or is there something connected through a possible achievement-zone based memory leak? Or are the AT&T servers hosting the WoW realms in Chicago having problems with connection stability?

No problems thus yet when I'm on Scilla, Dragonmaw, Baelgun, Lightbringer or Eredar.


Thought I would bring a thread I started, not seeing this one, to here.

But I don't think it would be local, cause... I really doubt this many people are having DC's problems, and are living near me in the middle-of-no-where Northern Idaho. >,>
Same here, theres a thread with almost 60 pages about this same issue but Blizzard is not doing anything
LA huh... And my realm is a Chicago server... I don't even touch LA through the tracerts when I go through the hops to the Twisting Nether Server, Though, I go from north Idaho, to Washington, to Montana, to North Dakota, then finally hitting Minnesota, Canada(for some reason), Michigan, Wisconsin, then finally Chicago Illinois.


I'm starting to think it's a AT&T problem with their server hosting rather then a Blizzard problem, or I would of thought I would have seen posts about it somewhere.
No one else is getting disconnected in my guild, but then again I'm playing on an east coast based server most people aren't in my neck of the woods in the guild or that I know of.
Usually when I'm playing and there's an issue on the server, everyone in my guild will speak up either in Voice Chat, Vent, or Teamspeak, and everyone else will too, in General, Trade, or Guild chat. If there's not a widespread issue on the server, then it comes down to the particular connection route through the Internet, from your location, to our servers.

You can see any possible issues (and there may be many, considering the weather around the country) along the connection route with a trace route.

Hit the Windows Key + R, and type:

cmd

In the command window, type:
tracert 206.17.111.92 > c:\trace.txt
You'll want to use your own realm's IP address in the example above, which you can find here:

http://www.wowpedia.org/US_realm_list_by_datacenter

It will take a few minutes to finish. After its done, open My Computer, and then your c: drive. Open the trace.txt file, and copy and paste the contents into a new post.

When your Trace hits our network, you will see this in the last several lines of the Trace Route:
* * * Request timed out.
This is normal, and intentional, on our part. Our network is set to not respond to Trace Routes.

Please also show or describe or email your Trace Route to your ISP. They can fully interpret and diagnose your Trace Route in detail, and run further tests.
________________________________________________
Account and Technical Services
If the Forum isn't helping, contact a Support Rep directly: http://us.blizzard.com/en-us/company/about/contact.html
'Black holes are where God divided by zero.'
Rate Me! https://www.surveymk.com/s/R6BG5YS
Well, I now have a different route pathing to Chicago then what I had a few hours ago.


Tracing route to 206.18.149.21 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 7 ms 7 ms 76.61.16.1
3 7 ms 7 ms 11 ms gig1-2.mscwid-rtr1.natnow.rr.com [65.28.217.9]
4 13 ms 7 ms 9 ms gig4-6.plmnwa-rtr1.natnow.rr.com [65.28.218.106]
5 28 ms 27 ms 27 ms ge-3-1-0.cr1.sea20.tbone.rr.com [66.109.6.90]
6 27 ms 27 ms 27 ms ae-1-0.pr0.sea20.tbone.rr.com [66.109.6.149]
7 28 ms 29 ms 29 ms te-4-3.car4.Seattle1.Level3.net [4.71.156.109]
8 29 ms 63 ms 28 ms ae-1-51.edge1.Seattle3.Level3.net [4.68.105.12]
9 29 ms 28 ms 29 ms 192.205.36.153
10 95 ms 94 ms 93 ms cr2.st6wa.ip.att.net [12.122.146.178]
11 94 ms 94 ms 95 ms cr2.cgcil.ip.att.net [12.122.31.129]
12 95 ms 95 ms 95 ms cr84.cgcil.ip.att.net [12.123.7.249]
13 93 ms 93 ms 93 ms gar4.cgcil.ip.att.net [12.122.132.217]
14 95 ms 95 ms 93 ms 12-122-254-202.attens.net [12.122.254.202]
15 95 ms 94 ms 94 ms 63.240.130.206
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
Having the same problem that I also posted about yesterday.


Tracing route to 199.107.24.244 over a maximum of 30 hops

1 1 ms <1 ms <1 ms phub.net.cable.rogers.com [192.168.0.1]
2 7 ms 6 ms 7 ms 10.26.8.1
3 8 ms 8 ms 8 ms 69.63.242.85
4 13 ms 9 ms 9 ms pos-0-0.gw01.pr.phub.net.cable.rogers.com [66.185.81.174]
5 34 ms 25 ms 25 ms 24.153.5.70
6 29 ms 28 ms 26 ms TenGigabitEthernet9-2.ar7.NYC1.gblx.net [64.208.169.149]
7 26 ms 26 ms 26 ms 192.205.37.137
8 28 ms 27 ms 30 ms cr1.n54ny.ip.att.net [12.122.81.58]
9 29 ms 28 ms 29 ms cr83.n54ny.ip.att.net [12.122.105.50]
10 26 ms 26 ms 26 ms gar20.n54ny.ip.att.net [12.122.131.249]
11 31 ms 32 ms 28 ms 12-122-254-114.attens.net [12.122.254.114]
12 27 ms 29 ms 28 ms mdf001c7613r0004-gig-12-1.nyc3.attens.net [63.240.65.14]
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.
I too have been disconnecting. If I am lucky I can get to the character select screen. I did manage to play for a little while today, but with constant DCing. Didn't matter the character, server, or area. I am seeing people from all over the country are having this issue. I am on the East Coast as are the servers I play on.
I have been getting disconnected every 5-10 minutes since Tuesday. I have reset the router numerous times and my internet works fine, I just can't play wow. Here is my trace output.

Tracing route to 206.18.98.204.tms-idc.com [206.18.98.204] over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 11 ms 7 ms 9 ms 69.63.255.209
4 13 ms 13 ms 13 ms 69.63.249.9
5 19 ms 19 ms 15 ms so-0-0-0.gw02.mtnk.phub.net.cable.rogers.com [66.185.80.170]
6 32 ms 46 ms 32 ms 69.63.251.129
7 34 ms 91 ms 33 ms TenGigabitEthernet9-2.ar7.NYC1.gblx.net [64.208.169.149]
8 41 ms 40 ms 40 ms 192.205.34.77
9 41 ms 41 ms 42 ms cr1.cgcil.ip.att.net [12.122.84.50]
10 41 ms 39 ms 39 ms cr83.cgcil.ip.att.net [12.123.7.109]
11 41 ms 39 ms 39 ms gar4.cgcil.ip.att.net [12.122.133.205]
12 39 ms 40 ms 41 ms 12-122-254-202.attens.net [12.122.254.202]
13 42 ms 40 ms 41 ms 63.240.130.206
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.

For the last 2 or 3 days I've been constantly dc'ing as well. I can rarely play for more than 5 consecutive minutes. I've tried everything in the Blizz FAQ. I have friends within a 5 minute walk of me, using the same ISP who are having no issues. Here's my traceroute:

Tracing route to 206.18.98.208.tms-idc.com [206.18.98.208]
over a maximum of 30 hops:

1 4 ms 1 ms 1 ms 192.168.1.1
2 11 ms 24 ms 10 ms 10.20.132.1
3 9 ms 10 ms 11 ms 67.231.221.57
4 9 ms 9 ms 12 ms 69.63.249.53
5 10 ms 11 ms 11 ms 69.63.249.93
6 15 ms 15 ms 12 ms 69.63.251.241
7 30 ms 31 ms 32 ms 69.63.248.194
8 29 ms 29 ms 30 ms TenGigabitEthernet9-2.ar7.NYC1.gblx.net [64.208.169.149]
9 37 ms 37 ms 36 ms 192.205.34.165
10 38 ms 39 ms 41 ms cr2.cgcil.ip.att.net [12.122.86.42]
11 38 ms 36 ms 36 ms cr84.cgcil.ip.att.net [12.123.7.249]
12 37 ms 40 ms 37 ms gar4.cgcil.ip.att.net [12.122.132.217]
13 39 ms 39 ms 52 ms 12-122-254-202.attens.net [12.122.254.202]
14 37 ms 39 ms 40 ms 63.240.130.202
15 *
The game has been nearly to totally unplayable for me for the last two weeks. At my apartment its totally fine, but if I take my computer to my parent's house (xmas break..) it won't work at all. I decided to try using my parent's computer and installed it.. it works, but still has the same problem (about 1/3 of the time I log in and cannot play).

I get instantly DC'd the moment I log into the game, but the odd part is I DON'T get DC'd. I can still move around, and even talk to others for about 10 minutes before getting logged. My latency hovers around 100. I cannot use any abilities or interact with the world in any way other than the chat system however.

I have no other problems with any other programs or use of the internet. My parent's internet is actually faster and more stable than what I have at my apartment.
Same issue as everyone else. Stops at the same hop. 1400ms+ latency


traceroute to 206.18.98.248 (206.18.98.248), 30 hops max, 40 byte packets
1 69.42.223.146 (69.42.223.146) 0.055 ms 0.011 ms 0.009 ms
2 awk-cr01.lax01.awknet.com (67.220.95.1) 0.243 ms 0.294 ms 0.354 ms
3 v150.core1.lax2.he.net (216.218.207.41) 0.240 ms 0.315 ms 0.375 ms
4 las-b3-link.telia.net (213.248.101.29) 0.315 ms 0.368 ms 0.390 ms
5 80.91.252.33 (80.91.252.33) 0.332 ms 80.91.252.29 (80.91.252.29) 0.293 ms 80.91.252.33 (80.91.252.33) 0.355 ms
6 192.205.34.13 (192.205.34.13) 0.559 ms 0.638 ms 0.651 ms
7 cr2.la2ca.ip.att.net (12.122.129.102) 58.556 ms 58.613 ms 58.603 ms
8 cr1.slkut.ip.att.net (12.122.30.29) 58.291 ms 58.290 ms 58.278 ms
9 cr2.dvmco.ip.att.net (12.122.30.26) 59.005 ms 59.005 ms 59.107 ms
10 cr1.cgcil.ip.att.net (12.122.31.86) 59.216 ms 59.208 ms 59.197 ms
11 cr83.cgcil.ip.att.net (12.123.7.109) 58.443 ms 58.436 ms 57.960 ms
12 gar4.cgcil.ip.att.net (12.122.133.205) 57.443 ms 57.494 ms 57.465 ms
13 12-122-254-202.attens.net (12.122.254.202) 58.321 ms 58.397 ms 58.430 ms
14 63.240.130.206 (63.240.130.206) 58.223 ms 63.240.130.202 (63.240.130.202) 58.725 ms 63.240.130.206 (63.240.130.206) 58.261 ms
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Pharque, that's an odd tracert result format. You on a mac? Maybe linux?

Anyway, your connection to the server seems alright.

I see... (For the posts with actual addresses) that a large chunk of us, are using Roadrunner, through different servers on opposite sides of the country, and even on different routes that aren't connecting to each other. (With the exception of the 2 people connecting to Rochester NY). Odd.

I would say, give it a few more days, maybe a week once most of these bad storms have past and most of the US Weather is calm.
Well I'm in Canada and there were no winter storms or anything of that nature and I've been randomly DCing at certain times of the day. Usually in the morning and after 7pm EST. I've come to the conclusion that my ISP is being throttled by another ISP(they're throttling p2p at certain times of the day, but how does this affect WoW?). I've never had this problem up untill the release of Cataclysm. Is blizzard doing anything about this?

My ISP is TekSavvy Solutions and they're being throttled by Bell. I remember reading in an earlier thread that Blizzard is in contact with Bell about this problem. Has anything become of it? Thanks.
Canada or not, You're still playing on US servers. All the North American WoW realms are in 4 datacenters here in the US. LA, Phonix, Chicago, and New York as of the summer of this last year.

I imagine once AT&T gets their act together, that these datacenters will be linked together so there wont be battlegroups anymore, and all the realms will be linked together for LFG and Battle Grounds.

Join the Conversation

Return to Forum