AWS EC2/RDS Outage in us-east-1
31–40 of 152 posts
Re: AWS EC2/RDS Outage in us-east-1
#32Re: AWS EC2/RDS Outage in us-east-1
#33Re: AWS EC2/RDS Outage in us-east-1
#34us-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
#35Well, this outage says something about the companies that religiously depend on it. If 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
#36https://status.heroku.com/incidents/1892 - it appears Heroku is being particularly affected. We've had multiple sites on multiple accounts go down in the past few minutes. EDIT T16:31Z: It appears Heroku has failed over their dashboard, but dynos are still failing to come online. We had assumed that they had multi-region failovers for their customers. Incredibly disappointing.
Re: AWS EC2/RDS Outage in us-east-1
#37Re: AWS EC2/RDS Outage in us-east-1
#38Re: AWS EC2/RDS Outage in us-east-1
#39The Spinnaker project is looking more appealing with every outage. Outage detected in X provider in Y region? Deploy infrastructure to Z provider in Y region.
> Deploy across multiple cloud providers including AWS EC2, Kubernetes
Kubernetes... where?
Re: AWS EC2/RDS Outage in us-east-1
#40I've noticed both Twitter and Reddit were having issues this morning, so this makes sense.