[HN Gopher] Is AWS S3 having an outage?
___________________________________________________________________
Is AWS S3 having an outage?
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/
Author : GGO
Score : 79 points
Date : 2024-10-07 19:41 UTC (3 hours ago)
| wbobeirne wrote:
| Also seeing Cloudfront failures on my end, both in us-east-1 and
| us-east-2.
| MuffinFlavored wrote:
| Yes. I can't tell if listing/reading is fine but putting
| (uploading) for sure seems to not be working (500 error).
| jerjerjer wrote:
| Have issues reading (500).
| jamroom wrote:
| us-east-2 seeing tons of S3 errors.
| synhare wrote:
| Elastic Beanstalk, Lambda, and CloudWatch returning errors for
| us. us-east-2
| chromatin wrote:
| 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
| mopatches wrote:
| 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.
| paulddraper wrote:
| No issues in us-east-1 (for once....)
| mopatches wrote:
| Thank you! I was misreading our logs. Can confirm no errors
| in us-east-1 for us as well.
| GGO wrote:
| S3 on us-east-2 stabilized for us as of 2 minutes ago
| MuffinFlavored wrote:
| 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?
| gottorf wrote:
| "Show me the incentive, and I'll show you the outcome."
| sdv0389 wrote:
| Seeing CloudFront + S3 errors in us-east-2 on our end as well.
| sdv0389 wrote:
| And now we're back up.
| aertmann wrote:
| Can confirm, S3 backed CloudFront experiencing random errors in
| us-east-2 for the past 15 minutes at least.
| mopatches wrote:
| AWS has posted the outage:
| https://health.aws.amazon.com/health/status
| szvsw wrote:
| 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...
| cr125rider wrote:
| They launch all the new fun toys there!
| jedberg wrote:
| 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.
| averageRoyalty wrote:
| Unless - like most people - you and your audience are not in
| the US.
| jedberg wrote:
| This wasn't an "everyone is in the US" type of post. Even
| for non-US folks, for a long time the default region was
| us-east-1, until they switched it to eu-west-1, and about
| 1/2 of all of AWS customers are in the US, or at least used
| to be until recently.
| gslin wrote:
| Something related/non-related, it's still painful to read
| specific timezone not UTC.
| nnf wrote:
| 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.
| krick wrote:
| 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.
| daniel_sim wrote:
| 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.
| colanderman wrote:
| 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.
| crgwbr wrote:
| I'd always hoped this is what HTML's time tag would become.
| Unfortunately it does almost nothing.
| austinpena wrote:
| Looks back up: https://www.taloflow.ai/is-aws-down/us-east-2
| sgt wrote:
| This is why I use Hetzner's Object Storage. Proven and tested! /s
| mastry wrote:
| I wonder if this is related to the NHC outage?
|
| https://news.ycombinator.com/item?id=41771629
| 7874cole wrote:
| Next time my boss complains about uptime, I will tell him, even
| AWS have downtime. Boom!
| dn0 wrote:
| 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 :)
___________________________________________________________________
(page generated 2024-10-07 23:01 UTC)