Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

US-East AWS Connectivity Issues

status.aws.amazon.com

Post reply on HN
Print view View original

31–40 of 51 posts

Re: US-East AWS Connectivity Issues

#31

Post by fjordan »

cperciva wrote: post #29
rbranson wrote: post #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 u…

I'm definitely seeing issues in multiple AZs. It seems to be partly firewall-related, however: I've seen cases where it's hard to get an initial SYN through, but once a TCP connection is established it stays established.

This, in addition to the increase in traffic we detected directly before, smells of DOS. Also, it is Friday the 13th.

Re: US-East AWS Connectivity Issues

#32

Post by aquark »

I'm getting external monitoring failures that are firing on and off, but have no problem reaching the servers or the site.

Interestingly newrelic is reporting the site down at the same time it is reporting a normal level of load on it.

Re: US-East AWS Connectivity Issues

#33

Post by ceph_ »

aroch wrote: post #14
rschmitty wrote: post #13

Does anyone know why in the world they display a green checkmark with a near invisible little 'i' for this?

Because checkmarks make everything look fine...

Non-snarky answer: They want to post that they are investigating an issue, but do not want to comment on the scope of the problem when it is still not fully understood.

Re: US-East AWS Connectivity Issues

#35

Post by rschmitty »

iota wrote: post #24
rschmitty wrote: post #13

Does anyone know why in the world they display a green checkmark with a near invisible little 'i' for this?

There are 4 statuses. Green checkmark (status 0) Green checkmark with "info" badge (status 1) Yellow triangle (status 2) Red "do not enter" rectangle (status 3) I suspect that status 0 indicates that they are investigating a problem with the server, and it switches to status 1 once the problem has been confirmed. This is also a good example of poor icon design...they aren't self-explanatory, and so they should not be…

Thanks!

Re: US-East AWS Connectivity Issues

#36

Post by iota »

cperciva wrote: post #25
iota wrote: post #24

Earlier quoted context omitted.

There are 4 statuses. Green checkmark (status 0) Green checkmark with "info" badge (status 1) Yellow triangle (status 2) Red "do not enter" rectangle (status 3) I suspect that status 0 indicates that they are investigating a problem with the server, and it switches to status 1 once the problem has been confirmed. This is also a good example of poor icon design...they aren't self-explanatory, and so they should not be…

What happened to status 2?

Good catch. Fixed!

Re: US-East AWS Connectivity Issues

#39

Post by astrodust »

trevyn wrote: post #7
NotDaveLane wrote: post #5

It's region us-east-1c for now, at least from where I'm sitting... I have instances in other us-east datacenters that are fine.

Specific availability zones in a region are mapped per-account, so your east-1c might be my east-1a: "To ensure that resources are distributed across the Availability Zones for a region, we independently map Availability Zones to identifiers for each account. For example, your Availability Zone us-east-1a might not be the same location as us-east-1a for another account. Note that there's no way for you to coordinate…

Clever and ridiculous at the same time.
Post reply on HN