Amazon was down(amazon.com)
amazon.com
Amazon was down
http://amazon.com
Amazon is down 11:49 AM west coast
45 comments
AWS seems to be okay via this status dashboard. Nothing on the Amazon twitter feed either [2].
[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:
[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:
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.
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.
Nothing on the @awscloud twitter either. Really sad support. https://twitter.com/awscloud
[deleted]
AWS Console icon is now red (i.e. Service disruption)
Funny how there is a widely reported problem and everything is green on AWS health check site http://status.aws.amazon.com/
Given that none of my running AWS services experienced any downtime, that seems entirely reasonable.
Is Amazon e-com website is dependent on AWS ? I don't think so. Pointers please.
Yes, it runs on EC2.
Proof: http://youtu.be/dxk8b9rSKOo?t=8m13s
Proof: http://youtu.be/dxk8b9rSKOo?t=8m13s
Just reported: Amazon Elastic Compute Cloud (N. Virginia) Increased API Error Rates
Update: AWS Management Console: Elevated error rates as of 2:15 CST
Update: AWS Management Console: Elevated error rates as of 2:15 CST
I hate how they weasel out and display a green checkbox, but with a tiny little "i" for information on Amazon Elastic Compute Cloud (N. Virginia).
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.
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.
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'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>
<?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>
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.
https://www.google.com/finance?q=amzn&ei=JWwSUuCkE8Lp0QGC5QE; compare to SPY, the overall market trend.
https://www.google.com/finance?q=amzn&ei=JWwSUuCkE8Lp0QGC5QE; compare to SPY, the overall market trend.
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.
Appears to all be back online.
- amazon.com = back
- aws console = can login and work
- SES = queue's have cleared
Their indian sites http://junglee.com and https://www.amazon.in/ looks perfectly fine.
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.
Everything back to normal now, so far as I can tell.
Amazon.com is still down for me, but http://www.amazon.de is running fine.
My EC2 instances are still running fortunately.
Well, AWS console being down is certainly more of an impact to me than amazon.com.
The console is working if you are already logged in. Although loggin requires going through www.amazon.com.
It's back: 3:33 EST.
Now the server is returning a 500, which is a slight bit of progress.
EC2 is ok for me SES has gone to the shitter
Amazon and AWS Console are back online :)
Amazon site seems to be up now.
Amazon.com is back up for me.
[deleted]