Did anyone else notice a huge spike in incoming network traffic on their EC2 instance immediately before the outage? Roughly 9:55AM EST.
Yes
US-East AWS Connectivity Issues
21–30 of 51 posts
Re: US-East AWS Connectivity Issues
#22This 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…
Not sure if it's the entire AZ. We have some Internet-reachable instances and Internet unreachable instances in the same AZ.
Re: US-East AWS Connectivity Issues
#23Why does this never happen to AWS West? I should really get to migrating over with 3 outages in the past 2 years on US East.
Re: US-East AWS Connectivity Issues
#24Does 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 used.
Re: US-East AWS Connectivity Issues
#25Does 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…
What happened to status 2?
Re: US-East AWS Connectivity Issues
#26This 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…
We are able to reach some servers but not all in our us-east AZ and notice it seems to be random.
Re: US-East AWS Connectivity Issues
#27Does 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...
Re: US-East AWS Connectivity Issues
#28All of mine just started magically working
Re: US-East AWS Connectivity Issues
#29This 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.
Re: US-East AWS Connectivity Issues
#30this has taken openredis offline: https://twitter.com/openredis
heroku is also reporting issues: