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

AWS us-east-1 down

news.ycombinator.com

Post reply on HN
Print view View original

321–330 of 331 posts

Re: AWS us-east-1 down

#321

Post by tedmiston »

dijit wrote: post #4

I wonder if this is a coincidence or if us-east-1 is simply down enough that I'm just experiencing selection bias; but I posted a poll on twitter earlier today: https://twitter.com/dijit/status/1668678588713824257 Contents: > Has anyone ever actually had customers accept an outage because AWS was down; or is this just cloud evangelicalism copium? > [ ] Yeah, outages free pass > [ ] No, they say to use AZ's

> Has anyone ever actually had customers accept an outage because AWS was down...

Whether customers "accept" it or not just comes down to what's in your SLA, if you have one in the first place, and if they are on a contract tier that it applies to. [Many servies provide no SLA for hobby / low tiers, beta features, etc.]

Firebase Auth, for instance, offers no SLA at all [1].

I would be curious to see statistics across a range of SLAs for what % include a force majeure or similar clause which excludes responsibility for upstream outages. I would expect this to be more common with more technical products / more technical customers.

[1]: https://stackoverflow.com/a/60500860/149428

Re: AWS us-east-1 down

#322

Post by elzbardico »

xyst wrote: post #112
kobalsky wrote: post #71

Earlier quoted context omitted.

it's important to inform customers about the resiliency of their systems and let them pick how far they are going to invest for it. then you get to eat popcorn when stuff explodes. * single server event. $ * multi server event. $$ * single az event. $$$ * multi az event. $$$$ * global provider event. $$$$$ * cross provider event. $$$$$$ * alien invasion. $$$$$$$$$$$$$$

Just need to deploy your service on Mars AND Earth. Duh

Multi-planetary-AZ DB cluster deployments. Putting the emphasis on "Eventual" in eventual consistency. Go for a walk before retrying reading from this replica!

Re: AWS us-east-1 down

#323

Post by throw03172019 »

OJFord wrote: post #268
throw03172019 wrote: post #252

My Whole Foods grocery pickup order was affected by this outage. They couldn’t check me in. Groceries were packed in the fridge but they told me to come back later. What a waste of time.

Are you just guessing it's related or is there a reason to be sure? Either way, does seem sjll6 to have no manual fallback 'check-in' (or policy-level ability to bypass the need for it) mechanism.

The Whole Foods employee working the pick-up area told me.

Re: AWS us-east-1 down

#326

Post by prfssnl »

throw03172019 wrote: post #252

My Whole Foods grocery pickup order was affected by this outage. They couldn’t check me in. Groceries were packed in the fridge but they told me to come back later. What a waste of time.

>They couldn’t check me in.

Are you an Amazon Flex driver? Or do you even need to check-in to pickup your order as a customer?

Re: AWS us-east-1 down

#328

Post by kroltan »

tedmiston wrote: post #318
kroltan wrote: post #60

Earlier quoted context omitted.

Semi-related: if you ever feel the need to report times to a global audience, not only make sure to always report the timezone (even if it is the same as the user's), but also use UTC offsets rather than timezone names. Life is too short to remember what each timezone name means and converting to it, UTC offsets are much easier on the mental calculator.

> Life is too short to remember what each timezone name means and converting to it, UTC offsets are much easier on the mental calculator. Many people also get the timezone names completely wrong. I've had multiple scheduling email exchanges where someone says X pm EST not realizing that at the time it's currently EDT and that EST ≠ EDT. And yet, for some reason, the two-letter abbreviations (e.g., ET) that are techni…

Fair enough, but please only use that with strictly USA audiences. (And remember that public information likely will not be targeted to strictly USA audiences)

Names don't carry any information intrinsically, they are only a reference to the actual information, and the offset information is pretty short, so why not just provide the information directly?

"X pm GMT-3" only requires the reader to know their own timezone offset, unlike "X pm Brasilia time" (which is inaccurately known as São Paulo time outside Brazil) or "X pm BRT", which requires the reader to both know what that timezone means, and their own (or, more likely, requires them to look the conversion up).

(And if the difference between GMT and UTC is significant, I hope it didn't take my comment to convince you about using offsets :> )

Re: AWS us-east-1 down

#329

Post by rovr138 »

jxf wrote: post #275
mananaysiempre wrote: post #248

Earlier quoted context omitted.

If the world were fair, we’d be calling these Eggert time zones, as Paul Eggert (longtime tzdata maintainer until the copyright trolls came) invented them; but it isn’t. (You probably still meant IANA the Internet org not IATA the aviation one.)

Is there context on this? I'd be interested in the history of what happened and why Eggert is no longer involved.

Just found this, https://en.wikipedia.org/wiki/Tz_database#2011_lawsuit

Re: AWS us-east-1 down

#330

Post by assimpleaspossi »

prfssnl wrote: post #327
assimpleaspossi wrote: post #192

Earlier quoted context omitted.

Yep

I heard they are paying Flex drivers for that day. Well, most of them.

They did.

Say what one wants about Amazon or how they treat delivery drivers. My son told me of some experiences he's had--including having his car totaled on an icy river bridge at four in the morning--and Amazon was on top of it, empathetic, and did more than what was expected.

Post reply on HN