Downtime Notice: 8:00 AM - 11:00 AM Eastern (-4 GMT) Thursday, August 20th

[akousmata]

This kind of response is why we typically do not provide rough estimates on uptime during unexpected issues like we've seen today, as they are seen as "moving the goal posts" when inevitably things come up during the build process, mirroring process, staging, backup, QA checks, etc. Typically, I'd use a response along the lines of, "The worlds are currently unavailable. At this time there is no ETA. We'll keep you updated." However, I know that too causes consternation, so I've been trying to be looser in providing information today.

We are making progress, and are quite a bit closer to opening the worlds. We'll let you know when they reopen.

Honestly, I'm astonished and impressed at your transparency after reading these posts. Providing more details than are necessary to people is refreshing. Often, the people who are frustrated usually have this fantasy of "If only they would tell me what's wrong, I could offer a million billion ways to fix their problem, they're obviously so incompetent they need my help". And by providing any details at all, it appears to me that you are at least making a good faith effort to be transparent. Keep it up, and I'll keep checking back. Thanks!

[Lemdog]

This kind of response is why we typically do not provide rough estimates on uptime during unexpected issues like we've seen today, as they are seen as "moving the goal posts" when inevitably things come up during the build process, mirroring process, staging, backup, QA checks, etc. Typically, I'd use a response along the lines of, "The worlds are currently unavailable. At this time there is no ETA. We'll keep you updated." However, I know that too causes consternation, so I've been trying to be looser in providing information today.

We are making progress, and are quite a bit closer to opening the worlds. We'll let you know when they reopen.

We appreciate the teams efforts to get the worlds back up. Keep up the good work, don't feed the trolls

[kylecamera]

nope...having a great time in world.

nm i'm in!! Thanks!!!

[blackdoguk]

The reason for the downtimes seems self-evident: Incompetence!
They hired bottom of the barrel techs and devs, so we have to pay for it with downtime. It's an American company. Do you really expect anything more than extremely poor quality?

[GrrArgh]

Everyone break out your 20-sided dice. We have to start rolling. We have no idea what the DC is, but we do know that it's being reduced as time passes.....as soon as someone rolls a natural 20 and the DCs have dropped enough, the servers WILL come back up.

[Enoach]

This kind of response is why we typically do not provide rough estimates on uptime during unexpected issues like we've seen today, as they are seen as "moving the goal posts" when inevitably things come up during the build process, mirroring process, staging, backup, QA checks, etc. Typically, I'd use a response along the lines of, "The worlds are currently unavailable. At this time there is no ETA. We'll keep you updated." However, I know that too causes consternation, so I've been trying to be looser in providing information today.

We are making progress, and are quite a bit closer to opening the worlds. We'll let you know when they reopen.

As one that has been part of well scripted deployments and even server moves that have had unexpected issues I can sympathize with what is probably happening at the Turbine office at this time working to get the system back up.

While I'm disappointed that I have not been able to log in, I am glad the team made the call to bring the system down while you resolve the issue that appeared.

Here is hoping that we see the "See you in game." comment sooner than later.

[DarigTheLost]

Thank you Cordovan. You are doing just fine. Keep up the good work.

Cordovan, I agree with this guy's quote, concerning quoting you about not wanting to give an estimate to when u hope to have the servers back up. Giving a ballpark figure and having to re adjust, is MUCH better than a non answer. I very much appreciate having an educational guess at when something should be done, and fully understand when something crops up to throw that hope out the window and you have to adjust the time involved. Don't let it faze you about the negative comments about getting the gnome garden just right. I am sure there are a lot of people who don't take the time to type THANK YOU VERY MUCH FOR KEEPING US INFORMED.

[Lemdog]

The reason for the downtimes seems self-evident: Incompetence!
They hired bottom of the barrel techs and devs, so we have to pay for it with downtime. It's an American company. Do you really expect anything more than extremely poor quality?

Well, for "Bottom of the barrel" techs, they are doing a great job. Please keep your biased drivel out of this thread. Thank you

[Kompera_Oberon]

This kind of response is why we typically do not provide rough estimates on uptime during unexpected issues like we've seen today, as they are seen as "moving the goal posts" [...]

That's a really sweet circular argument: "We fail at providing accurate time estimates, and so providing a time estimate is something we shouldn't even try to get right."

No! When you fail at something which is important, such as communicating information accurately to your customers, you should strive to get it right, and not just punt and accept the failure as a matter of course.

And please note that my response was not only about providing accurate time estimates. I do recall times when your (and by 'your' I mean Turbine's, regardless of who was the messenger) time estimates were accurate. It was also about providing updates which did not introduce unintended issues. By your 'logic' above concerning providing time estimates, since Turbine fails in most cases to deliver new content or patches without unintended consequences being included, they should simply stop providing those updates or patches. See how that works?

[MarauderX]

As a data center guy, I can understand some downtime, but usually they factor in twice the amount of time needed just in case the commissioning went wrong. 3 hours should be plenty. I hope everyone gets some great gifts and us VIPs get some bonus compensation.

[LrdSlvrhnd]

when i asked about doing each world (server) separately i meant closing them and fixing them separately. pick one world to start on then once restarted if all good continue with the next world n so on n so on. that way only the poor folks on that world would b unable to work on their mains but still have alts to obsess on now. next fix, patch, update or what not do different world first and if all good move on to the next. can be done since g-land was such a mess for weeks and worked on individually...

The difference there is that Ghallandra had a specific issue that affecting it specifically. Whereas the current issue is a global one. They're not fixing it server by server and then turning them all on at once. They're fixing it globally, everything at once, and then turning it on. Trying to do it server by server would only slow things down, because it would take just as long to fix... and then, what, 8 times longer? to deploy. They aren't just sitting there going "OK, Cannith is ready, Thelanis is ready, Argo is ready, Wayfinder is ready... but let's keep them offline until the others are ready, too!" It's all or nothing.

Also: To all Turbine employees: Thank you for all your hard work today! I know it's been a long day, and I just hope you're getting overtime and you guys aren't salaried!

[stinkyfish]

This kind of response is why we typically do not provide rough estimates on uptime during unexpected issues like we've seen today, as they are seen as "moving the goal posts" when inevitably things come up during the build process, mirroring process, staging, backup, QA checks, etc. Typically, I'd use a response along the lines of, "The worlds are currently unavailable. At this time there is no ETA. We'll keep you updated." However, I know that too causes consternation, so I've been trying to be looser in providing information today.

We are making progress, and are quite a bit closer to opening the worlds. We'll let you know when they reopen.

It's been a long frustrating day i'm sure, don't let the bad apples spoil the bunch.
We appreciate the looser updates, and every ones hard work to reopen the servers.

Cheers

[slarden]

The reason for the downtimes seems self-evident: Incompetence!
They hired bottom of the barrel techs and devs, so we have to pay for it with downtime. It's an American company. Do you really expect anything more than extremely poor quality?

y u b hatin

[Lukien2]

It is what it is and no amount of weeping, wailing and gnashing of teeth will make it better any faster. Patience is a virtue and as silence is golden I'll shut up now.

[Qaliya]

As a data center guy, I can understand some downtime, but usually they factor in twice the amount of time needed just in case the commissioning went wrong. 3 hours should be plenty. I hope everyone gets some great gifts and us VIPs get some bonus compensation.

My worst was 100 hours spent in the office over 6 consecutive days. Anyone who has experienced something similar knows how this goes.

[Platinum_Carter]

y u b hatin

well sed

[RTG]

This kind of response is why we typically do not provide rough estimates on uptime during unexpected issues like we've seen today, as they are seen as "moving the goal posts" when inevitably things come up during the build process, mirroring process, staging, backup, QA checks, etc. Typically, I'd use a response along the lines of, "The worlds are currently unavailable. At this time there is no ETA. We'll keep you updated." However, I know that too causes consternation, so I've been trying to be looser in providing information today.

We are making progress, and are quite a bit closer to opening the worlds. We'll let you know when they reopen.

I know this don't need to be said but I will anyway ...these few select people giving you grief don't speak for the masses /// love our DDO and the job you guys are doing ..TY

[Drathmar]

Everyone break out your 20-sided dice. We have to start rolling. We have no idea what the DC is, but we do know that it's being reduced as time passes.....as soon as someone rolls a natural 20 and the DCs have dropped enough, the servers WILL come back up.

Didn't they kill DC casting with Update 27?Your plan seems fruitless.Server saves are probably in the high 90s.What we need are dual Pick wielding Barbarians!Bash the servers until they succumb to your DPS!

[FifthTime]

I feel badly for those people at Turbine who are stuck working late to fix the mistakes of others. However, I don't feel sorry for whoever is responsible for not only writing the faulty code that resulted in the loss of tomes and hence the extended down time but then not testing it thoroughly enough to detect such an obvious bug.

That's just bad work. That guy should be on the hook for beers for everyone else.

I know I wouldn't be very impressed if I had to stay at work late to fix someone's mistakes.

[neain2008]

First off, thanks for the updates. Second, thanks for the great work on a game I have grown to love. It may not be perfect, but the best things never are.