FYI there's a great Chrome extension that hides all the working services (green checks) on the AWS status page so you can quickly see what's down.

https://chrome.google.com/webstore/detail/real-aws-status/ka...

Sorry guys, I knew I shouldn't have started my 4 instances at once.

Status page is down too: https://status.aws.amazon.com/

Shouldn't there be a separation of concerns for status pages, maybe use: https://www.statuspage.io/

Edit: http(s) was at fault (no SSL cert?)

Brace for half the internet going down if gets any worse, especially if its us-east (wish I was being ironic).

Dammit now my Amazon Echo doesn't work.

API Gateway is returning 500s. So much for server-less architecture :(

Many customer-facing amazon services are also affected, including amazon.com!

Twitter is not pretty:

https://twitter.com/search?f=tweets&vertical=default&q=amazo...

I blame Pokémon Go. Somehow or another I'm sure it's to blame.

I like how half the internet can die when EC2 has problems.

AWS would wish that all those downtime reporting services move to their infrastructure. That ways there won't be anyone to report the downtime.

I can't log into amazon.com to check my orders (first time that happened). THat's quite surprising as often these problems are unrelated

Am I the only one having daily issues with SQS? I have 150+ servers writing to a queue and they timeout at random a few times per day.

AWS should design for resilience [0].

[0] This is a part of the wisdom shared by AWS support upon reporting an outage.

Seems to be effecting everything but I have some running instances that seem fine. https://cloudstatus.eu/status/aws

Edit: Does seem to be recovering now

Amazon.com remains up... unless you attempt to buy something, when you get a 500 error.

11:27 AM PDT We are investigating increased API error rates in the US-EAST-1 Region.

Is anyone having issues with their lambda functions not working? Mine stopped working and is just returning "Service error." when I try to test even though they claim it's operating normally.

Looks like it's just their service API for now, i.e not responding to any queries on existing instances for me at all. However, everything else is working fine as far as I can tell.

We are getting very intermittent issues with S3 and SNS so far.

Can't log in to AWS Console. Instances running fine.

In the console, running instances was timing out on load for EC2 and some of our AWS API calls to get hostnames are timing out in PHP

Ditto, can't see any instance data either via the API or graphical dashboard. Instances themselves seem normal for the moment.

Just got through to the AWS Console. Finally can get back to work.

On this note: what are some good alternatives to AWS?

Dear smarta$$es, could you please tell me the benefits of serverless architecture (lambda) once again? My monolith app works perfectly fine even when the whole AWS is offline :P

everything on getstream.io is still up and running. most issues seem related to provisioning more instances.

does anybody have more details about what's actually down? their description is a bit vague.