<?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>Cog Tree &#187; error</title>
	<atom:link href="http://blog.cogtree.com/tag/error/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.cogtree.com</link>
	<description>Spend less time reading the news, and more time acting on it!</description>
	<lastBuildDate>Thu, 25 Feb 2010 05:01:05 +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>Sorry! Parse.ly is down for some&#8230;</title>
		<link>http://blog.cogtree.com/2009/10/sorry-parse-ly-is-down-for-some/</link>
		<comments>http://blog.cogtree.com/2009/10/sorry-parse-ly-is-down-for-some/#comments</comments>
		<pubDate>Mon, 26 Oct 2009 05:03:34 +0000</pubDate>
		<dc:creator>Sachin</dc:creator>
				<category><![CDATA[Parse.ly]]></category>
		<category><![CDATA[Sorry]]></category>
		<category><![CDATA[error]]></category>

		<guid isPermaLink="false">http://blog.cogtree.com/?p=249</guid>
		<description><![CDATA[
Sorry Parse.ly users, but one of our servers unexpectedly failed on us. As a result, we took Parse.ly down.  We&#8217;re working hard now roll our backups over to our failsafe and get Parse.ly back up and running.  We should back to normal in a few hours.  We&#8217;ll update this post when we&#8217;re all good to [...]]]></description>
			<content:encoded><![CDATA[<p><img class="aligncenter size-full wp-image-250" title="Sorry!" src="http://blog.cogtree.com/wp-content/uploads/2009/10/161457552_bc2518f37f.jpg" alt="Sorry!" width="500" height="375" /></p>
<p>Sorry Parse.ly users, but one of our servers unexpectedly failed on us. As a result, we took Parse.ly down.  We&#8217;re working hard now roll our backups over to our failsafe and get Parse.ly back up and running.  We should back to normal in a few hours.  We&#8217;ll update this post when we&#8217;re all good to go.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.cogtree.com/2009/10/sorry-parse-ly-is-down-for-some/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

