Amazon Web Services Downtime Counter

http://www.awsdowntime.com/

by yuvadam • 15 years ago

38 28 15 years ago

awsdowntime.com

sktrdie• 15 years ago

How do you guys come up with great web-designing skills even for these simple web pages?

yuvadam5• 15 years ago

I used blueprint in this case. I have a good history with it, and it always gives me clean, crisp results.

PStamatiou• 15 years ago

Attention to typography itself can lead to some pretty compelling designs. As Cameron Moll once said, great designers use typography/text as a UI element.

ollysb• 15 years ago

I'm presuming this only includes downtime since the latest outage began?

forwardslash2• 15 years ago

Ironically this page is down for me.

yuvadam5• 15 years ago

Probably DNS hasn't propagated yet. You can use http://goo.gl/rY6cz

forwardslash2• 15 years ago

That works, many thanks.

jdp233• 15 years ago

Is the percentage right?

AWS went down about 30 hours ago, and in the Seattle area we're 111 days + 7 hours into the year. so by my calculations, it's closer to 98.9% than 99.66...%

Or did I make a mistake?

yuvadam5• 15 years ago

The calculation is an inclusive, yearly, uptime percentage. This is assuming no other downtime will occur during 2011.

Additionally, this percentage is adequate for the 365-subsequent-days credit calculation. It doesn't matter at which 365-day window you look, my calculation assumes no other downtime has occurred, nor will occur.

jdp233• 15 years ago

Got it. If that's what you're reporting, then you might want slightly different language: "have been up" is past tense, so implied (at least to me) that you were just talking about year-to-date.

lobster_johnson• 15 years ago

For the purposes of claiming service credits from Amazon, the percentage given on your page is not necessarily useful. Amazon's uptime guarantee applies to the trailing 365 days. You can claim those service credits at any time.

Thus, if Amazon had an incident 2 months ago and have another incident now, then your own window is the range [now - 1.year, now] and you figure that this calculates to a 99.8% downtime for you and claim your credit. Your percentage then necessarily goes to zero because your window restarts. But for everyone else who doesn't claim a credit, the window continues to roll forward.

mattdawson2• 15 years ago

How on earth is this number actually being calculated? I'm an AWS customer and all of my ec2 EBS instances are up and running - and that's in us-east-1b, which is IIRC where this outage occurred.

yuvadam5• 15 years ago

Your us-east-1b is not other customers us-east-1b. Availability zones are permuted randomly for each customer.

Nonetheless, just because you haven't been affected, doesn't mean other have not been, or still aren't.

bgentry• 15 years ago

I really wish they would have picked another way to deal with the fact that people write crappy software that only launches in "1a" and "1b".

They dealt with the resulting capacity imbalances by randomly remapping AZs for new accounts, but AFAIK they're never publicly acknowledged this so most people aren't aware. Instead they should have just started charging more for resources requested explicitly in those zones until people fixed their poorly written software.

mattdawson2• 15 years ago

Right, I understand that. But it seems irresponsible to suggest - as I think this site does - that the entirety of AWS has the uptime you're advertising.

SpikeGronim2• 15 years ago

"Availability zones are permuted randomly for each customer"

This statement is false. AZs map directly to physical facilities. If you and I both ask for instances in us-east-1b they will have lower ping times than if one of us has an instance in us-east-1c.

Disclaimer: I used to work for AWS.

keithba• 15 years ago

I'm missing something - hours since the start of the year: 2671. Hours of uptime: 2641.

That lead to a downtime calc of 98.88 or so.

*edited for language clarity. Gah! Original sentence above implied that downtime was 2641.

T-hawk• 15 years ago

Picking the nit: 2641 hours of uptime from the start of the year until the downtime began, so the uptime calc is 98.88.

jdp233• 15 years ago

it just feels like 2641 hours of downtime since it started :-)

snorkel• 15 years ago

I'm AWS! I'm cloudy, I'm bursty, and I'm rocking two nines!

tommoor• 15 years ago

urgh, why not make something useful.

akl• 15 years ago

One might point out that "AWS" isn't down, EC2 in VA is entirely broken for a certain notable section of customers.

molecule• 15 years ago

I applaud the notion, but the implementation is atrocious hyberpole:

- simple javascript algebra that does not monitor or report any status data?

- equating the entirety of AWS w/ one region of EBS-backed EC2 instances is hyperbole that does not contribute to the discussion.

Amazon Web Services Downtime Counter

Related Stories