<?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: TypePad Tweets Its Downtime</title>
	<atom:link href="http://www.datacenterknowledge.com/archives/2008/10/03/typepad-tweets-its-downtime/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.datacenterknowledge.com/archives/2008/10/03/typepad-tweets-its-downtime/</link>
	<description>News and analysis about data centers, cloud computing, managed hosting and disaster recovery</description>
	<lastBuildDate>Mon, 13 Feb 2012 17:24:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Augie</title>
		<link>http://www.datacenterknowledge.com/archives/2008/10/03/typepad-tweets-its-downtime/comment-page-1/#comment-979</link>
		<dc:creator>Augie</dc:creator>
		<pubDate>Sat, 04 Oct 2008 22:16:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.datacenterknowledge.com/?p=3578#comment-979</guid>
		<description>At Sonic.net we have been using Twitter to communicate outages and other bits of information with our customers for about the last six months.

We separated our communication into two Twitter accounts: @sonicnet for direct communication with customers (tracking certain key-words like &#039;sonic.net&#039; helps) and @sonicnet_status for only the really important messages on our current status.

The experience has been very positive and customers are always pleasantly surprised to find us on Twitter and to find how responsive we are with it.</description>
		<content:encoded><![CDATA[<p>At Sonic.net we have been using Twitter to communicate outages and other bits of information with our customers for about the last six months.</p>
<p>We separated our communication into two Twitter accounts: @sonicnet for direct communication with customers (tracking certain key-words like &#8216;sonic.net&#8217; helps) and @sonicnet_status for only the really important messages on our current status.</p>
<p>The experience has been very positive and customers are always pleasantly surprised to find us on Twitter and to find how responsive we are with it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

