Discussion Forums
Discussion Forums > Category: Amazon Web Services > Forum: Amazon Elastic Compute Cloud >Thread: What's with changing back to "Performance Issues" again?
Advanced search options
What's with changing back to "Performance Issues" again?
Posted by: trogdoro
Posted on: Apr 23, 2011 7:26 PM
  Click to reply to this thread Reply
This question is not answered. Helpful answers available: 2. Correct answers available: 1.
What's with changing the ec2 status back to "Performance Issues" again? My instance is still dead in the water. >: [

i-1bbccd77

How is everyone else doing?
Permlink Replies: 12 | Pages: 1 - Last Post: Apr 24, 2011 12:34 PM by: fairstream
Replies
Re: What's with changing back to "Performance Issues" again?
Posted by: user528491
Posted on: Apr 23, 2011 7:27 PM
in response to: trogdoro in response to: trogdoro
  Click to reply to this thread Reply
I think three consecutive disruption badges on the status history would look bad for AWS reputation so they changed it to a lesser yellow yield sign instead.
Re: What's with changing back to "Performance Issues" again?
Posted by: mavericks39
Posted on: Apr 23, 2011 7:43 PM
in response to: trogdoro in response to: trogdoro
  Click to reply to this thread Reply
I have one that didn't recover yet... i-73f7681a
Re: What's with changing back to "Performance Issues" again?
Posted by: BrentJ@AWS
Posted on: Apr 23, 2011 8:24 PM
in response to: trogdoro in response to: trogdoro
  Click to reply to this thread Reply
Before I continue, let me first apologize for this standard message. The create volume API is now enabled. At this time all APIs are back up and working normally. We will be monitoring the service very closely, but at this time all EC2 and EBS APIs are operating normally in all Availability Zones so we have reduced our status to yellow.

We do have volumes that have not been recovered and we're are working cautiously to manually recover these volumes. Please note that if your volume has not yet been recovered, you will still not be able to write to your volume or successfully perform API calls on your volume until we have recovered it.

We will continue to update our status page and continue to provide updates as soon as we possibly can. http://status.aws.amazon.com

Regards,

Brent J

Re: What's with changing back to "Performance Issues" again?
Posted by: yujb
Posted on: Apr 23, 2011 8:40 PM
in response to: BrentJ@AWS in response to: BrentJ@AWS
  Click to reply to this thread Reply
"Before I continue, let me first apologize for this standard message."... then you proceed with the cut-and-past.. LOL...DOMO ARIGATO MR ROBOTO
Re: What's with changing back to "Performance Issues" again?
Posted by: tinytrader
Posted on: Apr 23, 2011 9:23 PM
in response to: BrentJ@AWS in response to: BrentJ@AWS
  Click to reply to this thread Reply
But things are not normal. We still can't get back to normal on that availability zone because we can't start micro instances and we can't change downed instances and EBS volumes to other instance types through the EC2 Console.

Edited by: tinytrader on Apr 23, 2011 9:23 PM
Re: What's with changing back to "Performance Issues" again?
Posted by: fairstream
Posted on: Apr 23, 2011 9:44 PM
in response to: trogdoro in response to: trogdoro
  Click to reply to this thread Reply
AWS! How insulting! This is not a simply "Performance Issue", this is a full blown Service disruption!

Your status update cleverly says "many" volumes are recovered... how many? 30 from a total of 1000000? Why not be honest with some real numbers here? Because I bet you there are "many" (more) ec2 instances still frozen!

You're APIs might be "working" but the "affected volumes" for EC2 machines are NOT WORKING - and the APIs for these machines are DEAD as can be!

For most of us are concerned, your services aren't simply disrupted... but DEAD! There is NO service! NONE!!! Our EC2 machines are DEAD!

Edited by: fairstream on Apr 23, 2011 9:45 PM
Re: What's with changing back to "Performance Issues" again?
Posted by: Stephen Foley RealName(TM)
Posted on: Apr 23, 2011 10:45 PM
in response to: trogdoro in response to: trogdoro
  Click to reply to this thread Reply
I also struggle with moving the status of this outage from "Service Disruption" to "Performance Issues".

This is their latest status:

9:58 PM PDT Progress on recovering the remaining stuck volumes is proceeding slower than we anticipated. We are currently looking for ways in which we can speed up the process, and will keep you updated.

I have one of these stuck volumes. It has been stuck for a number of days now. I am experiencing a disruption to service as are my clients. It is not a performance issue, there in no performance issue as there is no service to perform in. It has been and continues to be a Service Disruption.

If this is Amazon's way of trying to help them look better in the world, it is not working it just continues to erode my trust in what I am being told.
Re: What's with changing back to "Performance Issues" again?
Posted by: stivlo
Posted on: Apr 23, 2011 10:58 PM
in response to: Stephen Foley in response to: Stephen Foley
  Click to reply to this thread Reply
I actually agree with Amazon, it's a performance issue: in fact my instance is stuck stopping since 10 hours, it's just a little slow, see? Just a little slow..

sorry for this, I couldn't resist
Re: What's with changing back to "Performance Issues" again?
Posted by: sparklab
Posted on: Apr 23, 2011 11:40 PM
in response to: stivlo in response to: stivlo
  Click to reply to this thread Reply
"It's not dead, it's resting."
Re: What's with changing back to "Performance Issues" again?
Posted by: Stephane Legay RealName(TM)
Posted on: Apr 23, 2011 11:55 PM
in response to: trogdoro in response to: trogdoro
  Click to reply to this thread Reply
I can understand outages. Even severe outages. Even catastrophic, 72 hour datacenter-wide failure. Amazon has been a pioneer in the cloud and has offered an outstanding service to countless startups. It's a learning curve. Mistakes will be made. I'm OK with that.

The lack of transparency, however, is unforgivable. Had we know the depth of the issue early on, we'd have bitten the bullet 3 days ago and rebuilt our servers rather than wait for dead instances to come back alive.

Customers are entitled to know exactly, hour by hour, what the problems are, what Amazon's doing to fix them, recovery rate, and a best guess of expected service disruption duration. Instead we're getting daily cryptic statements with zero technical value.

I'm very disappointed.
Re: What's with changing back to "Performance Issues" again?
Posted by: Casetta Flavio RealName(TM)
Posted on: Apr 24, 2011 2:59 AM
in response to: sparklab in response to: sparklab
  Click to reply to this thread Reply
"beautiful plumage, inn it? Norwegian blue!"
Re: What's with changing back to "Performance Issues" again?
Posted by: fairstream
Posted on: Apr 24, 2011 12:34 PM
in response to: Stephane Legay in response to: Stephane Legay
  Click to reply to this thread Reply
Stephane... We totally agree. Lack of transparency is absolutely appalling... and the cryptic statements are absolutely meaningless. AWS makes a novice weather forecasters look like a king...

What's disgusting is that Amazon is actively withholding information (most likely because of the legal department). They've already lost public trust on their ability to maintain their SLA. Now they are losing trust on the way they handle trouble - which is much more troubling than their SLA...

Speaking of SLA.... If Amazon's SLA was actually 99.95% (without the pages of exlcusions), in the last 3 days, the amount of downtime we have experienced would be our maximum allowed downtime for over 20 years!