Is AWS S3 having an outage?

93 pointsGGO1y ago44 comments

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/

44 comments

mopatches1y ago

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

gslin1y ago

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

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

crgwbr1y ago

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

1 more reply

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

1 more reply

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

1 more reply

quesera1y 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!

MuffinFlavored1y 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?

gottorf1y ago

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

szvsw1y ago

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…

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

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

averageRoyalty1y ago

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

1 more reply

cr125rider1y ago

They launch all the new fun toys there!

iJohnDoe1y ago

It’s usually always cheaper there.

synhare1y ago

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

aertmann1y ago

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

chromatin1y 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

mastry1y ago

I wonder if this is related to the NHC outage?

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

austinpena1y ago

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

gp5dgk1y ago

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.

GGOOP1y ago

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

MuffinFlavored1y ago

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

jerjerjer1y ago

Have issues reading (500).

mopatches1y ago

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.

paulddraper1y ago

No issues in us-east-1 (for once....)

mopatches1y ago

Thank you! I was misreading our logs. Can confirm no errors in us-east-1 for us as well.

dn01y ago

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

wbobeirne1y ago

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

sdv03891y ago

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

sdv03891y ago

And now we're back up.

jamroom1y ago

us-east-2 seeing tons of S3 errors.

sgt1y ago

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

7874cole1y ago

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

j / k navigate · click thread line to collapse

44 comments

mopatches1y ago

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

gslin1y ago

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

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

crgwbr1y ago

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

1 more reply

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

1 more reply

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

1 more reply

quesera1y 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!

MuffinFlavored1y ago

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

gottorf1y ago

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

szvsw1y ago

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…

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

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

averageRoyalty1y ago

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

1 more reply

cr125rider1y ago

They launch all the new fun toys there!

iJohnDoe1y ago

It’s usually always cheaper there.

synhare1y ago

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

aertmann1y ago

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

chromatin1y 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

mastry1y ago

I wonder if this is related to the NHC outage?

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

austinpena1y ago

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

gp5dgk1y ago

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.

GGOOP1y ago

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

MuffinFlavored1y ago

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

jerjerjer1y ago

Have issues reading (500).

mopatches1y ago

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.

paulddraper1y ago

No issues in us-east-1 (for once....)

mopatches1y ago

Thank you! I was misreading our logs. Can confirm no errors in us-east-1 for us as well.

dn01y ago

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

wbobeirne1y ago

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

sdv03891y ago

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

sdv03891y ago

And now we're back up.

jamroom1y ago

us-east-2 seeing tons of S3 errors.

sgt1y ago

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

7874cole1y ago

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

j / k navigate · click thread line to collapse