8 ms·
Yup, same here. It has been a few minutes already. Wanna bet the green checkmark[1] will stay green until the incident is resolved? [1] https://status.aws.amaz
by alexleclair 10y ago
Yup, same here. It has been a few minutes already. Wanna bet the green checkmark[1] will stay green until the incident is resolved?
[1] https://status.aws.amazon.com/ https://status.aws.amazon.com/
- tuna-piano 10y agoStill green now, 8 minutes in.
- bpicolo 10y agoI've had a few non-Amazon providers tell me AWS things are not working in the last 5 minutes, no note from Amazon though. Nice.
- leesalminen 10y agoJust sent out a notice to our customers via our status page. I really wanted to be able to add a link back to AWS detailing the issue but that's a pipe dream I suppose.
- fudged71 10y ago... still green
- cheeze 10y agoJust went yellow Edit: nevermind
- matthuggins 10y agoStill green for me
- deleted 10y ago[deleted]
- leesalminen 10y agoJust went yellow Increased Error Rates We are investigating increased error rates for Amazon S3 requests in the US-EAST-1 Region. https://status.aws.amazon.com/ https://status.aws.amazon.com/
- nkozyra 10y agoCheck individual services ... Amazon Simple Storage Service (US Standard) Service is operating normally
- schneidmaster 10y agoDid it? Still fields of green for me.
- malloci 10y agoWhile keeping the status green for s3, they have at least put up a notice at the top: Increased Error Rates We are investigating increased error rates for Amazon S3 requests in the US-EAST-1 Region.
- schneidmaster 10y agoYeah I just now saw that. Probably regional cache clearing or something.
- jonstaab 10y agohttp://downdetector.com/status/aws-amazon-web-services http://downdetector.com/status/aws-amazon-web-services looks like a reasonable alternative place to check/report downtime.
- eicnix 10y agoWhich is coincidently down.
- booleanbetrayal 10y agodowndetectordown.com ?
- pure_ambition 10y agoyep, page won't load.
- talawahdotnet 10y agoMaybe they are hosted on S3 facepalm or maybe they just got a surge in traffic
- deleted 10y ago[deleted]
- zedpm 10y agoI just check Twitter, since Amazon's status is always a lie. My personal dashboard is still showing no problems. It's bad enough that the main public status is always green even when there's clearly a problem, but you'd think they could at least make the private status accurate.
- jonstaab 10y agoGah. It was up 3 minutes ago. Anyone have any suspicion this is another ddos episode? I saw that SO was down last night too: https://twitter.com/StackStatus/status/836450836322516992 https://twitter.com/StackStatus/status/836450836322516992
- talawahdotnet 10y agoThere was an alert on the personal health dashboard[1] a second ago, it said S3 Operational issue in us-east-1 but when I tried to view the details it showed an error. Then I refreshed and the event disappeared altogether. [1] https://phd.aws.amazon.com/phd/home?region=us-east-1#/dashboard/open-issues https://phd.aws.amazon.com/phd/home?region=us-east-1#/dashbo...
- socialentp 10y agoSame here. But it is in the general status dashboard: http://status.aws.amazon.com/ http://status.aws.amazon.com/
- hartleybrody 10y agoI'm seeing green checkmarks across the board, but they just added a notice to the top of the page: > Increased Error Rates > We are investigating increased error rates for Amazon S3 requests in the US-EAST-1 Region.
- syntheticcdo 10y agoI guess sub-1% to 100% failure rate is technically an "increase".
- Artemis2 10y agoI guess file uploads and downloads are technically "API calls".
- samstave 10y agothe worst thing is when your system cant handle these "increased error rates" as your control plane cascades failure due to something like this.... The worst "increased error rate" problem I had was when the API was failing and my autoscale system couldnt deal and launched thousands of instances because it couldnt tell when instances were launched (lack of API access) and the instances pummelled the fuck out of all other parts of the system and we basically had to reboot the entire platform.... Luckily, amazon is REALLY forgiving with respect to costs in these (and actually most) circumstance....
- salvor 10y agorecalls numerous times Yes. Yes they are. Thankfully.
- tlogan 10y agoThese service health boards are more like advertisement page then actual status of the service.
- mwfj 10y agoI guess their bizarre thinking is something along the lines of: "unless we have proof that noone can access the service, we won't change the indicator from green to yellow. Seriously: I don't understand why you guys stay with AWS.
- rattray 10y ago> I don't understand why you guys stay with AWS. Who do you recommend instead (assuming in-house or Hetzner-equiv is out of reach)? Google Cloud? Azure? Rackspace?
- johansch 10y agoGoogle Cloud if you're looking for something similar. It's just so much better and cheaper. I think a lot of the resistance here towards that kind of move is just because people are inherently lazy and they aren't paying the bill themselves. (I'm guessing a relatively large part is also selfish attachment to the market leader because of employment reasons. I hate wasting money, both for myself and for my employer, so I don't really understand this kind of thinking - but I do understand how it could flourish in a venture capital-rich time/locale.) I also recommend reading: https://thehftguy.com/2016/06/15/gce-vs-aws-in-2016-why-you-should-never-use-amazon/ https://thehftguy.com/2016/06/15/gce-vs-aws-in-2016-why-you-...
- joatmon-snoo 10y agoGoogle also doesn't have the best record for developer tools.
- johansch 10y agoLet me guess. They cancelled your grandmother's RSS reader four years ago?
- matwood 10y agoI always joke that if one of those statuses ever went to red, it means the zombie apocalypse has begun.
- cperciva 10y agoThe good news is, if Amazon's services are marked as offline, you're allowed to use Amazon Lumberyard to control nuclear power plants.
- paulddraper 10y agoThe number of non-green marks is the number of ICBMs currently in flight towards an AWS data center.
- chrisan 10y agoIn case anyone wants to see what mysterious the red icon looks like: https://status.aws.amazon.com/images/status3.gif https://status.aws.amazon.com/images/status3.gif At best when there are problems (not like now I guess) I will see the "note" green icon https://status.aws.amazon.com/images/status1.gif https://status.aws.amazon.com/images/status1.gif
- krylon 10y agoI've heard (on the Fnord new show on the most recent CCC congress, so take it with a grain of salt and a bucket of humor) that Amazon's TOS are more or less void when a Zombie Apocalypse breaks out. They had some convoluted but fairly specific wording in their TOS, whoever wrote must have had a lot of fun.
- jfim 10y agoFrom https://aws.amazon.com/service-terms/ https://aws.amazon.com/service-terms/ > 57.10 Acceptable Use; Safety-Critical Systems. Your use of the Lumberyard Materials must comply with the AWS Acceptable Use Policy. The Lumberyard Materials are not intended for use with life-critical or safety-critical systems, such as use in operation of medical equipment, automated transportation systems, autonomous vehicles, aircraft or air traffic control, nuclear facilities, manned spacecraft, or military use in connection with live combat. However, this restriction will not apply in the event of the occurrence (certified by the United States Centers for Disease Control or successor body) of a widespread viral infection transmitted via bites or contact with bodily fluids that causes human corpses to reanimate and seek to consume living human flesh, blood, brain or nerve tissue and is likely to result in the fall of organized civilization.
- jrcii 10y agoif(true){ displayGreenCheck() }
- clamprecht 10y agoCalling @jeffbarr https://news.ycombinator.com/user?id=jeffbarr https://news.ycombinator.com/user?id=jeffbarr
- adrenalinelol 10y agoLooks like his personal site isn't loading... :)
- johansch 10y agoYup, it is indeed hosted with Amazon.
- nostromo 10y agoThe red check mark is hosted on S3...
- AtheistOfFail 10y agoComment of the year.
- Kiro 10y agoFact of the year.
- deleted 10y ago[deleted]
- ak2196 10y agoThe truth is stranger than fiction. https://twitter.com/awscloud/status/836656664635846656 https://twitter.com/awscloud/status/836656664635846656
- crowbahr 10y ago"Care to share the code as an anti pattern?" brilliant.
- ceejayoz 10y agoMe right now: https://www.youtube.com/watch?v=_cHa063Mwos https://www.youtube.com/watch?v=_cHa063Mwos
- emrekzd 10y agoIn December 2015 I received an e-mail with the following subject line from AWS, around 4 am in the morning: "Amazon EC2 Instance scheduled for retirement" When I checked the logs it was clear the hardware failed 30 mins before they scheduled it for retirement. EC2 and root device data was gone. The e-mail also said "you may have already lost data". So I know that Amazon schedules servers for retirement after they already failed, green check doesn't surprise me.
- smoodles 10y agoSo just as a FYI the reason that probably happened to you is that the underlying host was failing. I am assuming they wanted to give you a window to deal with it but the host croaked before then. I've been dealing w/ AWS for a long long time and I've never seen a maintenance event go early unless the physical hardware actually died...
- problems 10y agoThat's completely ridiculous, get some fucking RAID Amazon. I order drives off newegg directly to my DC and I'm yet to lose data with the cheapest drives available in RAID10.
- prdonahue 10y agoYes, solving problems at your scale and AWS' are quite comparable.
- problems 10y agoNot saying my scale is the the same at all - but the fact they can't do something so simple that I can do it as a single individual is embarrassing at best. Simple solutions to this do scale - Linode and DigitalOcean don't have such issues for example - and while they're not Amazon scale, they are quite large and I'd say they prove the concept.
- phonon 10y ago
- ak2196 10y agoWe have a slack emoji for it called greenish. It's the classic AWS green checkmark with an info icon in the bottom. Apparently it's NOT an outage if you don't acknowledge it. It's called alt-uptime.
- Fiahil 10y agoSo, global S3 outage for more than an hour now. Still green, still talking about "US East issue". I'm amazed.
- tuna-piano 10y agoIt's crazy how much better the communication (including updates and status pages) is of the companies that rely on AWS than AWS' communication itself. https://status.heroku.com/incidents/1059 https://status.heroku.com/incidents/1059
- busterarm 10y agoAlso, https://status.pantheon.io https://status.pantheon.io
- tcsf 10y agoBlake Gentry gave a full accounting of Heroku's response process here - http://www.heavybit.com/library/video/every-minute-counts-coordinating-herokus-incident-response/ http://www.heavybit.com/library/video/every-minute-counts-co... Amazon should take notes.
- all_usernames 10y agoI feel for them. Imagine, 40 or 50 different engineering teams all responsible for updating their statuses. At this moment on the AWS status page I see random usage of the red, yellow, and green icons, even though all the status updates are "Increased error rates." What that tells me is that there's no unified communication protocol across the teams, or they're not following it. And just imagine what it's like being on the S3 team right now. I notice even Cloudflare is starting to have problems serving up pages now.
- SnowingXIV 10y agoFont Awesome went out for me for a bit, but they did a great job getting back up and keeping their users in the loop. https://status.fortawesome.com/ https://status.fortawesome.com/
- gordon_freeman 10y agoLooks like they have fixed the issue with their health dashboard now. From https://status.aws.amazon.com/ https://status.aws.amazon.com/ : Update at 11:35 AM PST: We have now repaired the ability to update the service health dashboard. The service updates are below. We continue to experience high error rates with S3 in US-EAST-1, which is impacting various AWS services. We are working hard at repairing S3, believe we understand root cause, and are working on implementing what we believe will remediate the issue.