Is AWS S3 having an outage?
93 points by GGO 9 months ago | 44 commentsAWS 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/
- mopatches 9 months agoAWS has posted the outage: https://health.aws.amazon.com/health/status
- gslin 9 months agoSomething related/non-related, it's still painful to read specific timezone not UTC.
- nnf 9 months agoI'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.
- crgwbr 9 months agoI’d always hoped this is what HTML’s time tag would become. Unfortunately it does almost nothing.
- yellowsir 9 months agosame with gps - the user should deside how to open direction / location links.
- yellowsir 9 months ago
- daniel_sim 9 months agoThis 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 9 months agoIt 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.
- colanderman 9 months ago
- krick 9 months agoYeah, 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.
- quesera 9 months agoAlso, some timezone labels are ambiguous, e.g. "CST".
- quesera 9 months ago
- crgwbr 9 months ago
- quesera 9 months agoYes, 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!
- nnf 9 months ago
- MuffinFlavored 9 months agohttps://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 9 months ago"Show me the incentive, and I'll show you the outcome."
- gottorf 9 months ago
- szvsw 9 months agous-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…
- jedberg 9 months agoUS 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.
- szvsw 9 months agoYeah 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.
- averageRoyalty 9 months agoUnless - like most people - you and your audience are not in the US.
- jedberg 9 months agoThis 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.
- jedberg 9 months ago
- szvsw 9 months ago
- cr125rider 9 months agoThey launch all the new fun toys there!
- iJohnDoe 9 months agoIt’s usually always cheaper there.
- jedberg 9 months ago
- synhare 9 months agoElastic Beanstalk, Lambda, and CloudWatch returning errors for us. us-east-2
- aertmann 9 months agoCan confirm, S3 backed CloudFront experiencing random errors in us-east-2 for the past 15 minutes at least.
- chromatin 9 months agoCloudfront 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
- mastry 9 months agoI wonder if this is related to the NHC outage?
- austinpena 9 months agoLooks back up: https://www.taloflow.ai/is-aws-down/us-east-2
- gp5dgk 8 months agoI 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.
- GGO 9 months agoS3 on us-east-2 stabilized for us as of 2 minutes ago
- MuffinFlavored 9 months agoYes. I can't tell if listing/reading is fine but putting (uploading) for sure seems to not be working (500 error).
- jerjerjer 9 months agoHave issues reading (500).
- jerjerjer 9 months ago
- mopatches 9 months agoWe'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 9 months agoNo issues in us-east-1 (for once....)
- mopatches 9 months agoThank you! I was misreading our logs. Can confirm no errors in us-east-1 for us as well.
- mopatches 9 months ago
- paulddraper 9 months ago
- dn0 9 months agoNext 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 :)
- wbobeirne 9 months agoAlso seeing Cloudfront failures on my end, both in us-east-1 and us-east-2.
- sdv0389 9 months agoSeeing CloudFront + S3 errors in us-east-2 on our end as well.
- sdv0389 9 months agoAnd now we're back up.
- sdv0389 9 months ago
- jamroom 9 months agous-east-2 seeing tons of S3 errors.
- sgt 9 months agoThis is why I use Hetzner's Object Storage. Proven and tested! /s
- bethecloud 9 months ago[flagged]
- datadeft 9 months ago[flagged]
- 7874cole 9 months agoNext time my boss complains about uptime, I will tell him, even AWS have downtime. Boom!