mastry
I wonder if this is related to the NHC outage?

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

mopatches
AWS has posted the outage: https://health.aws.amazon.com/health/status
gslin
Something related/non-related, it's still painful to read specific timezone not UTC.
szvsw
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…

synhare
Elastic Beanstalk, Lambda, and CloudWatch returning errors for us. us-east-2
aertmann
Can confirm, S3 backed CloudFront experiencing random errors in us-east-2 for the past 15 minutes at least.
GGO
S3 on us-east-2 stabilized for us as of 2 minutes ago
mopatches
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.
MuffinFlavored
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?

wbobeirne
Also seeing Cloudfront failures on my end, both in us-east-1 and us-east-2.
chromatin
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

sdv0389
Seeing CloudFront + S3 errors in us-east-2 on our end as well.
jamroom
us-east-2 seeing tons of S3 errors.
MuffinFlavored
Yes. I can't tell if listing/reading is fine but putting (uploading) for sure seems to not be working (500 error).
sgt
This is why I use Hetzner's Object Storage. Proven and tested! /s
bethecloud
[flagged]
datadeft
[flagged]