<?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>downrightnow blog &#187; LiveJournal</title>
	<atom:link href="http://blog.downrightnow.com/category/outages/livejournal/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.downrightnow.com</link>
	<description>downrightnow monitors the status of popular web services, combining user reports and official updates to tell you when there&#039;s an outage or service issue.</description>
	<lastBuildDate>Thu, 31 Mar 2011 04:07:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Twitter, LiveJournal, Facebook Trouble: A Perfect Storm &#8211; August 6, 2009</title>
		<link>http://blog.downrightnow.com/2009/08/twitter-livejournal-facebook-down/</link>
		<comments>http://blog.downrightnow.com/2009/08/twitter-livejournal-facebook-down/#comments</comments>
		<pubDate>Thu, 06 Aug 2009 17:12:46 +0000</pubDate>
		<dc:creator>downrightnow</dc:creator>
				<category><![CDATA[Facebook]]></category>
		<category><![CDATA[LiveJournal]]></category>
		<category><![CDATA[Outages]]></category>
		<category><![CDATA[Twitter]]></category>

		<guid isPermaLink="false">http://blog.downrightnow.com/?p=39</guid>
		<description><![CDATA[We&#8217;ve noticed an unusually high number of service disruptions today, all happening at around the same time. First to fall was LiveJournal, which began reporting database problems on the LiveJournal Status page at 8:58 am ET; downrightnow immediately picked up the announcement.  Kudos to LJ for acknowledging the issue and keeping users informed. User reports [...]]]></description>
			<content:encoded><![CDATA[<p>We&#8217;ve noticed an unusually high number of service disruptions today, all happening at around the same time.</p>
<p>First to fall was <a href="http://downrightnow.com/livejournal">LiveJournal</a>, which began reporting database problems on the <a href="http://status.livejournal.org/" target="_blank">LiveJournal Status</a> page at 8:58 am ET; downrightnow immediately picked up the announcement.  Kudos to LJ for acknowledging the issue and keeping users informed.</p>
<p><span id="more-39"></span></p>
<p><img class="aligncenter size-full wp-image-44" title="LiveJournal Status" src="http://blog.downrightnow.com/wp-content/uploads/2009/08/livejournal-status.png" alt="LiveJournal Status" width="400" height="102" /></p>
<p>User reports of <a href="http://downrightnow.com/twitter">Twitter</a> trouble started at 9:07 am and downrightnow immediately reported a possible outage.  By 9:36 am, we were receiving even more reports and upgraded our evaluation to a likely service disruption. At 9:40 am, <a href="http://www.techcrunch.com/2009/08/06/serious-twitter-outage-ongoing/" target="_blank">TechCrunch</a> picked up the story.  It wasn&#8217;t until approximately 9:55 am that Twitter posted its <a href="http://status.twitter.com/post/157160617/site-is-down" target="_blank">first official announcement</a>, saying:</p>
<blockquote><p><em>We are determining the cause and will provide an update shortly.</em></p></blockquote>
<p><a href="http://status.twitter.com/post/157191978/ongoing-denial-of-service-attack" target="_blank">Another official update</a> followed at around 11:00 am that broke the news: Twitter had identified a Denial of Service (DoS) attack.  We wish Twitter good luck in dealing with the attack and their announcements are definitely appreciated.  For those keeping score, we will also point out that downrightnow users were notified of potential service trouble 30 minutes before it was widely reported by TechCrunch, and 45 minutes before Twitter itself acknowledged the issue.  Thanks to everyone who submitted a report!</p>
<p><img class="aligncenter size-full wp-image-45" title="Twitter Status" src="http://blog.downrightnow.com/wp-content/uploads/2009/08/twitter-status.png" alt="Twitter Status" width="400" height="95" /></p>
<p>Finally, our outage-weary users also began complaining of trouble at <a href="http://downrightnow.com/facebook">Facebook</a> by 10:35 am.  We reported a temporary service disruption and have continued to monitor the social network&#8217;s status as intermittent user reports have continued to flow in, both from downrightnow users and on Twitter (which now appears mostly recovered).  Unfortunately, Facebook doesn&#8217;t provide official announcements or updates on service issues, so its users are left in the dark (those who aren&#8217;t downrightnow users, that is).  We hope Facebook will follow the lead of other services such as LiveJournal and Twitter who communicate with their users during service trouble.  Until then, we&#8217;ll continue to keep you updated with the best information available.</p>
<p>As always, you can keep an eye on these services and others all in one place at <a href="http://downrightnow.com/">downrightnow.com</a>.</p>
<p><strong>Update:</strong> According to <a href="http://mashable.com/2009/08/06/facebook-problems/" target="_blank">Mashable</a>,  Facebook and LiveJournal have also confirmed that <a href="http://en.wikipedia.org/wiki/Denial-of-service_attack" target="_blank">DDoS attacks</a> are contributing to their service disruptions today.  Though it&#8217;s not clear whether the same attackers are behind all 3 incidents, the timing does raise suspicion.  Rumors that downrightnow commissioned the onslaught in order to boost traffic are entirely unsubstantiated. :)</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.downrightnow.com/2009/08/twitter-livejournal-facebook-down/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>

