Stuck connecting: Comcast, Washington area.

Technical Support
Prev 1 12 13 14 19 Next
At the AFK you say? I'm in Greenwood, too. Heading up there straight away.


We're about to leave from Ravenna. Expect us soon. :D
Be there in a bit - is everyone bringing their laptops??
Ran the repair tool and all that, still getting stuck on "Success!"

This is not successful, Bliz. :C
Still an issue as of 2pm. No WoW access via Comcast.
Silverdale/Bremerton area here. Same issues but I can't get on an of my alts in SW or surrounding areas. I can access my main on her farm tho.

I wish I was going with you guys, it sounds like so much fun! Have a great time!
I hope it's resolved before everyone rushes out of the door for the 4th of July holiday.
LOL i am actually having fun! Logged in and now I can fly without a mount.. making swimming motions and flying around Netherstorm lol even picked up a quest and still took off without a mount! ROFL
Just tried again, got in on main but once again nobody had names, friends list blank, guild list blank, can't check mail, can't talk to the npc's, can't chat, still has zero ms home on the latency.

For any blizz folk keeping track, once again I'm in Anacortes, Washington and I'm on Winterhoof server
Can get into the game but cant talk to NPC's, other players show as "unknown" issue started when I was doing arenas and I would get stuck on the loading screen at 80-100%

deleted cache and WTF. power cycled my modem to no avail. Renton, WA


Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms dlinkrouter.hsd1.wa.comcast.net [192.168.0.1]
2 8 ms 7 ms 7 ms 73.98.96.1
3 9 ms 10 ms 8 ms 68.87.205.217
4 10 ms 8 ms 9 ms ae-21-0-ar03.seattle.wa.seattle.comcast.net [69.
139.164.141]
5 14 ms 11 ms 11 ms he-1-7-0-0-11-cr01.seattle.wa.ibone.comcast.net
[68.86.93.5]
6 9 ms 9 ms 9 ms be-12-pe03.seattle.wa.ibone.comcast.net [68.86.8
4.106]
7 10 ms 9 ms 9 ms as7018-2.seattle.wa.ibone.comcast.net [66.208.22
9.102]
8 41 ms 40 ms 42 ms cr82.st0wa.ip.att.net [12.122.84.18]
9 42 ms 43 ms 43 ms cr2.ptdor.ip.att.net [12.122.5.230]
10 42 ms 42 ms 42 ms cr1.ptdor.ip.att.net [12.122.30.141]
11 42 ms 44 ms 47 ms cr1.sffca.ip.att.net [12.122.30.146]
12 41 ms 39 ms 39 ms cr1.la2ca.ip.att.net [12.122.3.122]
13 37 ms 37 ms 37 ms gar20.la2ca.ip.att.net [12.122.128.181]
14 40 ms 39 ms 39 ms 12-122-254-238.attens.net [12.122.254.238]
15 39 ms 39 ms 41 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.12
9.193.250]
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.
Same here!

Rochester, Washington... but no one know where that is :(


i know where it is only because i to live in the middle or rochester nowhere, makes this even worse for us =(
In Shoreline WA, using comcast, with the same issue. Logged into the Deeprun Tram, but when I hearthed to the Shrine I got stuck on the loading screen. D:

Can I also say it's really cool to see so many people from WA state who play Wow? Despite the issues we're having today? :D
I was able to login but then I took a portal to SW and the loading screen wouldn't load past like 90%. Anyone in Olympia wanna do some tight !@#$?
Hey guys. Gig Harbor here. Been stuck on "Success!" or "Retrieving realm list" for quite a while now.


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 13 ms 20 ms 17 ms 73.220.4.1
3 15 ms 39 ms 17 ms te-0-0-0-13-ur06.tacoma.wa.seattle.comcast.net [68.85.241.177]
4 177 ms 37 ms 18 ms ae-28-0-ar03.seattle.wa.seattle.comcast.net [69.139.164.205]
5 28 ms 22 ms 30 ms he-1-12-0-0-11-cr01.seattle.wa.ibone.comcast.net [68.86.93.177]
6 29 ms 17 ms 17 ms be-13-pe03.seattle.wa.ibone.comcast.net [68.86.84.110]
7 20 ms 17 ms 17 ms as7018-2.seattle.wa.ibone.comcast.net [66.208.229.102]
8 50 ms * * cr82.st0wa.ip.att.net [12.122.84.18]
9 57 ms 55 ms 46 ms cr2.ptdor.ip.att.net [12.122.5.230]
10 51 ms 47 ms 49 ms cr1.ptdor.ip.att.net [12.122.30.141]
11 49 ms 47 ms 47 ms cr1.sffca.ip.att.net [12.122.30.146]
12 49 ms 60 ms 45 ms cr1.la2ca.ip.att.net [12.122.3.122]
13 50 ms 48 ms 96 ms gar20.la2ca.ip.att.net [12.122.128.181]
14 46 ms 48 ms 48 ms 12-122-254-238.attens.net [12.122.254.238]
15 48 ms 51 ms 56 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
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.
same exact issues here, have not been able to get in all morning on my 90's, can get in with lowbies but nothing works, no guild info, chat, mailboxes, people are running in place with UNKNOWN above them with no names. log in bar goes 3/4 and freezes, can't log out correctly, have to alt/tab and close. This is beyond annoying, can't get through to Comcast...power cycled modem, restarted, tried other computer...nothing... :(
Reporting from Snohomish!

No success.

When I could get in, the chat server was working fine, interestingly enough.

Cheers, folks.
Checking in from Sammamish
I'm in, I can chat, zone out and in, run around fine. BUT. Only on low level characters. 1-30. My 90s are still locked out.
Bellevue, WA

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 2 ms 1 ms 1 ms www.asusnetwork.net [192.168.1.1]
2 13 ms 11 ms 9 ms 73.96.168.1
3 15 ms 17 ms 11 ms te-0-0-0-11-ur06.bellevue.wa.seattle.comcast.net
[68.86.113.137]
4 16 ms 11 ms 15 ms ae-18-0-ar03.seattle.wa.seattle.comcast.net [69.
139.164.117]
5 20 ms 21 ms 13 ms he-1-5-0-0-10-cr01.seattle.wa.ibone.comcast.net
[68.86.94.57]
6 19 ms 15 ms 17 ms be-17-pe03.seattle.wa.ibone.comcast.net [68.86.8
3.14]
7 14 ms 17 ms 19 ms as7018-2.seattle.wa.ibone.comcast.net [66.208.22
9.102]
8 * 45 ms 49 ms cr82.st0wa.ip.att.net [12.122.84.18]
9 48 ms 46 ms 43 ms cr2.ptdor.ip.att.net [12.122.5.230]
10 54 ms 51 ms 47 ms cr1.ptdor.ip.att.net [12.122.30.141]
11 43 ms 46 ms 41 ms cr1.sffca.ip.att.net [12.122.30.146]
12 48 ms * 46 ms cr1.la2ca.ip.att.net [12.122.3.122]
13 41 ms 43 ms 41 ms gar20.la2ca.ip.att.net [12.122.128.181]
14 44 ms 45 ms 57 ms 12.122.251.190
15 47 ms 47 ms 47 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54]

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.
Spokane, WA
Same issues as everyone else =/
Sup all my Washington nerds :) Here in Everett as well, and of course no luck. But remember, its NEVER Comcast's fault.. its always something on our end *sarcasm. I swear we know more about tech procedures than most of the people who work there. Guess I'll just / kneel and pray to Uther.
Internet is working fine. it's just wow. wondering what is wrong with wow/comcast when the internet works doing anything else...so confused

Join the Conversation

Return to Forum