Login Issues 3/26

#0 - March 26, 2008, 7:36 a.m.
Blizzard Post
Hey everyone,

It appears that a number of Battlegroups are having connectivity issues.

We're investigating further and we ask your patience while we do so. I'll be adding more information as I get it.

Please post in this thread if you wish to discuss the issue or look for updates.

Thanks!

---

UPDATE 1:41 CST

Please post your traceroute here if you're having connectivity issues for further diagnosis:

http://forums.worldofwarcraft.com/thread.html?topicId=5540036362&sid=1

---

UPDATE 2:26 CST

Still investigating. For specific replies, feel free to use the Next Blizzard Post button to skip through the rabbling.

--

UPDATE 2:56 CST

We may have an incoming fix that will resolve the stuck-in-limbo issue. I'll update as events warrant. Thank you for your saintly patience in the meantime.

--

UPDATE 3:41 CST

The Breaking News has been updated with a notice regarding the issue. No resolution yet. Soon, Fortunato.

--

UPDATE 3:52 CST

I just wanted to let everyone know that the "characters stuck in limbo" issue does appear to be on our end. We're working as hard as we can--everyone from our in-game staff to our server techs--to make sure you guys get to play.

I need to make clear that at the moment, a Game Master will not be able to move or otherwise "fix" your character to make it unstuck. If you have an open petition, I can guarantee that you will not receive a favorable response for the amount of time you'll have to wait. I'm only looking out for you when I say this.

--

UPDATE 3:58 CST

Realms will be restarted shortly.

YOU'RE THE BEST

AROUUUND

--

UPDATE 4:52 CST

The Nightfall, Stormstrike, and Retaliation Battlegroups appear to be experiencing some lingering issues which I'm investigating. I'll let you know.

You've all done so well exercising patience while we sorted this out, and I ask for just a little bit more during the server-up growing pains and while we put further resolutions in place.

Thank you so much, everyone.

--

UPDATE: 5:19 CST


Retaliation appears to be stabilizing on its own. Please be gentle and don't spam it.

--

UPDATE: 5:58 CST

Stormstrike and Nightfall appear to be stabilizing over time. Be nice and they should let you play.

Thanks for your patience, everyone, and let us know if anything else comes up. If you can't log in immediately, please just wait a few minutes.

--

UPDATE 8:38 PDT

Realm-wide latency and connectivity issues appear to be resolved; however, isolated difficulties are still being addressed by our lovely realm technicians and database administrators. Namely—

    Spell tab errors.

    Kael'thas instability; while resolution is not yet set, we've already begun to investigate the source for this realm's unusual latency at present.

    Ongoing latency spikes for battlegroups Bloodlust, Vengeance, and Shadowburn. While all realms within appear to recover on their own quite quickly, we're still concerned with the consistency that these spikes have occurred. Known issue, looking into it.


--

UPDATE 9:52 PDT

Kael'Thas is back up and running.

--
#46 - March 26, 2008, 7:43 a.m.
Blizzard Post
OP updated. Please post your traceroute in the following thread to aid in diagnosis:

http://forums.worldofwarcraft.com/thread.html?topicId=5540036362&sid=1

Thank you!
#65 - March 26, 2008, 7:46 a.m.
Blizzard Post
Q u o t e:
Belfaire,

Is this thread specifically for the people who cannot connect at all or for those that got a character "stuck" while exiting an instance and can not relog onto that character?

I'm thinking the latter but since I belong to the battlegroup posted I just thought I'd check.

My posts are consolidated to the other can't connect thread for reference.



We're seeing if the two are connected. I'd appreciate it if people experiencing either would go through the steps in the traceroute thread (which, yes, now has instructions, haha).
#98 - March 26, 2008, 7:57 a.m.
Blizzard Post
The armchair server tech help is appreciated, but yes, at the moment this is still our determination after viewing some of these traceroutes.

You may not all be experiencing the same issue.

It makes sense for the two to be connected if they are indeed separate issues, especially since both hit at the same time.

I'll update when I have more info. I understand everyone's upset, but keep it civil in here.
#134 - March 26, 2008, 8:12 p.m.
Blizzard Post
Just want everyone to know I'm still here and aim to be until the resolution of the issue.
#182 - March 26, 2008, 8:23 p.m.
Blizzard Post
For conspiracy theorists, I have no reason to be untruthful with you as to the cause of the issue--when it's been our fault in the past, we've owned up without fail. We believe it's external. If this is not the case, I will let you know.

I am not a server technician. I am in contact with them, though, and I'm passing along information as I get it.

I can either spend time relaying information back and forth to diagnose and resolve the issue or spend time suspending people who can't be civil while a resolution is put in place. Let me do my job.
#238 - March 26, 2008, 8:34 p.m.
Blizzard Post
Q u o t e:
Thanks for the info. Belfaire. Hope you're not stuck here all night trying to figure it out. D:

If so, though, let me know. I'll order coffee. On me.


Hahahaha. Oh, I'll be here for a while, that's for sure. I ain't about to leave on time at a time like this.
#279 - March 26, 2008, 8:40 p.m.
Blizzard Post
Q u o t e:
This is starting to become grounds for a locked thread. 12 pages of "Its not ISP" and posts ending with "idiot" and random traces. We all pay to play, frustration is normal, but the "fix it now or else" is a 100% guarantee of it not being fixed any sooner.

Lock and give us periodic updates imo.


You wouldn't believe how letting people vent helps calm things down sometimes. I'm fine with keeping it open even though a large percentage of the peanut gallery may be incorrect. It's cool. We're fixing it, I know we're fixing it, I'm telling you we're fixing it, and that's what counts.
#303 - March 26, 2008, 8:44 p.m.
Blizzard Post
Q u o t e:


Bored bored :O

So on a side topic, What is your char type in-game? Race, Class. What professions do you have?



I main a rogue, 17/44/0 BS/Mining.

I have two alts I play with regularity: a paladin (ret) with JC/Mining and a shaman (enh) with Herb/Alch.

Beyond that, a bunch of lowbies to try all the classes out. I'm not a big caster fan (to play myself, I mean), just because I prefer the renewable resource of Energy. <3

Q u o t e:
What are the odds that Bliz. will release an extensive statement about this after it's conclusion? admitably(SP?) I'm rather curious.


I'll tell you whatever the combination of PR, good business sense, and common courtesy will allow me.
#320 - March 26, 2008, 8:48 p.m.
Blizzard Post
Q u o t e:


Were you excited about the release of Sunwell? (To play, that is, not deal with the crapola going on here.) Or do you not raid (much)?


Admittedly I don't get to raid as much as I'd like since I came to this shift. I wanted the job, though, so it was definitely a price I was willing to pay. I used to be a hardcore raider!

I'm really excited for the new 5-man, and the dailies (and daily limit increase!) will be great for money.
#369 - March 26, 2008, 8:57 p.m.
Blizzard Post
Hey folks! OP updated with the following info:

We may have an incoming fix that will resolve the stuck-in-limbo issue. I'll update as events warrant. Thank you for your saintly patience in the meantime.
#393 - March 26, 2008, 9 a.m.
Blizzard Post
Q u o t e:


Curious is your rogue on a PVP server? and do you buy into the fact that Vanish is working as intended?


Rogue's on PVE. I don't mind admitting that I'm pretty awful at PVP. That's why I'm specced Combat. ;)

With Vanish, let me put it this way--all abilities in the game are affected by latency. Vanish is one of those unfortunate abilities that's very visually affected by it. I don't have as much of a problem with it as other people seem to, though.

From working in the Game Master department, though, I can say from personal experience that we've resolved a number of issues with Vanish in the past.
#454 - March 26, 2008, 9:08 a.m.
Blizzard Post
Q u o t e:
You know, Belfaire, if there wasn't a character issue and I was able to log into all my characters right now....


I'd be in bed:)

haha


That makes two of us ;)

Q u o t e:
Sarcasm. wonderful. Some people put hours, days and even months of their time into this game.. So maybe they aren't so saintly when things go awry.


It wasn't sarcasm. Most everyone is being pretty great, considering.
#503 - March 26, 2008, 9:20 a.m.
Blizzard Post
Thread extended.

I'm still here and we're still figuring things out. There's a lot to do. I appreciate everyone's civility, and those who can't be civil, I really don't blame you. Just dial it down as best you can.
#604 - March 26, 2008, 9:30 a.m.
Blizzard Post
Q u o t e:


Can't pay people overtime... WTH come on blizzard


These issues arose long after Tech Support went home for the evening.

Q u o t e:

I like how you say "we" as in there's more than one person workin on this issue, if this was true how come I'm having to wait two hours for a GM response in game?

I have not yet seen anyone else addressing the issue besides you, grant it you're probably working your best but are you alone in this? Or is everyone else in bed right now dreaming about how much free money they're making by allowing this to happen over night?


Because tens of thousands of people are petitioning in right now about this very issue even though a Game Master will likely not be able to assist in the issue until things are resolved by our server techs. I mean this literally. This is not an imaginary number.

The reason you don't see others addressing the issue is because I am a public face and the non-public people are doing the real grunt work behind the scenes. All I'm doing is relaying and quelling the masses.
#730 - March 26, 2008, 9:41 a.m.
Blizzard Post
The Breaking News has been updated with a notice regarding the issue. No resolution yet. Soon, Fortunato.
#765 - March 26, 2008, 9:44 a.m.
Blizzard Post
Q u o t e:
The real question is... why couldn't this happen last night when I was supposed to be writing a 7-page essay on managing diversity but instead stayed up to play 10 games of AV? Then of course I wrote the essay while everyone was enjoying the new 2.4 content.


Or on a night I wasn't working! :D
#837 - March 26, 2008, 9:51 a.m.
Blizzard Post
I just wanted to let everyone know that the "characters stuck in limbo" issue does appear to be on our end. We're working as hard as we can--everyone from our in-game staff to our server techs--to make sure you guys get to play.

I need to make clear that at the moment, a Game Master will not be able to move or otherwise "fix" your character to make it unstuck. If you have an open petition, I can guarantee that you will not receive a favorable response for the amount of time you'll have to wait. I'm only looking out for you when I say this.
#902 - March 26, 2008, 9:58 a.m.
Blizzard Post
Realms will be restarted shortly.
#974 - March 26, 2008, 10:04 a.m.
Blizzard Post
It truly shows a negative attitude when people insert invisible subliminal "not"s into your quotes :(
#1005 - March 26, 2008, 10:07 a.m.
Blizzard Post
Heaven help me, thread extended
#1072 - March 26, 2008, 10:12 a.m.
Blizzard Post
Q u o t e:
Belfaire, I thought you said realm restarts won't fix the issue.


They sure wouldn't have at the time.
#1090 - March 26, 2008, 10:13 a.m.
Blizzard Post
Q u o t e:



Retcon?



;D

i kid.


lorelol

(sandlol)
#1208 - March 26, 2008, 10:28 a.m.
Blizzard Post
Oh, and as promised:

There was a brief but nonetheless powerful connectivity issue with some ISPs. It appears to have resolved itself in short order.

At roughly the same time this occurred, we began having issues with our Arena, Battleground, and instance servers on some Battlegroups, which kicked people offline. After this point, I'm afraid that I don't have any more technical information available; needless to say, though, issues occurred with characters logging in.

I'd love to give you all the gritty details, but I'm either not privy to them or can't (or a combination of the two).

Things should be back to normal soon.
#1254 - March 26, 2008, 10:34 a.m.
Blizzard Post
Q u o t e:


If it was a mod issue, I would not have been able to happily play all evening UNTIL the server crashed and kicked half the guild off, and we've been unable to get back on since.

If it was a mod issue, I would not be able to log in and play my characters on Kirin Tor with no difficulty, while I still cannot get on my Icecrown characters.


No, it is not a mod issue. Please stop putting up that straw man. The game is seriously borked.


To be fair, a lot of people experience these kinds of latency/disconnection issues because of faulty or outdated mods with new patches. The symptoms were almost identical and we hadn't had a noticeable issue with server status on our end until a little later, so it was natural to assume that that's what was going on.

I don't frivolously offer solutions, because it doesn't benefit anyone. Thankfully over time we were able to fully diagnose the issue and the resolution is incoming and ongoing.
#1280 - March 26, 2008, 10:42 a.m.
Blizzard Post
Q u o t e:
Isn't it a little unfair for you to blame ppls mods? I was Dc'd yet all took all of my mods out as i always do when a patch comes in! Maybe Bilzz needs to take responsibility for their lack of responce time. anyone remined of New Orelands? Blame everyone but the ppl who were directly involved!


For one, that's horribly offensive and you know it. I can't even believe you'd make the comparison.

I know you can't have the perspective that working here provides, but when 80% of all incoming issues can be resolved with a reset of the player's UI, and when the symptoms match an issue that doing as much can resolve, you recommend they reset their UI.

You needn't be melodramatic about it. We're trying to help you. If you don't want it, that's cool, but don't expect a smooth troubleshooting experience if that's the case.
#1318 - March 26, 2008, 10:49 a.m.
Blizzard Post
I'll find out what's up, those who can't get in. Thanks for the update.
#1326 - March 26, 2008, 10:51 a.m.
Blizzard Post
Also: You've all done so well exercising patience while we sorted this out, and I ask for just a little bit more during the server-up growing pains and while we put further resolutions in place.

Thank you so much, everyone.
#1348 - March 26, 2008, 10:56 a.m.
Blizzard Post
I'm on it, Nightfall people. Don't worry.
#1352 - March 26, 2008, 10:57 a.m.
Blizzard Post
Q u o t e:
ISP ISSUE?

I have absolutely playing on Blackhand, Frsotmourne, Carine, etc servers

Oh my ISP is terribad, i am so sure, my level 1 toon on Blackhand is running so smooth with my terribad ISP can even solo Illidan.

Yet my 70 toon in full epic couldnt even make a bandage before I get disconnected again and again and again and again and again.......


You're a little late, Ape. ;)
#1363 - March 26, 2008, 10:59 a.m.
Blizzard Post
I'd like to ask everyone to give it about ten minutes. Log out if you're trying to log in, grab a glass of water, groove to the sweet sounds of Mr. Hendrix. Then try to log back in and lemme know how things look.
#1386 - March 26, 2008, 11:02 a.m.
Blizzard Post
Edited OP to add Stormstrike to the affected Battlegroups.

*fist pound*
#1397 - March 26, 2008, 11:04 a.m.
Blizzard Post
Steamwheedle Cartel's on Stormstrike. It's in the OP. It's cool, guys. ;)
#1442 - March 26, 2008, 11:15 a.m.
Blizzard Post
Just wanted to update that Retaliation is also among the affected Battlegroups.

Hang in there, kiddos.
#1461 - March 26, 2008, 11:19 a.m.
Blizzard Post
Guys, I'm going to be incognito for a while, but I'll update you with progress as soon as I get back.

Retaliation appears to be stabilizing on its own. Please be gentle and don't spam it.
#1536 - March 26, 2008, 11:43 a.m.
Blizzard Post
Hey guys. Just awaiting an update on Stormstrike and Nightfall.

Can some of you inhabitants of those Battlegroups log in and tell me if things be wack?
#1581 - March 26, 2008, 11:57 a.m.
Blizzard Post
Stuff appears to be stabilizing. I've asked the techs to keep an eye on it just in case, but for now, just ease into the game and be nice to it. It's had a rough night.
#1595 - March 26, 2008, 12:39 p.m.
Blizzard Post
Q u o t e:
You do your job very well!


I do my job. It's a switch, not a dial. ;)
#1599 - March 26, 2008, 2:23 p.m.
Blizzard Post
Hey folks! Checking in.

The connectivity and character stuck concerns expressed previously appear to have resolved with the restarts issued near 2:00am PDT. Again, thank you so much for remaining patient through what can legitimately be labeled "an ordeal." :)

Eldre'Thalas and Shadow Council are now up and running after witnessing multiple absent continents.

That said, we're still investigating errors experienced by players upon attempting to review one's Spell tab.

With this, it appears Kael'thas is experiencing stability issues at present. We've already touched base with our realm technicians and they're looking into the matter currently.


Good morning!
#1601 - March 26, 2008, 2:44 p.m.
Blizzard Post
We're taking a look at ongoing latency spikes occurring for battlegroups Bloodlust, Vengeance, and Shadowburn at this time. While all realms within appear to recover on their own quite quickly, we're still concerned how consistent these increases in mail and loot latency appear to be. :)
#1603 - March 26, 2008, 3:03 p.m.
Blizzard Post
Haha, Belfaire went home, my good man. To recharge and reb—err, to sleep and be merry, I mean.

Sleep and be merry. Like all non-cybernetic creatures do. >.>
#1607 - March 26, 2008, 3:11 p.m.
Blizzard Post
Negative. No ETA as of yet, but should one appear I'll be happy to provide. :)
#1615 - March 26, 2008, 3:25 p.m.
Blizzard Post
Can you define "still"? How long has it been stuck and where?
#1617 - March 26, 2008, 3:51 p.m.
Blizzard Post
Kael'thas is back up and running smoothly.

Kîng - I'm seeing what I can do to alleviate your sticky situation, as it should have resolved itself. Give me a bit of time. :)
#1620 - March 26, 2008, 4:09 p.m.
Blizzard Post
GOODNESS GRACIOUS, WHY ALL THE YELLING?! I CAN'T HEAR TIESTO OVER ALL THE NOISE.

Which makes me a very sad panda. Or Sprite Darter, as it were.

Again, specific battlegroups (Bloodlust, Vengeance, Rampage, and Shadowburn) are experiencing what appears to be cyclical latency spikes. These spikes are creating many disturbances—mail and loot lag, included, as well stuck characters. This still being looked into along side the Spell tab error; the two appear connected in source.

Now, in a calm voice, can you provide me the name and realm of your stuck character? Is it Azrian on Destromath? :)
#1622 - March 26, 2008, 4:14 p.m.
Blizzard Post
What're you experiencing or seeing, Arcano? Without details, I'm afraid I've nothing to reference. :)
#1628 - March 26, 2008, 4:36 p.m.
Blizzard Post
Dagaz—as I noted previously, we're seeing trends in increased latency wax and wane. It appears that as soon as realms start to encounter difficulties, they'll work to correct the issue themselves. The result is that players will become stuck and, shortly thereafter, escape from whatever confines. Regardless, the matter seems to be repeating.

If you witness any sort of similar issue, please let me know ASAP, alright? Truly much appreciated.
#1629 - March 26, 2008, 4:38 p.m.
Blizzard Post
Darangren, Arcano—based on reports, this appears to be affecting only those battlegroups I've listed (Rampage, Bloodlust, Vengeance, and Shadowburn). That said, we're still awaiting word from our Database Administrators, so this may be more widespread than I've noted.

Please keep me up to date and I'll be happy to pass on the information.
#1633 - March 26, 2008, 5:16 p.m.
Blizzard Post
You're getting stuck at "Connecting"? Have you tried resetting your router or modem and then giving it another shot, Drakilu?
#1637 - March 26, 2008, 5:59 p.m.
Blizzard Post
Are you able to access other characters, Nonek, on the same realm?
#1639 - March 26, 2008, 6:04 p.m.
Blizzard Post
In the meantime, I'd recommend submitting an in-game petition from one of your alts regarding the fact that your druid is stuck—be sure to note that you get caught at the loading bar, too, as this is an important piece of information. This will get you back to playing your main while we work out issues from the inside-out. :)