UPDATE: Site appears to be responding now, but there is a maintenance message. AWS dashboard also shows the following updates:
AWS Management Console: 12:14 PM PDT We are currently experiencing
elevated error rates for the AWS Management Console
Amazon Elastic Compute Cloud (N. Virginia): 12:11 PM PDT We are
investigating increased API error rates and latencies for tagging
related API calls in the US-EAST-1 region.
It's not. We're having issues with one of our EC2 instances and this is clearly effecting other sites. It's very unnerving that their service health dashboard isn't reporting any issues.
EDIT: It just now reported an issue on EC2 N. Virginia. Still a little disappointed that it's not real-time.
It could be either certain services limited to Virginia, or certain sites within the region -- my instance is hosted in Virginia, and while very basic, has remained up throughout.
AWS console is also down. We can't login and others are reporting the same issue. Our hosted instances and infrastructure however is online and functioning.
I've been struggling to light up new ec2 instances via the API:
<?xml version="1.0" encoding="UTF-8"?>
<Response><Errors><Error><Code>Unavailable</Code><Message>The service is unavailable. Please try again shortly.</Message></Error></Errors><RequestID>d063a1f7-9fa9-41bb-8792-xxxxxxxxxxxxxx</RequestID></Response>
Sheesh. This makes what, the fourth or fifth time this year so far.. and for an extended period of time to boot. I wonder if this is linked to how they do their deployments, or something else (Everyone has access to deploy to the live site last I heard).
Every developer does have the ability to deploy to production and roughly 0.001% of deployments cause an outage, but this is a company where the mean time between deployments on an average weekday is 11.6 seconds. Source: http://www.youtube.com/watch?v=dxk8b9rSKOo
I deserve to see something visually distinct if there is a problem. This is purposefully poor UX.
If I'm visiting the status page for your site, it's probably because I'm a technical user who suspects something is broken. Don't you dare hide what is broken from me.
If one looks at the intra-day chart of AMZN, you could see the market adjust the pricing of the stock relative to the revenue lost every second due to site down.
The interesting thing is that amazon doesn't typically lose orders when the site goes down for a short period, it often just causes people to delay their orders a little.
45 comments
[ 2.8 ms ] story [ 113 ms ] thread[1] http://status.aws.amazon.com/
[2] https://twitter.com/amazon
UPDATE: Site appears to be responding now, but there is a maintenance message. AWS dashboard also shows the following updates:
EDIT: It just now reported an issue on EC2 N. Virginia. Still a little disappointed that it's not real-time.
Edit: back up for me; SMTP gateway is authenticating and emails are sending out again.
<?xml version="1.0" encoding="UTF-8"?> <Response><Errors><Error><Code>Unavailable</Code><Message>The service is unavailable. Please try again shortly.</Message></Error></Errors><RequestID>d063a1f7-9fa9-41bb-8792-xxxxxxxxxxxxxx</RequestID></Response>
Update: AWS Management Console: Elevated error rates as of 2:15 CST
http://status.aws.amazon.com/images/status1.gif
I deserve to see something visually distinct if there is a problem. This is purposefully poor UX.
If I'm visiting the status page for your site, it's probably because I'm a technical user who suspects something is broken. Don't you dare hide what is broken from me.
Proof: http://youtu.be/dxk8b9rSKOo?t=8m13s
https://www.google.com/finance?q=amzn&ei=JWwSUuCkE8Lp0QGC5QE... compare to SPY, the overall market trend.