Is AWS S3 having an outage?

#1

Post by GGO » Mon, Oct 07, 2024, 7:41 PM UTC

AWS status https://health.aws.amazon.com/health/status shows all green but I am having internal server errors returned from S3. Anyone else having this issue? Downdetector has spike for AWS outage coincidentally https://downdetector.com/status/aws-amazon-web-services/

Re: Is AWS S3 having an outage?

#2

Post by wbobeirne » Mon, Oct 07, 2024, 7:42 PM UTC

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

Re: Is AWS S3 having an outage?

#3

Post by MuffinFlavored » Mon, Oct 07, 2024, 7:44 PM UTC

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

Re: Is AWS S3 having an outage?

#4

Post by jamroom » Mon, Oct 07, 2024, 7:44 PM UTC

us-east-2 seeing tons of S3 errors.

Re: Is AWS S3 having an outage?

#5

Post by synhare » Mon, Oct 07, 2024, 7:45 PM UTC

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

Re: Is AWS S3 having an outage?

#6

Post by chromatin » Mon, Oct 07, 2024, 7:45 PM UTC

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

Re: Is AWS S3 having an outage?

#7

Post by mopatches » Mon, Oct 07, 2024, 7:45 PM UTC

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.

Re: Is AWS S3 having an outage?

#8

Post by jerjerjer » Mon, Oct 07, 2024, 7:47 PM UTC

MuffinFlavored wrote: post #3

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).

Re: Is AWS S3 having an outage?

#9

Post by GGO » Mon, Oct 07, 2024, 7:47 PM UTC

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

Re: Is AWS S3 having an outage?

#10

Post by MuffinFlavored » Mon, Oct 07, 2024, 7:48 PM UTC

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?