Live data from Hacker News

US-East AWS Connectivity Issues

status.aws.amazon.com

11–20 of 51 posts

Re: US-East AWS Connectivity Issues

#12
post #8

We (ScraperWiki) can still access some of our US East servers. From those, can daisy chain SSH into the ones that are offline. Those servers can't see the world, but are working fine and can see other EC2 instances.

Hi, can you use port forwarding to get website up on those affected nodes?

Re: US-East AWS Connectivity Issues

#15
post #3

Amazon is continuing the trend of announcing outages 30 minutes after they start. Just signed up for a support contract since the status page said everything was fine.

And by "announcing" you mean indicating everything is a-okay with the green checkmark but putting a tiny footnote next to it.

Re: US-East AWS Connectivity Issues

#16
ELBs are also having problems. One of mine is reporting all instances out of service (transient error), then all instances in service, intermittently. But the ELB is never reachable (even when it reports all instances healthy and up). All instances behind this one are reachable, up and running. US-East-1.

Some of our other instances are reachable but some are not, same as others have been reporting.

Re: US-East AWS Connectivity Issues

#19
This appears to be connectivity issues entirely to/from the Internet or other EC2 regions from a single availability zone in us-east-1. The intra-AZ networks within us-east-1 have remained available during the event. One of the AZs we use was affected, but no external traffic flows to it. I noticed this because an auto-scale group was trying to bring up instances inside of the affected zone (our us-east-1a) and was unable to contact a server outside of AWS.
Post reply on HN