AWS us-east-1 down • Hacker News Board

Re: AWS us-east-1 down

#191

Post by drivers99 » Tue, Jun 13, 2023, 9:15 PM UTC

yawaramin wrote: post #144

throw0101c wrote: post #70

Earlier quoted context omitted.

Basically just use the output of `date -u`.

Use `date -u -Iseconds`, please ;-)

    date: illegal option -- I
    usage: date [-jnRu] [-d dst] [-r seconds] [-t west] [-v[+|-]val[ymwdHMS]] ... 
                [-f fmt date | [[[mm]dd]HH]MM[[cc]yy][.ss]] [+format]

Re: AWS us-east-1 down

#192

Post by assimpleaspossi » Tue, Jun 13, 2023, 9:16 PM UTC

prfssnl wrote: post #174

assimpleaspossi wrote: post #172

My son delivers part-time for Amazon and all the drivers at his warehouse were sent home. So if your delivery is late or non-existent today....

Amazon Flex?

Yep

Re: AWS us-east-1 down

#193

Post by dijit » Tue, Jun 13, 2023, 9:16 PM UTC

throaway87c10f0 wrote: post #164

Mysterious lack of "AWS is bad for the internet because it is so centralized" dialog up in here. edit: for those that would downvote: HN _just_ yesterday: https://news.ycombinator.com/item?id=36295352 https://news.ycombinator.com/item?id=36295305

its just tired at this point.

everyone knows, nobody seems to care.

Another comment of mine in this thread asks the question if you can excuse downtime of your service due to AWS outages.

Consensus seems to be: yes

which is a pretty huge deal, well worth the insane cost increase of AWS by itself. No other hosting provider would grant you such an excuse.

I would weep for the centralised future of the internet, but its already here, so theres no point.

Re: AWS us-east-1 down

#194

Post by jmacjmac » Tue, Jun 13, 2023, 9:16 PM UTC

Can we find stats somewhere, something like number of outages by regions?

Re: AWS us-east-1 down

#195

Post by mdaniel » Tue, Jun 13, 2023, 9:17 PM UTC

theshrike79 wrote: post #126

Guesses, which one is it this time: * DNS * Misconfigured switch It's always one of those two.

* Cert expiry

Re: AWS us-east-1 down

#196

Post by xp84 » Tue, Jun 13, 2023, 9:17 PM UTC

rurp wrote: post #47

intsunny wrote: post #28

For those wondering: Currently PDT is 7 hours behind UTC. AWS can do so many things, reporting critical outage updates in UTC is not one of those things.

The inconsistency with timezones across different services in the AWS console has always baffled and annoyed me. Some places have a time without a timezone and I can never tell right away if it's utc, local time, or region time.

> The inconsistency [of everything, everywhere] in the AWS console

ftfy

AWS is powerful and very popular, but for the console, "it functions" must be the only condition the UI has to satisfy. Should every page use a unique table and sorting widget and UI language? Yes, please!

I'm assuming this helps them move fast, not having to coordinate with anybody or wait for a UI designer to tell them how it should look. But it's striking when compared to GCP.

Re: AWS us-east-1 down

#197

Post by andrelaszlo » Tue, Jun 13, 2023, 9:17 PM UTC

intsunny wrote: post #28

For those wondering: Currently PDT is 7 hours behind UTC. AWS can do so many things, reporting critical outage updates in UTC is not one of those things.

After spending some time in the Canary Islands I realized how nice it was to be in UTC all the time and now I have my laptop clock set to UTC. Still contemplating whether I should set Google Calendar and my smartwatch to UTC as well. 8-)

Re: AWS us-east-1 down

#198

Post by drivers99 » Tue, Jun 13, 2023, 9:18 PM UTC

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

Or Swatch Internet time (.beat time). No time zones, it's always UTC+1, with the day divided into 1000 beats.

Re: AWS us-east-1 down

#199

Post by inopinatus » Tue, Jun 13, 2023, 9:19 PM UTC

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

I will pass you the address of a struct timespec, please fill it in.

Re: AWS us-east-1 down

#200

Post by jmull » Tue, Jun 13, 2023, 9:19 PM UTC

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?

Best latency from where almost 90% of my users are?