AWS has posted the outage: https://health.aws.amazon.com/health/status
Something related/non-related, it's still painful to read specific timezone not UTC.
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.
I’d always hoped this is what HTML’s time tag would become. Unfortunately it does almost nothing.
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.
It exists: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/ti...
As a nearby comment indicates, it's not clear any browser makes use of it.
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.
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…
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.
They launch all the new fun toys there!
Elastic Beanstalk, Lambda, and CloudWatch returning errors for us. us-east-2
Can confirm, S3 backed CloudFront experiencing random errors in us-east-2 for the past 15 minutes at least.
Looks back up: https://www.taloflow.ai/is-aws-down/us-east-2
S3 on us-east-2 stabilized for us as of 2 minutes 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?
"Show me the incentive, and I'll show you the outcome."
We're seeing CloudFront and S3 issues in us-east-2 in multiple accounts. No errors in us-east-1 or and ap-south-1.
No issues in us-east-1 (for once....)
Thank you! I was misreading our logs. Can confirm no errors in us-east-1 for us as well.
Also seeing Cloudfront failures on my end, both in us-east-1 and us-east-2.
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
Seeing CloudFront + S3 errors in us-east-2 on our end as well.
And now we're back up.
us-east-2 seeing tons of S3 errors.
Yes. I can't tell if listing/reading is fine but putting (uploading) for sure seems to not be working (500 error).
Have issues reading (500).
This is why I use Hetzner's Object Storage. Proven and tested! /s