Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AWS us-west-2 issues

news.ycombinator.com

Post reply on HN
Print view View original

101–107 of 107 posts

Re: AWS us-west-2 issues

#101

Post by dylan604 »

fortunateregard wrote: post #90
dylan604 wrote: post #12

https://downdetector.com/status/aws-amazon-web-services/ My Roomba isn't working!!! hahahaha!

On an unrelated note, I opened this url in a new tab, took a quick look, then came back to read the comments. A few minutes after I hear the fans on my pc start ramping up. Sure enough, I open the system monitor and see chrome going crazy on my CPU. In chrome, I open the task manager, then click sort by CPU. The entry at the top of the list reads: > subframe: facebook[dot]com I get taken to the open downdetector.com…

Facebook is losing too much money from iOS denying it the goods, so theZuck has mandated SDK to start mining crypto?

Re: AWS us-west-2 issues

#102

Post by faangiq »

socialismisok wrote: post #25
willio58 wrote: post #17

It's crazy to me how long it takes Amazon to notify users that there is even an issue. I think it took 15 minutes for them to acknowledge an issue, thats a lot of time for our services.

That's because it's a political issue inside AWS. They have the technology to report it automatically, but there's a strong pressure not to post "green-i" or yellow or red, because those things impact SLA payments. So if there's any way they can spin it as not an outage they will try not to post it.

They are brutally political and incompetent.

Re: AWS us-west-2 issues

#103

Post by haloboy777 »

ogn3rd wrote: post #71
socialismisok wrote: post #25

Earlier quoted context omitted.

That's because it's a political issue inside AWS. They have the technology to report it automatically, but there's a strong pressure not to post "green-i" or yellow or red, because those things impact SLA payments. So if there's any way they can spin it as not an outage they will try not to post it.

Can confirm this, it's political. It's always great seeing the "rationality" for not doing the right thing. After the 3 outages last December, I can remember a certain person in a certain global outage slack channel laughing at customers who weren't "resilient" enough to withstand the outage. Then AWS focused a resiliency campaign to document all those customers risks, as if AWS's own poorly designed system wasn't th…

I know many services that do this. And even if you fight with customer care for RCA they go silent and pass you around to other team members to whom you need to tell the problem again and again.

Re: AWS us-west-2 issues

#104

Post by giaour »

chasd00 wrote: post #69
giaour wrote: post #65

Earlier quoted context omitted.

> as far as not getting out, any lock unable to be unlocked from inside seems like something should not be allowed to be made. ever. This would vary by jurisdiction, but locks without an unlock lever are usually prohibited by the fire code.

interesting. my back door has a deadbolt requiring a key on both sides. ..it's an old house.

My house still has a deadbolt like that, too. They were popular for a while, especially on doors with large glass panes (so that would-be intruders couldn’t smash the glass and unlock the door w/o a key).

Re: AWS us-west-2 issues

#105

Post by enapupe »

davidjfelix wrote: post #77
enapupe wrote: post #72

Could any of you clarify to me why do we have "Edge" domain rather than a specific region?

Yeah, you can select "edge" for some resources (API Gateway and Lambda are two that come to mind) which just means it's located in all regions plus some additional "edge" infrastructure that isn't available as a region. AWS puts some restrictions on edge resources since there isn't enough capacity or full-region functionality. Usually you pick this for stuff that is CDN oriented and front a regional service with that…

Exactly, why did it failed yesterday then? If supposedly just us-west-2 was down :(

Re: AWS us-west-2 issues

#106

Post by 0xbadcafebee »

ramesh31 wrote: post #45

The moment I get a whiff of AWS issues, that's basically a wrap on the day. I'm not going to spend my time wondering why something isn't working today because somewhere down the chain it is undoubtedly a silently failing AWS service driving me mad. The whole house of cards comes tumbling down and things stop working that Amazon will swear up down left and right are 100% healthy. Sadly this has become a monthly occurr…

This is a good point: we should come up with a list of what services use what cloud providers, so not all our eggs are in one basket.

Re: AWS us-west-2 issues

#107

Post by davidjfelix »

enapupe wrote: post #105
davidjfelix wrote: post #77

Earlier quoted context omitted.

Yeah, you can select "edge" for some resources (API Gateway and Lambda are two that come to mind) which just means it's located in all regions plus some additional "edge" infrastructure that isn't available as a region. AWS puts some restrictions on edge resources since there isn't enough capacity or full-region functionality. Usually you pick this for stuff that is CDN oriented and front a regional service with that…

Exactly, why did it failed yesterday then? If supposedly just us-west-2 was down :(

My guess is if you saw an outage with edge, it was because you were being routed by us-west-2
Post reply on HN