<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Amazon Does the Right Thing</title>
	<atom:link href="http://gigaom.com/2008/07/26/amazon-does-the-right-thing/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2008/07/26/amazon-does-the-right-thing/</link>
	<description></description>
	<lastBuildDate>Sat, 25 May 2013 10:48:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Paul Carney</title>
		<link>http://gigaom.com/2008/07/26/amazon-does-the-right-thing/#comment-74622</link>
		<dc:creator><![CDATA[Paul Carney]]></dc:creator>
		<pubDate>Sun, 27 Jul 2008 15:09:49 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.wordpress.com/?p=3018#comment-74622</guid>
		<description><![CDATA[I don&#039;t agree that a &quot;sorry&quot; was necessary. They outlined in very specific detail as to what happened and how they are going to try (operative word) to avoid it in the future. That is what I would expect of a business that I depend on at this level.

As for the details being &quot;technical&quot; and not &quot;customer-facing&quot;, this is what we need. The issue was not a business issue, but a very technical one. This explanation shows that they figured it out and solved it. The post was not meant to be a business post.

I have experienced similar types of outages from our hosting provider (where we have 8 servers that operate 24/7 for our 15,000 clients), so I know how important an outage is. Amazon&#039;s explanation was spot-on, necessary and accepted. No need to say &quot;sorry&quot;, but more importantly, &quot;here is how we are going to try to avoid this in the future&quot;.]]></description>
		<content:encoded><![CDATA[<p>I don&#8217;t agree that a &#8220;sorry&#8221; was necessary. They outlined in very specific detail as to what happened and how they are going to try (operative word) to avoid it in the future. That is what I would expect of a business that I depend on at this level.</p>
<p>As for the details being &#8220;technical&#8221; and not &#8220;customer-facing&#8221;, this is what we need. The issue was not a business issue, but a very technical one. This explanation shows that they figured it out and solved it. The post was not meant to be a business post.</p>
<p>I have experienced similar types of outages from our hosting provider (where we have 8 servers that operate 24/7 for our 15,000 clients), so I know how important an outage is. Amazon&#8217;s explanation was spot-on, necessary and accepted. No need to say &#8220;sorry&#8221;, but more importantly, &#8220;here is how we are going to try to avoid this in the future&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam Denby</title>
		<link>http://gigaom.com/2008/07/26/amazon-does-the-right-thing/#comment-74621</link>
		<dc:creator><![CDATA[Sam Denby]]></dc:creator>
		<pubDate>Sat, 26 Jul 2008 20:11:36 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.wordpress.com/?p=3018#comment-74621</guid>
		<description><![CDATA[I am a user of S3 and I have many years experience with problem and crisis management in large data centers. Amazon have posted a model report which explains what happened, looks for root causes and identifies actions in place to tackle them. I agree that saying sorry would have been good, but I think this was posted by engineers focused on the problem, rather than customer-facing people.]]></description>
		<content:encoded><![CDATA[<p>I am a user of S3 and I have many years experience with problem and crisis management in large data centers. Amazon have posted a model report which explains what happened, looks for root causes and identifies actions in place to tackle them. I agree that saying sorry would have been good, but I think this was posted by engineers focused on the problem, rather than customer-facing people.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Gunderloy</title>
		<link>http://gigaom.com/2008/07/26/amazon-does-the-right-thing/#comment-74620</link>
		<dc:creator><![CDATA[Mike Gunderloy]]></dc:creator>
		<pubDate>Sat, 26 Jul 2008 19:02:28 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.wordpress.com/?p=3018#comment-74620</guid>
		<description><![CDATA[@Matt: If you check the times involved, you&#039;ll see that our coverage of the refund process was posted before they made the policy exception for this outage.

As for the apology, when a service with a 99.9% SLA misses badly, I think it&#039;s only good form to tell your customers that you&#039;re sorry about the downtime. YMMV, I guess.]]></description>
		<content:encoded><![CDATA[<p>@Matt: If you check the times involved, you&#8217;ll see that our coverage of the refund process was posted before they made the policy exception for this outage.</p>
<p>As for the apology, when a service with a 99.9% SLA misses badly, I think it&#8217;s only good form to tell your customers that you&#8217;re sorry about the downtime. YMMV, I guess.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Hussein Platte</title>
		<link>http://gigaom.com/2008/07/26/amazon-does-the-right-thing/#comment-74619</link>
		<dc:creator><![CDATA[Matt Hussein Platte]]></dc:creator>
		<pubDate>Sat, 26 Jul 2008 18:55:59 +0000</pubDate>
		<guid isPermaLink="false">http://webworkerdaily.wordpress.com/?p=3018#comment-74619</guid>
		<description><![CDATA[Why should they be sorry about anything?  More to the point, why do you think this is a situation that requires an apology?  Early on you were beating up on Amazon because of their cynical fill-out-the-forms attitude regarding the refund.  Now that you&#039;ve discovered your error WRT the refund, it seems that the apology might best be turned around.]]></description>
		<content:encoded><![CDATA[<p>Why should they be sorry about anything?  More to the point, why do you think this is a situation that requires an apology?  Early on you were beating up on Amazon because of their cynical fill-out-the-forms attitude regarding the refund.  Now that you&#8217;ve discovered your error WRT the refund, it seems that the apology might best be turned around.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
