from Hacker News

Is AWS S3 having an outage?

by GGO on 10/7/24, 7:41 PM with 44 comments

• by mopatches on 10/7/24, 7:54 PM

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

• by gslin on 10/7/24, 8:15 PM

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

• by MuffinFlavored on 10/7/24, 7:48 PM

  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?

• by szvsw on 10/7/24, 8:12 PM

  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…

• by synhare on 10/7/24, 7:45 PM

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

• by aertmann on 10/7/24, 7:49 PM

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

• by chromatin on 10/7/24, 7:45 PM

  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

• by mastry on 10/7/24, 10:14 PM

  I wonder if this is related to the NHC outage?

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

• by austinpena on 10/7/24, 8:28 PM

  Looks back up: https://www.taloflow.ai/is-aws-down/us-east-2

• by gp5dgk on 10/8/24, 11:20 PM

  I am seeing on multiple AWS accounts CloudWatch log groups are not loading. It even says you have no log groups, that's not the case.

• by GGO on 10/7/24, 7:47 PM

  S3 on us-east-2 stabilized for us as of 2 minutes ago

• by MuffinFlavored on 10/7/24, 7:44 PM

  Yes. I can't tell if listing/reading is fine but putting (uploading) for sure seems to not be working (500 error).

• by mopatches on 10/7/24, 7:45 PM

  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.

• by dn0 on 10/7/24, 10:44 PM

  Next time you can also check https://cloudstatus.page/cloud/aws/issues

  I guess I'll increase the frequency of some probes to get better aligned with the official timeline :)

• by wbobeirne on 10/7/24, 7:42 PM

  Also seeing Cloudfront failures on my end, both in us-east-1 and us-east-2.

• by sdv0389 on 10/7/24, 7:48 PM

  Seeing CloudFront + S3 errors in us-east-2 on our end as well.

• by jamroom on 10/7/24, 7:44 PM

  us-east-2 seeing tons of S3 errors.

• by sgt on 10/7/24, 8:34 PM

  This is why I use Hetzner's Object Storage. Proven and tested! /s

• by 7874cole on 10/7/24, 10:24 PM

  Next time my boss complains about uptime, I will tell him, even AWS have downtime. Boom!