Is AWS S3 having an outage?

Something related/non-related, it's still painful to read specific timezone not UTC.

nnf · a year ago

I've long wished for built-in browser functionality that converts times to the user's preferred time zone, with perhaps a dotted outline indicating that a change was made by the browser to the page.

crgwbr · a year ago

I’d always hoped this is what HTML’s time tag would become. Unfortunately it does almost nothing.

daniel_sim · a year ago

This is worth proposing. A tag where fallback text is provided within which can be overridden by the browser with a formatted date string would be excellent.

krick · a year ago

Yeah, but, I mean, the least you could do is to say UTC-7. I'm sure everybody living in PDT knows it's, well, their time, but how the fuck should everyone else know what time PDT is.

quesera · a year ago

Yes, this can be super painful, especially when correlating information from several sources, or when traveling. It can become almost impossible when reviewing historical data.

My solution to inconsistent time rendering in AWS (sometimes UTC, sometimes localtime) is to run a separate browser profile for AWS (and third party status pages) that that's always running in UTC.

But seriously, status page people: there's no excuse for being vague about timezones!

us-east-1 gang rise up!!

For once I can feel mild pleasure at seeing the tables turned…

To be honest I don’t know why all my projects are always in USE1, I guess it’s just because that’s where we have always had them for my lab so I’ve stuck with it for no good reason…

jedberg · a year ago

US East 1 was the default region until a few years ago. If your account is older than that, then most likely all your stuff is there.

szvsw · a year ago

Yeah the account is from like 2019 or so. But still, I’m spinning everything up with Terraform or AWS Copilot, so it is still an active choice on my end to put it in us-east-1.

averageRoyalty · a year ago

Unless - like most people - you and your audience are not in the US.

cr125rider · a year ago

They launch all the new fun toys there!

iJohnDoe · a year ago

It’s usually always cheaper there.

mopatches · a year ago

AWS has posted the outage: https://health.aws.amazon.com/health/status

gslin · a year ago

MuffinFlavored · a year ago

https://health.aws.amazon.com/health/status

Rhetorical question (I know why, humans manually involved, incentive to not report SLA breakage, etc.): How does their status page not auto-update when one of their core APIs goes to basically 99% 500 (or even above 5% 500) status error?

gottorf · a year ago

"Show me the incentive, and I'll show you the outcome."

synhare · a year ago

Elastic Beanstalk, Lambda, and CloudWatch returning errors for us. us-east-2

aertmann · a year ago

Can confirm, S3 backed CloudFront experiencing random errors in us-east-2 for the past 15 minutes at least.

chromatin · a year ago

Cloudfront is: my small, not even yet profitable SaaS landing page and javascript frontend, served by CloudFront, are down since about 17 minutes ago (3:28 US Eastern)

the API whcih sits behind ELB is working fine

edit: us-east-2

mastry · a year ago

I wonder if this is related to the NHC outage?

https://news.ycombinator.com/item?id=41771629