<story><title>Summary of the AWS Service Event in the Sydney Region</title><url>http://aws.amazon.com/message/4372T8/</url></story><parent_chain><item><author>jaketay</author><text>Our instances with ap-southeast-2 were out for around 12 hours. We used multiple availability zones and it didn&amp;#x27;t prevent downtime at all. It&amp;#x27;s very interesting the difference between AWS and Google outage responses. AWS is down for 12+ hours for some customers, force each customer to chase service level credits and sign off the postmortem with a nameless &amp;amp; faceless &amp;quot;-The AWS Team&amp;quot;. Not one person at AWS was willing to take responsibility for this failure.&lt;p&gt;Whereas Google was recently down for less than 18 minutes. A VP at Google sent an email advising all affected customers, posted continuous updates to their status page, sent a further apology email at the conclusion, posted a service credit exceeding the SLA to all customers in the zone (without forcing customers to chase this themselves with billing) and lastly wrote one of the most well written post mortems I&amp;#x27;ve ever seen. AWS has much to learn from Google about how to handle outages properly.</text></item></parent_chain><comment><author>jread</author><text>I independently monitor availability of 150 public cloud services and only observed 1.73 hours downtime for this event. This is the first EC2 outage I&amp;#x27;ve observed in any region for over 6 months. According to my stats, in 2015 EC2 was highly available with 6 of 9 regions (including every US and EU region) having no outages, and total average service availability of 99.998% (78% of downtime in sa-east-1). I haven&amp;#x27;t observed a single outage in us-west-2 or eu-west-1 in nearly 3 years. This compared to 16-33 minutes of downtime in every region for GCE in 2015, and total average availability of 99.995%. Additionally, since 2013 I&amp;#x27;ve never observed a global EC2 outage like the 4&amp;#x2F;11&amp;#x2F;2016 GCE event.&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;cloudharmony.com&amp;#x2F;status-for-aws&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;cloudharmony.com&amp;#x2F;status-for-aws&lt;/a&gt;</text></comment>
<story><title>Summary of the AWS Service Event in the Sydney Region</title><url>http://aws.amazon.com/message/4372T8/</url></story><parent_chain><item><author>jaketay</author><text>Our instances with ap-southeast-2 were out for around 12 hours. We used multiple availability zones and it didn&amp;#x27;t prevent downtime at all. It&amp;#x27;s very interesting the difference between AWS and Google outage responses. AWS is down for 12+ hours for some customers, force each customer to chase service level credits and sign off the postmortem with a nameless &amp;amp; faceless &amp;quot;-The AWS Team&amp;quot;. Not one person at AWS was willing to take responsibility for this failure.&lt;p&gt;Whereas Google was recently down for less than 18 minutes. A VP at Google sent an email advising all affected customers, posted continuous updates to their status page, sent a further apology email at the conclusion, posted a service credit exceeding the SLA to all customers in the zone (without forcing customers to chase this themselves with billing) and lastly wrote one of the most well written post mortems I&amp;#x27;ve ever seen. AWS has much to learn from Google about how to handle outages properly.</text></item></parent_chain><comment><author>Fenntrek</author><text>To be fair, that was a total outage of every region on the planet in google cloud platform&amp;#x27;s 18 minute outage case.&lt;p&gt;Compared to the sole region ap-southeast-2 (for you) in AWS&amp;#x27;s case. (though it was a longer outage).&lt;p&gt;That being said, I 1000% agree that Google cloud platform&amp;#x27;s response to fix issues, postmortems and actions to make things right are top notch.</text></comment>