<?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/"
		>
<channel>
	<title>Comments on: Slashdot down for more than 5 hours</title>
	<atom:link href="http://royal.pingdom.com/2008/04/30/slashdot-down-for-more-than-5-hours/feed/" rel="self" type="application/rss+xml" />
	<link>http://royal.pingdom.com/2008/04/30/slashdot-down-for-more-than-5-hours/</link>
	<description>Ramblings and tech news from the Pingdom team</description>
	<lastBuildDate>Thu, 09 Feb 2012 15:34:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: Links List 5.16.08 &#124; IT's About Uptime - The StackSafe Blog</title>
		<link>http://royal.pingdom.com/2008/04/30/slashdot-down-for-more-than-5-hours/comment-page-1/#comment-160751</link>
		<dc:creator>Links List 5.16.08 &#124; IT's About Uptime - The StackSafe Blog</dc:creator>
		<pubDate>Fri, 16 May 2008 14:34:40 +0000</pubDate>
		<guid isPermaLink="false">http://royal.pingdom.com/?p=285#comment-160751</guid>
		<description>[...] CRN. There has been no official word on the cause for the downtime, but combined with the recent Slashdot downtime, tech readers are sure to be “fairly frazzled” at their online news [...]</description>
		<content:encoded><![CDATA[<p>[...] CRN. There has been no official word on the cause for the downtime, but combined with the recent Slashdot downtime, tech readers are sure to be “fairly frazzled” at their online news [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FRRO Blog &#187; Blog Archive &#187; Uptime, Downtime</title>
		<link>http://royal.pingdom.com/2008/04/30/slashdot-down-for-more-than-5-hours/comment-page-1/#comment-147603</link>
		<dc:creator>FRRO Blog &#187; Blog Archive &#187; Uptime, Downtime</dc:creator>
		<pubDate>Wed, 30 Apr 2008 18:20:16 +0000</pubDate>
		<guid isPermaLink="false">http://royal.pingdom.com/?p=285#comment-147603</guid>
		<description>[...] started reporting on this outage, as evidently seen from the reports published by The Register and Pingdom. The site has since been up and running already but not without invoking amusing, and insightful, [...]</description>
		<content:encoded><![CDATA[<p>[...] started reporting on this outage, as evidently seen from the reports published by The Register and Pingdom. The site has since been up and running already but not without invoking amusing, and insightful, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Slashdot was Down!</title>
		<link>http://royal.pingdom.com/2008/04/30/slashdot-down-for-more-than-5-hours/comment-page-1/#comment-147539</link>
		<dc:creator>Slashdot was Down!</dc:creator>
		<pubDate>Wed, 30 Apr 2008 17:04:53 +0000</pubDate>
		<guid isPermaLink="false">http://royal.pingdom.com/?p=285#comment-147539</guid>
		<description>[...] popular site for monitoring uptime of websites and server, Pingdom confirmed that Slashdot was unavailable for around 5 hours from 09:38 CET (03:38 US EST) till 14:48 CET [...]</description>
		<content:encoded><![CDATA[<p>[...] popular site for monitoring uptime of websites and server, Pingdom confirmed that Slashdot was unavailable for around 5 hours from 09:38 CET (03:38 US EST) till 14:48 CET [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

