<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>halestock</author><text>I can&amp;#x27;t help but wonder, with the increases in attrition across the industry, are we hitting some kind of tipping point where the institutional knowledge in these massive tech corporations is disappearing?&lt;p&gt;Mistakes happen all the time but when all the people who intimately know how these systems work leave for other opportunities, disasters are bound to happen more and more.</text><parent_chain></parent_chain></comment><story><title>AWS&apos;s us-east-1 region is experiencing issues</title><url>https://health.aws.amazon.com/phd/status</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>saltypal</author><text>Based on our telemetry, this started as NXDOMAINs for sqs.us-east-1.amazonaws.com beginning in modest volumes at 20:43 UTC and becoming a total outage at 20:48 UTC. Naturally, it was completely resolved by 20:57, 5 minutes before anything was posted in the &amp;quot;Personal Health Dashboard&amp;quot; in the AWS console.&lt;p&gt;It takes a while to find a Vice President, I guess.</text><parent_chain></parent_chain></comment><story><title>AWS&apos;s us-east-1 region is experiencing issues</title><url>https://health.aws.amazon.com/phd/status</url></story>