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

AWS us-east-1 outage

status.aws.amazon.com

Post reply on HN
Print view View original

911–920 of 1001 posts

Re: AWS us-east-1 outage

#911

Post by mastax »

balls187 wrote: post #907
jesboat wrote: post #484

Earlier quoted context omitted.

> This issue is affecting the global console landing page, which is also hosted in US-EAST-1 Even this little tidbit is a bit of a wtf for me. Why do they consider it ok to have anything hosted in a single region? At a different (unnamed) FAANG, we considered it unacceptable to have anything depend on a single region. Even the dinky little volunteer-run thing which ran https://internal.site.example/~someEngineer was…

MAANG* How long before Meta takes over for Facebook?

Well, alphabet needs to take over for Google first.

Re: AWS us-east-1 outage

#912

Post by junyoon »

banana_giraffe wrote: post #273
bobviolier wrote: post #258

Earlier quoted context omitted.

https://status.aws.amazon.com/ still shows all green for me

It's acting odd for me. Shows all green in Firefox, but shows the error in Chrome even after some refreshes. Not sure what's caching where to cause that.

firefox has more aggressive caching than other browsers I think

Re: AWS us-east-1 outage

#913

Post by selimthegrim »

api wrote: post #312
temuze wrote: post #113

Friends tell friends to pick us-east-2. Virginia is for lovers, Ohio is for availability.

I live in Ohio and can confirm. If the Earth were destroyed by an asteroid Ohio would be left floating out there somehow holding onto an atmosphere for about ten years.

Always has been.

Re: AWS us-east-1 outage

#915

Post by taf2 »

booleanbetrayal wrote: post #900

I'm pretty well versed in Kinesis / Firehose errors these days. I just got a new Firehose error I've never seen before: > Firehose error: Slow down. I wonder if they had to introduce a new exception / rate-limit to mediate this issue ...

I noticed some additional rate limiting as we're processing a backlog of data from earlier today... It's possible they just have increased the normal thresholds while everyone is in a similar recovery mode and they too are bring capacity back to normal levels.

Re: AWS us-east-1 outage

#916

Post by kgeist »

Kavelach wrote: post #381
ethbr0 wrote: post #235

Earlier quoted context omitted.

> It should be costing them trust not to push it when they should though. This is what Amazon, the startup, understood. Step 1: Always make it right and make the customer happy, even if it hurts in $. Step 2: If you find you're losing too much money over a particular issue, fix the issue . Amazon, one of the world's largest companies, seems to have forgotten that the risk of not reporting accurately isn't money, but…

> It's late Soviet Union in a nutshell How come an action of a private company in a capitalist country is like the Soviet Union?

They talk about gaming the metrics. Something the Soviet Union was known for.

Re: AWS us-east-1 outage

#917

Post by savant_penguin »

mypalmike wrote: post #838
savant_penguin wrote: post #793

Earlier quoted context omitted.

they usually beg you to use multiple availability zones though I'm not sure how many aws services are easy to spawn at multiple regions

Which ones are difficult to deploy in multiple regions?

iirc elb+autoscaling

Re: AWS us-east-1 outage

#918

Post by toomanyrichies »

cronix wrote: post #789
all_usernames wrote: post #560

Earlier quoted context omitted.

Every damn Well-Architected Framework includes multi-AZ if not multi-region redundancy, and yet the single access point for their millions of customers is single-region. Facepalm in the form of $100Ms in service credits.

> Facepalm in the form of $100Ms in service credits. It was also greatly affecting Amazon.com itself. I kept getting sporadic 404 pages and one was during a purchase. Purchase history wasn't showing the product as purchased and I didn't receive an email, so I repurchased. Still no email, but the purchase didn't end in a 404, but the product still didn't show up in my purchase history. I have no idea if I purchased an…

They're also unable to refund Kindle book orders via their website. The "Request a refund" page has a 500 error, so they fall back to letting you request a call from a customer service rep. Initiating this request also fails, so they then fall back to showing a 1-888 number that the customer can call. Of course, when I tried to call, I got "All circuits are busy".

Re: AWS us-east-1 outage

#919

Post by [deleted] »

notwedtm wrote: post #906
codegeek wrote: post #724

Earlier quoted context omitted.

"Yes, VP approval is needed to make any updates on the status dashboard." If services are clearly down, why is this needed ? I can understand the oversights required for a company like Amazon but this sounds strange to me. If services are clearly down, I want that damn status update right away as a customer.

Because "services down" also means SLA credits.

[deleted]

Re: AWS us-east-1 outage

#920

Post by jhugo »

jhugo wrote: post #359
blahyawnblah wrote: post #163

Earlier quoted context omitted.

Lots of services are only in us-east-1. The sso system isn't working 100% right now so that's where I assume it's hosted.

You can pick the region for SSO — or even use multiple. Ours is in ap-southeast-1 and working fine — but then the console that it signs us into is only partially working presumably due to dependencies on us-east-1.

(Correction: you can choose the region but you can't use multiple for the same org.)
Post reply on HN