Average EC2 Uptime?

Usually uptime is calculated in a yearly basis. So if you have a Service Level Agreement for 99.95% this means.

Usually uptime is calculated in a yearly basis. So if you have a Service Level Agreement for 99.95% this means: 365 * 0.0005 = 0.1825 days or 4.38 hours If during a year of service there is an outage and your system is down for more than that, then you are liable for compensation. As of your question, I have a server running unstopped in EC2 for about 3 months now.

I would say that their uptime is good, but if you have a mission critical application you definitely need to have a fail-over solution. A good uptime only means that they will be able to respond to an outage quickly. Even a 99.9999% uptime won't be able to save you if you aren't prepared for an outage.

Since Amazon switched to provide an SLA, I've never had an instance go down on me. When I've had instances go down in the past, Amazon has always sent a message informing me that the instance is degraded before it actually disappeared, so I've had time to start up a new instance. The previous answer makes a good point, though; EC2's service model dictates that you write your apps to handle failover to a new server if you're not prepared for extended down time.

SLA's are useless. They only measure how much risk the company is willing to take on and have no bearing on actual uptime. I've seen SLA's, with heavy penalties, offered when the company knew the could not meet the SLA in order to land the sale.

I have one client with 400+ days of EC2 uptime and another with 300+ days as measured by web pulse, this is by far the most reliable service I've worked with.

Conrad@papa ~ $ uptime 04:42:36 up 495 days, 8:51, 8 users, load average: 0.02, 0.02, 0.00.

Read the SLA carefully (aws.amazon.com/ec2-sla/) they only count "Region Unavailable" as downtime, and what is more they only count it as downtime if the region is down for 5 consecutive minutes. €œ"Annual Uptime Percentageâ€? Is calculated by subtracting from 100% the percentage of 5 minute periods during the Service Year in which Amazon EC2 was in the state of “Region Unavailable.

€? By my count this mean any downtime of less then 4 minutes is not countable. Also if they do break the SLA they are only in for %10 of the month in which you had largest downtime bill.

So if they where down for all of January and your bill was $100 they would apply a $10 credit to your account. I would have a hard time convensing my boss that this is a serious product with a SLA like that.

For my single instance running in the US-East availability zone, 9 months, 0 downtime.

2 Answer was from back in '09... 3 years straight now for that machine. – Marc Hughes May 18 at 17:19.

Checking out the AWS Service Health Dashboard will get you a good idea of any current or past issues. My experience is that the AWS uptime is better than most "traditional" hosting options (even full-blown redundant RackSpace setup...). However, simply going with AWS for uptime is like getting a car for the keychain (ok, almost.. ;)).

With an architecture utilizing AWS the big benefit is scaling (without upfront costs).

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.