Realm Issues - Ruin and Bloodscalp

#0 - April 22, 2008, 2:19 a.m.
Blizzard Post
Hey guys, we'll be consolidating realm issues into this thread, so that I can gather and forward information most efficiently to the appropriate parties.

Thanks for your cooperation guys; please list your realm, and what specifically seems to be occuring. I'll try to get the information to the right people as soon as possible.
#15 - April 22, 2008, 2:34 a.m.
Blizzard Post
Q u o t e:
US Executus Instance servers are down, Stuck in Karazhan at the moment


Can you guys confirm that all instances are down on Executus?
#44 - April 22, 2008, 3:12 a.m.
Blizzard Post
Thanks for the information guys. I've forwarded what you've provided, and the situation is being investigated. Please post any major developments or issues you encounter in this thread so we can keep tabs on things.

Your patience is greatly appreciated!
#82 - April 24, 2008, 2:41 a.m.
Blizzard Post
Just as an update guys, we have people looking into the issues on Bloodscalp as we speak.

Hopefully we'll get things worked out soon, but there isn't an ETA available currently.
#91 - April 24, 2008, 3 a.m.
Blizzard Post
Q u o t e:
Only thing I dont understand, is that this has been brought up before in the last week. We have gone through two "maintenances" on tuesday for the usual seven hour period, and when it comes back up nothing has changed. What is the point of these maintenances if not to fix problems like this? I have even seen other servers get extended maintenance on these regularly scheduled days, yet nothing for Bloodscalp.

This doesnt seem to be a simple "we can just reboot and everything is OK" this is a case of the instance servers being overpopulated and crashing. I think this is evidenced when the servers are fine for the initial few minutes, but start to lag and then crash again when raiding starts back up or as more people log back in.


I know that you guys want solid answers, and I don't blame you.

Unfortunately, as per the usual, I can only really say that it's being investigated, and as with any persistent issue, the situation is much more complex than it appears at face value =(.
#92 - April 24, 2008, 3:08 a.m.
Blizzard Post
As an update, I'm receiving reports that Bloodscalp should be stabilizing for now. We'll continue to monitor the situation, but if you experience further issues, please let us know.

I'm really sorry about the delays guys, and I really appreciate your patience while we've worked on this.
#95 - April 24, 2008, 3:21 a.m.
Blizzard Post
Q u o t e:


Well, the usual isn't quite cutting it, and I know it's your company policy to play nice and treat us all like children that won't understand, but not all your customers are the 12-15 year olds that you seem to want to cater to. Having worked in Customer Service as a supervisor for years, I know that you're not allowed to compromise more. So tell us, what ARE you exactly able to do, other than tell us "Hey guys, your server is down" which we already know and already reported to you.

Give us a straight answer. "Server has a corrupted data file that would take X days to fix". Then maybe we could plan accordingly, and not throw our time, our friends' time, and our guild mates' time away on a game that won't work.


Simple answer?

I don't have that information to give, and if I did, I'd still not be in a position to provide it. When it comes to a situation like this, estimates like 'hours' or 'days' are simply not available. I know that isn't what you want to hear, but that's me playing as straight with you as possible. You wanted the 'adult' answer, and that's it.

That doesn't change the fact that I find this whole situation regrettable, and that I wish I had more solid information to provide to enable that kind of planning. I know that interrupted raids are no-one's idea of a picnic, and I won't pretend otherwise. A lot of Bloodscalp players have expressed concerns about compensation. The only method to seek it effectively is to make a post on the Suggestion forum about it. They won't comment, but if you keep an eye on your Account Management pages, you may see time reimbursed. Obviously, there are no guarantees, and typically compensation is not available - but I wanted to make sure you guys were aware anyway.

What I am able to do is assure you that we know about the situation, and are investigating it. I can provide updates regarding any attempts to resolve the issue. You may not value this much, but personally, I'd prefer to provide what updates I can, than maintain silence, and encourage the perception that the situation is being ignored when I am quite certain that it isn't.
#214 - April 24, 2008, 2:15 p.m.
Blizzard Post
If you have an issue with a particular realm, then please continue to post here.

If you have an issue, however, with a particular player from a particular realm, then please do not.



Curb the loathing or contempt you possess for each other briefly. Or redirect it towards us, if you must, but let's keep the infighting at bay.

Thanks.
#219 - April 24, 2008, 2:41 p.m.
Blizzard Post
We just witnessed marked improvement for battlegroups Bloodlust and Vengeance. And this was after extensive research and troubleshooting for nearly 3 weeks. The length of time required to resolve persistent technical ailments is never ideal, Scærcrøw, but it's a facet of resolution that's generally consistent.

Now, Bloodscalp is reporting differing issues than that of Arthas, Alleria, and Warsong—and at remarkably different times. So, there's two very separate concerns popping up herein and thus, likely, two very separate directions down which our Technicians must head to fully alleviate each and every woe.

While I possess no update (my contacts have not yet come on shift), I'll see what information I can find out.
#221 - April 24, 2008, 2:49 p.m.
Blizzard Post
Q u o t e:
Please, at least acknowledge you are looking into the problem, even if there is no solution on the horizon.


We have. :)

http://forums.worldofwarcraft.com/thread.html?topicId=5974362508&sid=1&pageNo=5#82

Q u o t e:
Just as an update guys, we have people looking into the issues on Bloodscalp as we speak.
#223 - April 24, 2008, 3:03 p.m.
Blizzard Post
Q u o t e:
Why are you telling us about other servers?


Because it provides a perspective which you are sincerely lacking—albeit likely through no fault of your own—at this point in time. It's a testament that ongoing issues cannot be resolved immediately, but that resolution will be pursued until it's achieved.

We cannot just "fix it." It's not a switch. That said, no one here is attempting to dismiss your frustration (a fact for which I do genuinely apologize); we are, however, trying to provide you valuable insight and relevance. Should you choose to reject it, I'm sorry.
#225 - April 24, 2008, 3:40 p.m.
Blizzard Post
Q u o t e:
Are we going to get a refund of some kind since we've lost about 40 hours of play time over the past month due to server crashes?


This is a matter which is truly not under the purview of the Game Master department, Aslinge, so I possess no insight as to what may or may not become of this particular series of events. Suffice to say that such things are reviewed continually and that, should compensation be given the go ahead, word will most likely be made within General—not herein.
#228 - April 24, 2008, 4:34 p.m.
Blizzard Post
Q u o t e:
Edit: If a GM can't issue free game time, please forward our request to the department that could do it for us.


I am not in contact with those who ultimately decide such things, Hawtty. Again, though, matters of this nature are always under constant review; there's truly no need for anything to be relayed. :)
#231 - April 24, 2008, 4:47 p.m.
Blizzard Post
Why?
#235 - April 24, 2008, 4:53 p.m.
Blizzard Post
This thread is a hub for the very same information you're requesting. To spread our points of contact thin by posting within multiple threads would only complicate matters further. It wouldn't serve any reasonable, valuable purpose; it would only create two disparate communication links.

Regardless, General Discussion is not a GM domain. You're welcome to link this thread, though. :)
#245 - April 24, 2008, 5:10 p.m.
Blizzard Post
No, Naha. I cannot make anyone within Community post on behalf of a Game Master. We are truly wholly separate departments, assigned to address wholly separate concerns. Community is privy to the same information we are (and is, in turn, informed at the same pace), but is not ultimately responsible for identical aspects. That said, the nature of the post seems to be requesting a hardware upgrade—given that it's a request and given that such matters are normally not discussed in depth prior to their implementation, I'm unsure if the post, in its present form, is really capable of being responded to. It's sort of the same thing as being asked an oddly phrased question...sometimes, even if you have an answer that's relevant, it's hard to actually address the points you know since there's other topics getting in the way.

Community members are still coming on shift for the day, so perhaps there's still time yet for a head's up or a redirect. It's not something that's a guarantee, however.

Q u o t e:
This thread was intented for realm issues regarding all servers, but it has been taken over by complaints with Blooodscalp, and due to the fact that the 'Blue' said we're no going to get a response on the thread you linked, more people from Bloodscalp are likely going to come here posting.


No. I said I could not make a post therein. Huge, yawning, gaping difference. :)
#248 - April 24, 2008, 5:14 p.m.
Blizzard Post
No prob, Naha. Just don't dot shock me and we'll call it even. ;)
#251 - April 24, 2008, 5:18 p.m.
Blizzard Post
Fair enough. Forewarning, though—I'll be deleting posts which are not informative, civil, or otherwise useful to this thread. This includes replies which contain nothing but "I H8 U BLIZZTARD, "BUMP FOR GREAT JUSTICE," and "OMG FIX IT!"

Yes, I'm going to be fairly brutal, but I'd like for this topic to stay on track. I don't want my ability to communicate with all of you equitably and nicely impaired in any way.
#256 - April 24, 2008, 5:39 p.m.
Blizzard Post
Thanks for the information, guys. It's truly invaluable. When approaching situations such as this, it's important to gather and review both internal and external data. You're providing the latter.

It looks as though the issues are likely focused on a ill-functioning component which is set to be replaced quite soon. I don't have an ETA on when the replacement is scheduled to occur, but it's definitely a priority. This is believed to be the source, but is not wholly confirmed; we're going to cross that bridge first, though, and then go from there.
#261 - April 24, 2008, 6:28 p.m.
Blizzard Post
Q u o t e:
Alot of those irrate people, and I'm not excluding me, would be much happier if -anyone- at blizzard were to post with some details and communication as to what's happening and how they are going about fixing it.


This is what this thread is for; you'll find the information you seek herein. Regardless, the thread in question—its topic is ostensibly requesting a realm upgrade. Its diction and wording are more indicative of a demand or a suggestion rather than an inquiry of its status. This fact alone makes the thread a difficult one to which to respond. I realize this point was likely unrealized, but it's definitely something to consider and may prove useful later on.

May I ask where the thread originated, though?
#263 - April 24, 2008, 6:33 p.m.
Blizzard Post
To provide a solely educated guess (please bear in mind that I am not a technical savant and am not privy to all mitigating details), Dropdeadfred, it's quite likely that we will be unable to resolve this issue by the start of peak raiding hours tonight. Things might go smoothly regardless! But it's probably safe to plan ahead and perhaps reschedule accordingly.
#266 - April 24, 2008, 8:35 p.m.
Blizzard Post
Aw. It ain't so bad, Hawtty. I get to meet a lot of rad people along the way. :)

Q u o t e:
Anyway, do you have any info at all why the servers are crashing? Bad ISP?, Bad weather? Servers need a upgrade?


This (few "Blue" posts back):

    It looks as though the issues are likely focused on a ill-functioning component which is set to be replaced quite soon. I don't have an ETA on when the replacement is scheduled to occur, but it's definitely a priority. This is believed to be the source, but is not wholly confirmed; we're going to cross that bridge first, though, and then go from there.
#272 - April 24, 2008, 9:51 p.m.
Blizzard Post
Q u o t e:
Will this said component be fixed tonight by say, 6:30svt? If not its probably useless for any guild to do any raiding.


Pulling from another previous post.

http://forums.worldofwarcraft.com/thread.html?topicId=5974362508&sid=1&pageNo=14#263

    To provide a solely educated guess (please bear in mind that I am not a technical savant and am not privy to all mitigating details), Dropdeadfred, it's quite likely that we will be unable to resolve this issue by the start of peak raiding hours tonight. Things might go smoothly regardless! But it's probably safe to plan ahead and perhaps reschedule accordingly.
#275 - April 24, 2008, 9:57 p.m.
Blizzard Post
Q u o t e:
Unfortunate, any word of possible compensation for lost and wasted raid/play time?


Again from another previous post. ;)

http://forums.worldofwarcraft.com/thread.html?topicId=5974362508&sid=1&pageNo=12#225

    This is a matter which is truly not under the purview of the Game Master department, Aslinge, so I possess no insight as to what may or may not become of this particular series of events. Suffice to say that such things are reviewed continually and that, should compensation be given the go ahead, word will most likely be made within General—not herein.


No problem with repeating posts or information, but it'd be probably be a good plan to start reading the "Blue" posts starting from page...10? Just use the little "Blizz" symbol to skip ahead. Should be fairly quick. They're all short!
#290 - April 25, 2008, 5:44 p.m.
Blizzard Post
I fear the blue-hued text is a reserved quirk, Nienna. But I can post in white, though, mwahahaha. ;)

That all said, I'm still trying to find out an ETA for you folks. One's presently not available; but, should such surface, I'll be quick to relay it herein.