Well there’s your problem, people. Use multiple AZs.
AWS EC2/RDS Outage in us-east-1
11–20 of 152 posts
Re: AWS EC2/RDS Outage in us-east-1
#12Copy that. Happy Labor Day weekend everyone.
It's been 2 hours and they still don't have a red flag on https://status.aws.amazon.com/
Re: AWS EC2/RDS Outage in us-east-1
#13Re: AWS EC2/RDS Outage in us-east-1
#14Is there any way for the owners of the instances to reach them?
Re: AWS EC2/RDS Outage in us-east-1
#15>We are investigating connectivity issues affecting some instances in a single Availability Zone in the US-EAST-1 Region. Well there’s your problem, people. Use multiple AZs.
Re: AWS EC2/RDS Outage in us-east-1
#16If your entire service just went down as soon as this happened, Congratulations! You didn't deploy in multiple regions or think about a failsafe/fallback option that redirects from your affected service or instance.
Re: AWS EC2/RDS Outage in us-east-1
#17>We are investigating connectivity issues affecting some instances in a single Availability Zone in the US-EAST-1 Region. Well there’s your problem, people. Use multiple AZs.
Re: AWS EC2/RDS Outage in us-east-1
#18us-east-1 continues to have continually worse uptime than other regions (for, likely, good reason too, it continues to be the default region). I've avoided that region and I can't remember the last time I had downtime caused by Amazon.
Re: AWS EC2/RDS Outage in us-east-1
#19It looks like it was localized to zone D.