Time Warner Instance Load Screen Hanging

Technical Support
Prev 1 11 12 13 33 Next
duplicate post
Upstate NY
Kansas City
NC

amazing how many times these regions appear in this thread
With anyone experiencing this issue, I've discovered a decent way to help you not get booted from groups. If you see your load is taking longer than it should, alt+tab and crash the game (I right click it on the taskbar and click Close). Relaunch the game and login. You might get a "You have been disconnected from the server." after this because the game thinks you're still logged in. But try one more time and it should let you in (or freeze again, if so try again). I'm usually able to do this fast enough where I don't get booted from group.
I have been having this problem for like 9 days now, i have been posting on another forum and the blues said that the problem was fixed but its still doing the same thing, any time i get a load screen, coming in or out of a dungeon, or in and out of pvp or game, i get a load screen freeze, its really impossible to play at this point, im fet up with it to be honest. fix this or im done with wow.

There was a specific issue with one ISP a few days ago that was resolved, but this issue is continuing to affect a small number of accounts scattered across many ISPs.
________________________________________________
Account and Technical Services || Tues - Sat 645 - 1545 PST
Not seeing a resolution on the forums? Contact a Support Rep directly! - http://us.blizzard.com/en-us/company/about/contact.html

Experience is simply the name we give our mistakes.
Like the post? Comments or suggestions? Submit a survey here, please - http://www.surveymk.com/s/RMW9Y6X


When people complain about problems with ISPs, they are often told to switch to another ISP if they're not happy with the one they have. Can you please tell us which ISP you are referring to?
01/06/2011 10:01 PMPosted by Hymie
Rochester, NY TWC

Approximately 50% of the time my girlfriend and I load into an instance, arena, or battleground, the load screen freezes, and eventually disconnects.

This's also often followed by severe lag spikes (1000ms+) upon logging back into the game after force closing the game.

Exact same issues for me.

TWC, KC Missouri.

I've been using my same connection for the past 2 years with no issues. Shortly after Cataclysm release, I started having these problems constantly. I provided some traceroutes in another thread, will be more than happy to provide any other data to get this resolved.
I am in S. Maine, using TWC. Something that I find great humor in, is that this happens immediately after cata release, and anyone could even begin to blame it on the ISP.
TWC Desert Cities (San Diego, So Cal), connecting to Dark Iron in Chicago data center.

Periods of really bad lag, some of which can be associated with just downright crappy TWC service in general, but other times other connections work fine... but WoW suffers.
Im having the same problam here in Toronto On and its really anoying like ive only had the game scince Christmas and its doing this to my main character ...like why should people pay for a game the eventualy glitches and wont let you play.
TWC KC,MO

i am having this exact issue along with random lag spikes of up to 8k. Just posted tracert and info in the other time warner sticky.
ISP - Time Warner Cable (Road Runner Cable Connection)
Rochester, NY

This started happening on December 10th, 2010 the first time I ran a heroic CATA dungeon.

Realm: Earthen Ring (US)

This happen when entering or exiting dungeons. Either releasing from them after death, entering them as a ghost, or just entering or leaving them. That loading bar freezes up about 75% of the time.

Tracing route to 206.18.99.105 over a maximum of 30 hops

1 * * * Request timed out.
2 21 ms 13 ms 22 ms gig4-3.rochnygts-rtr01.nyroc.rr.com [24.93.4.153]
3 8 ms 9 ms 31 ms gig1-0-4.rochnymth-rtr03.nyroc.rr.com [24.93.0.214]
4 10 ms 8 ms 16 ms xe-4-1-0-0.rochnyei-rtr000.nyroc.rr.com [24.92.224.10]
5 23 ms 24 ms 23 ms ae-3-0.cr0.chi10.tbone.rr.com [66.109.6.72]
6 28 ms 28 ms 28 ms ae-0-0.pr0.chi10.tbone.rr.com [66.109.6.153]
7 29 ms 28 ms 27 ms xe-10-1-0.edge2.Chicago2.Level3.net [4.59.28.105]
8 38 ms 29 ms 32 ms ae-2-52.edge4.Chicago2.Level3.net [4.69.138.167]
9 32 ms 26 ms 26 ms 192.205.37.149
10 38 ms 25 ms 25 ms cr2.cgcil.ip.att.net [12.122.81.22]
11 27 ms 31 ms 24 ms cr84.cgcil.ip.att.net [12.123.7.249]
12 27 ms 25 ms 23 ms gar4.cgcil.ip.att.net [12.122.132.217]
13 32 ms 29 ms 27 ms 12-122-254-202 begin_of_the_skype_highlighting 12-122-254-202 end_of_the_skype_highlighting begin_of_the_skype_highlighting 12-122-254-202 begin_of_the_skype_highlighting 12-122-254-202 end_of_the_skype_highlighting end_of_the_skype_highlighting begin_of_the_skype_highlighting 12-122-254-202 begin_of_the_skype_highlighting 12-122-254-202 end_of_the_skype_highlighting begin_of_the_skype_highlighting 12-122-254-202 begin_of_the_skype_highlighting 12-122-254-202 end_of_the_skype_highlighting end_of_the_skype_highlighting end_of_the_skype_highlighting.attens.net [12.122.254.202]
14 39 ms 25 ms 25 ms 63.240.130.202
15 * * * Request timed out.
16 * * * Request timed out.
(Continues to time out until 30)

Tracing route to 206.18.149.72 over a maximum of 30 hops

1 * * * Request timed out.
2 18 ms 8 ms 9 ms gig4-2.rochnygts-rtr01.nyroc.rr.com [24.93.4.149]
3 9 ms 12 ms 17 ms srp13-0.rochnymth-rtr03.nyroc.rr.com [24.93.3.119]
4 9 ms 6 ms 9 ms xe-4-2-0-0.rochnyei-rtr000.nyroc.rr.com [24.92.224.14]
5 21 ms 22 ms 24 ms ae-3-0.cr0.chi10.tbone.rr.com [66.109.6.72]
6 25 ms 25 ms 23 ms ae-0-0.pr0.chi10.tbone.rr.com [66.109.6.153]
7 27 ms 24 ms 25 ms xe-10-0-0.edge2.Chicago2.Level3.net [4.59.28.101]
8 32 ms 23 ms 26 ms ae-2-52.edge4.Chicago2.Level3.net [4.69.138.167]
9 26 ms 25 ms 36 ms 192.205.37.149
10 26 ms 23 ms 24 ms cr2.cgcil.ip.att.net [12.122.81.22]
11 25 ms 27 ms 23 ms cr84.cgcil.ip.att.net [12.123.7.249]
12 26 ms 23 ms 23 ms gar4.cgcil.ip.att.net [12.122.133.205]
13 24 ms 29 ms 26 ms 12-122-254-202 begin_of_the_skype_highlighting 12-122-254-202 end_of_the_skype_highlighting begin_of_the_skype_highlighting 12-122-254-202 begin_of_the_skype_highlighting 12-122-254-202 end_of_the_skype_highlighting end_of_the_skype_highlighting.attens.net [12.122.254.202]
14 23 ms 25 ms 25 ms 63.240.130.202
15 * * * Request timed out.
16 * * * Request timed out.
(Continues until 30)
I have had this issue since I installed Cataclysm.

I have played since Vanilla with no issues till now.

Of course, ISP is TWC out of Albany NY.

I just stopped releasing in raids and wait for a rez when we wipe due to our tank DC's everytime the boss is pulled because his ISP is Brighthouse.
I'm seeing this exact issue. I've had to stop releasing in raids as well as it only seems to occur during the loading screens.

I'm on TWC in Kansas City MO.

Running Win 7 and had no noticeable issues until cataclysm release.

Never have an issue logging into the game, just loading into instances. This occurs in Battlegrounds as well as Raid and dungeon instances.
I ran a heroic earlier and was fine (never died though). I just attempted to run heroic Deadmines. We wiped a few times and getting back to my corpse was never an issue.. until 7 pm rolls around. Got stuck on the loading screen and they booted me. This is so much fun. So yes, it seems to be a primetime issue for me too.
Yeah, having same issue here quite annoying when trying to arena or raid.

I'm on TWC Kansas City, Kansas

Random getting stuck at loading screens and have to close wow and restart, and even then its a gamble as to whether i get in. Also happens that the loading screen will take some time to load, but then I will get in the instance/arena and lag like crazy.

*update* Little thing I noticed, even though my launcher says WoW is up to date, when I first log in it has the little green circle that says game data is still being downloaded. Is there a reason for that?
Been having this same issue since Cata - New England user of TWC, loading screen hangups, blue bar loading to full and then stuck there till an alt f4. Happens zoning in to dungeons, zoning out, pvp, and loading into the game itself - running no mods at this time.

Hoping for a fix soon, playing like this is very discouraging and frustrating!

Figured out how to run the trace-

Tracing route to us.logon.battle.net [12.129.206.130]

over a maximum of 30 hops:



1 26 ms 25 ms 25 ms 192.168.1.1

2 32 ms 34 ms 34 ms 10.107.96.1

3 10 ms 33 ms 33 ms g5-1-24.spldme47-rtr001.ne.northeast.rr.com [24.31.154.156]

4 41 ms 41 ms 36 ms g10-6-0-0.ptldmehx-rtr001.ne.northeast.rr.com [204.210.69.218]

5 19 ms 44 ms 46 ms rdc-204-210-69-49.ne.northeast.rr.com [204.210.69.49]

6 29 ms 53 ms 64 ms ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74]

7 53 ms 54 ms 53 ms ae-1-0.pr0.nyc30.tbone.rr.com [66.109.6.161]

8 31 ms 69 ms 51 ms xe-5-3-0.edge2.Newark1.Level3.net [4.59.20.37]

9 70 ms 61 ms 60 ms ae-31-51.ebr1.Newark1.Level3.net [4.68.99.30]

10 56 ms 53 ms 52 ms ae-2-2.ebr1.NewYork1.Level3.net [4.69.132.97]

11 29 ms 61 ms 61 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66]

12 38 ms 55 ms 62 ms ae-1-69.edge3.NewYork1.Level3.net [4.68.16.17]

13 53 ms 61 ms 54 ms 192.205.37.69

14 99 ms 131 ms 125 ms 12.122.81.126

15 129 ms 124 ms 139 ms cr2.cgcil.ip.att.net [12.122.1.2]

16 100 ms 124 ms 127 ms cr1.cgcil.ip.att.net [12.122.2.53]

17 122 ms 124 ms 126 ms cr2.dvmco.ip.att.net [12.122.31.85]

18 123 ms 125 ms 124 ms cr1.slkut.ip.att.net [12.122.30.25]

19 106 ms 141 ms 131 ms cr2.la2ca.ip.att.net [12.122.30.30]

20 124 ms 125 ms 124 ms cr84.la2ca.ip.att.net [12.123.30.249]

21 100 ms 126 ms 124 ms gar5.la2ca.ip.att.net [12.122.129.25]

22 97 ms 124 ms 125 ms 12.122.255.74

23 124 ms 135 ms 122 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.129.193.246]

24 * 12.129.211.38 reports: Destination net unreachable.



Trace complete.
I have this exact same issue connecting to Windrunner which is in the LA data center. I am using TWC in Kansas City.
The vast majority of people reporting this are going to the Chicago DC, but I have seen one or two verified reports of instance zoning to the LA DC. Any more data would be appreciated.
I'm another KC TWC user and I'm having the instance loading screen issue with characters on both Spinebreaker (Chicago data center) and Windrunner (LA data center).
Problem is still persisting, Jan. 5th went a whole day without the lag or my MS/Ping spiking, now it's still doing it at a set time here in California, Inland Empire around 5-6:00PM. Ping will go to 300-500. 3 weeks en-counting.
Time Warner Cable buffalo NY

same problem have played since vanilla never had this issue before now since cata launched it seems to be about 50/50 if i get past a loading screen or not
Exact same problem as everyone else on this thread.

TWC Rochester, NY.

Extremely annoying, and moreso because I feel bad for making people wait for me to get back in!!!
Bump, I'm in the same boat as many others here.

Shocker...wait for it....Northern NY, TWC customer, Aggramar (Chicago server).

Only problem I seem to have is zoning in/out of instances. Sometimes it works, sometimes I freeze on loading bar.

I've spent some time on the phone and testing with TWC, they swear my line is fine.

I've also checked my addons/system/drivers/run WoW repair,etc.

Any more offical news from you Blue folks? Ideas of what the problem might be and a timeframe for resolution?

Join the Conversation

Return to Forum