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

AWS EC2/RDS Outage in us-east-1

status.aws.amazon.com

Post reply on HN
Print view View original

101–110 of 152 posts

Re: AWS EC2/RDS Outage in us-east-1

#101

Post by bcrosby95 »

freehunter wrote: post #90
manojlds wrote: post #75

Earlier quoted context omitted.

Being on AWS is also easy to explain to customers about downtimes - AWS was down and customers are pretty understanding in that case and don't demand why you aren't multi AZ etc ( of course YMMV based on sensitivity of your business)

Kind of like the "no one ever got fired for recommending IBM", if you have significant downtime on Linode or Hetzner, people are going to ask "why weren't you on AWS?!". If you're on AWS and AWS goes down, you get to skip that question entirely. You were already using the logical choice, you don't need to defend anything. If Netflix can go down when AWS goes down, so can your app. AWS outages impact so much of the In…

Netflix is multi region and even when a full region went down they were still fine.

So your statement relies on customer ignorance.

Re: AWS EC2/RDS Outage in us-east-1

#102

Post by jbourne »

bdcravens wrote: post #68
Matthias247 wrote: post #51

Earlier quoted context omitted.

This is not true. The region where new software is deployed first is different team by team (or service by service).

Perhaps, but I can't recall a product launch that wasn't available in us-east-1 from day 1.

I believe us-east-1 is one of the regions included in the minimal set of regions for a new AWS service to be considered 'available'. If I recall, eu-west-1 is another such region.

Re: AWS EC2/RDS Outage in us-east-1

#103

Post by SPascareli13 »

hhw wrote: post #98
bob1029 wrote: post #71

Earlier quoted context omitted.

For us this is exactly the correct approach. We could have spent millions of dollars and thousands of man hours hardening things to be resilient to single region outages. But for what? We aren't GE or Google. If our conference line goes down for 2-3 hours per year because we don't have apocalypse-proof infrastructure, literally nothing bad happens to our business. In this exact outage we are discussing, all of my cow…

2-3 hours per year is a lot of downtime. Most competent bare metal providers see maybe one major outage of less than an hour every 3-5 years. Nothing other than a facility wide power outage, if the load somehow gets dropped because the generators don't start right away as they should, or a misbehaving (only partially failing) core network infrastructure device should result in major outages when all the proper redund…

I don't want to advertise your particular company, but if we are talking about numbers, how does your bare metal offer compares to a Amazon ec2 offer for example? And how would a customer that need to scale their load do it?

Re: AWS EC2/RDS Outage in us-east-1

#104

Post by dijit »

hhw wrote: post #98
bob1029 wrote: post #71

Earlier quoted context omitted.

For us this is exactly the correct approach. We could have spent millions of dollars and thousands of man hours hardening things to be resilient to single region outages. But for what? We aren't GE or Google. If our conference line goes down for 2-3 hours per year because we don't have apocalypse-proof infrastructure, literally nothing bad happens to our business. In this exact outage we are discussing, all of my cow…

2-3 hours per year is a lot of downtime. Most competent bare metal providers see maybe one major outage of less than an hour every 3-5 years. Nothing other than a facility wide power outage, if the load somehow gets dropped because the generators don't start right away as they should, or a misbehaving (only partially failing) core network infrastructure device should result in major outages when all the proper redund…

Don’t mind me. I’m just here to corroborate your claims of downtime as a consumer of bare-metal hosting providers for 15-something years.

Re: AWS EC2/RDS Outage in us-east-1

#105

Post by Johnny555 »

bob1029 wrote: post #71
matt2000 wrote: post #61

Just wanted to add a quick note before we get the usual deluge of "you should be running in multiple AZs and regions" posts: These outages are relatively rare and your best decision might just be to accept the tiny amount of downtime and keep your app simple and inexpensive to run. I of course don't know the tradeoffs involved in running your system, but I know for a lot of my situations the simplicity of single AZ w…

For us this is exactly the correct approach. We could have spent millions of dollars and thousands of man hours hardening things to be resilient to single region outages. But for what? We aren't GE or Google. If our conference line goes down for 2-3 hours per year because we don't have apocalypse-proof infrastructure, literally nothing bad happens to our business. In this exact outage we are discussing, all of my cow…

If your business is so complicated and mature that it takes millions of dollars to build multi-region tolerance, you probably need that tolerance.

For more simpler sites, having multi-region failover (even if it's a manual failover and you lose a few in-flight transactions) is much easier to build.

Re: AWS EC2/RDS Outage in us-east-1

#106

Post by [deleted] »

matt2000 wrote: post #61

Just wanted to add a quick note before we get the usual deluge of "you should be running in multiple AZs and regions" posts: These outages are relatively rare and your best decision might just be to accept the tiny amount of downtime and keep your app simple and inexpensive to run. I of course don't know the tradeoffs involved in running your system, but I know for a lot of my situations the simplicity of single AZ w…

[deleted]

Re: AWS EC2/RDS Outage in us-east-1

#108

Post by tilolebo »

hhw wrote: post #98
bob1029 wrote: post #71

Earlier quoted context omitted.

For us this is exactly the correct approach. We could have spent millions of dollars and thousands of man hours hardening things to be resilient to single region outages. But for what? We aren't GE or Google. If our conference line goes down for 2-3 hours per year because we don't have apocalypse-proof infrastructure, literally nothing bad happens to our business. In this exact outage we are discussing, all of my cow…

2-3 hours per year is a lot of downtime. Most competent bare metal providers see maybe one major outage of less than an hour every 3-5 years. Nothing other than a facility wide power outage, if the load somehow gets dropped because the generators don't start right away as they should, or a misbehaving (only partially failing) core network infrastructure device should result in major outages when all the proper redund…

3 hours of downtime per year equals to 99,96% uptime.

In what world is that a lot of downtime?

Re: AWS EC2/RDS Outage in us-east-1

#110

Post by rosser »

tilolebo wrote: post #108
hhw wrote: post #98

Earlier quoted context omitted.

2-3 hours per year is a lot of downtime. Most competent bare metal providers see maybe one major outage of less than an hour every 3-5 years. Nothing other than a facility wide power outage, if the load somehow gets dropped because the generators don't start right away as they should, or a misbehaving (only partially failing) core network infrastructure device should result in major outages when all the proper redund…

3 hours of downtime per year equals to 99,96% uptime. In what world is that a lot of downtime?

In a world where you have SLAs with your customers, in which you commit to something better?
Post reply on HN