<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>jswanson</author><text>Newest update: 10:29 PM PDT We can confirm a portion of a single Availability Zone in the US-EAST-1 Region lost power. We are actively restoring power to the effected EC2 instances and EBS volumes. We are continuing to see increased API errors. Customers might see increased errors trying to launch new instances in the Region.&lt;p&gt;Source: &lt;a href=&quot;http://status.aws.amazon.com/?rf&quot; rel=&quot;nofollow&quot;&gt;http://status.aws.amazon.com/?rf&lt;/a&gt;
Or: &lt;a href=&quot;http://status.aws.amazon.com/rss/ec2-us-east-1.rss&quot; rel=&quot;nofollow&quot;&gt;http://status.aws.amazon.com/rss/ec2-us-east-1.rss&lt;/a&gt;</text><parent_chain></parent_chain></comment><story><title>Amazon EC2 down?</title><url>http://status.aws.amazon.com/?rf</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>chintan</author><text>We learnt our lesson the hard way after the great AWScalypse of Apr 2011.&lt;p&gt;The lesson: Use n&amp;#62;1 hosting companies (even if one of them promises a-z-multiregion-distributed-fault-tolerant-back-up)</text><parent_chain></parent_chain></comment><story><title>Amazon EC2 down?</title><url>http://status.aws.amazon.com/?rf</url></story>