<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>EveryJoe &#187; S3</title>
	<atom:link href="http://www.everyjoe.com/tag/s3/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.everyjoe.com</link>
	<description>Sports News - Tech Reviews - Entertainment - Life Tips for EveryJoe</description>
	<lastBuildDate>Wed, 09 Dec 2009 22:11:21 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Amazon Says S3 Outage is Internal</title>
		<link>http://www.everyjoe.com/articles/amazon-says-s3-outage-is-internal-608/</link>
		<comments>http://www.everyjoe.com/articles/amazon-says-s3-outage-is-internal-608/#comments</comments>
		<pubDate>Sun, 20 Jul 2008 21:04:27 +0000</pubDate>
		<dc:creator>Jayvee Fernandez</dc:creator>
				<category><![CDATA[Computers]]></category>
		<category><![CDATA[S3]]></category>

		<guid isPermaLink="false">http://www.techsideup.com/amazon-says-s3-outage-is-internal/</guid>
		<description><![CDATA[
Twitter avatars, blog images, and SmugMug photos are all vanishing because Amazon S3 is down.
Hackers? Alas, Amazon probably can&#8217;t put the blame on them. They say the problem is internal:
10:32 AM PDT A quick update that we believe this is an issue with the communication between several Amazon S3 internal components. We do not have an ETA at this time but will continue to keep you updated.
They say they&#8217;re coming close to a fix, though:
1:38 PM PDT At this point, we are accelerating progress on restoring internal communication as all signs continue to look good. 
This just goes to show [...]<p>Post from: <a href="http://www.everyjoe.com">EveryJoe</a></p>
<p><a href="http://www.everyjoe.com/articles/amazon-says-s3-outage-is-internal-608/">Amazon Says S3 Outage is Internal</a></p>
]]></description>
			<content:encoded><![CDATA[<div align="center"><img src="http://www.everyjoe.com/files/608/2008/07/aws.gif" alt="Amazon Web Services" border="0" /></div>
<p>Twitter avatars, <a href="http://www.centernetworks.com/amazon-s3-down-july-2008">blog images</a>, and <a href="http://smugmug.wordpress.com/2008/07/20/amazon-s3-outage-causes-smugmug-outage/">SmugMug photos</a> are all vanishing because Amazon S3 is <a href="http://news.cnet.com/8301-1023_3-9995301-93.html">down</a>.</p>
<p>Hackers? Alas, Amazon probably <a href="http://status.aws.amazon.com/">can&#8217;t</a> put the blame on them. They say the problem is internal:<span id="more-49998"></span></p>
<blockquote><p><strong>10:32 AM</strong> PDT A quick update that we believe this is an issue with the communication between several Amazon S3 internal components. We do not have an ETA at this time but will continue to keep you updated.</p></blockquote>
<p>They say they&#8217;re coming close to a fix, though:</p>
<blockquote><p><strong>1:38 PM PDT</strong> At this point, we are accelerating progress on restoring internal communication as all signs continue to look good. </p></blockquote>
<p>This just goes to show that, even with a giant like Amazon, things can go awry without any external intervention.</p>
<p>Of course, there&#8217;s always the other possibility: Amazon covering up an S3 security vulnerability by attributing the outage to internal communication problems. Then again, we must never assume malice when stupidity will suffice.</p>
<p>Post from: <a href="http://www.everyjoe.com">EveryJoe</a></p>
<p><a href="http://www.everyjoe.com/articles/amazon-says-s3-outage-is-internal-608/">Amazon Says S3 Outage is Internal</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.everyjoe.com/articles/amazon-says-s3-outage-is-internal-608/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>