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

71–80 of 331 posts

Re: AWS us-east-1 down

#71

Post by kobalsky »

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

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.        $$$$$$$$$$$$$$

Re: AWS us-east-1 down

#72

Post by jen20 »

TremendousJudge wrote: post #68
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.

It's also usually extremely US-centric. Nobody outside of North America has any idea what "PDT" or "Mountain Time" means.

Not to mention they conflict. CST can be "Central Standard Time", "China Standard Time" or "Cuba Standard Time" and so forth...

Re: AWS us-east-1 down

#73

Post by rotten »

thefourthchime wrote: post #32
jarym wrote: post #26

us-east-1 seems to be very 'special' compared to the other regions - I wonder if they will ever align it with the rest of them.

I think a lot of companies just do everything there and pinky promise one day they'll go multi-region.

I worked with a devops person who moved everything we had set up in other regions _to_ US-East-1 because that is where you are supposed to run stuff. According to him, the other regions were just for DR stuff.

Re: AWS us-east-1 down

#74

Post by andrewmcwatters »

impulser_ wrote: post #69

Why does everyone keep deploying their products to this one region when it always seems like the one that fails? We don't use big cloud were I work, so maybe I'm missing something. Does East-1 offer something other don't?

There's a lot of software, iirc even Amazon's own dashboards, that simply defaults to us-east-1.

Re: AWS us-east-1 down

#76

Post by mardifoufs »

rbosinger wrote: post #24

It's always during the demos to the stakeholders, isn't it?

I'm so glad my demo today was specifically about local inference on... Windows. I guess working I finally found an upside to doing ML outside Linux ; we don't have Windows VMs on AWS!! :)

Re: AWS us-east-1 down

#78

Post by conductr »

dylan604 wrote: post #66
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.

just report it in epoch seconds

that's based on UTC, so just use UTC?

Re: AWS us-east-1 down

#79

Post by donalhunt »

TremendousJudge wrote: post #68
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.

It's also usually extremely US-centric. Nobody outside of North America has any idea what "PDT" or "Mountain Time" means.

I mostly struggle with Irish Standard Time (used for DST in Ireland) and Indian Standard Time which have the same acronym. :(

Thankfully, I learnt a long time ago to use ISO 8601 and UTC for dates and times. I still revert to PST/PDT if my audience is primarily left coast based.

Post reply on HN