<?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/"
	
	xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>Technosailor.com &#187; fail whale</title>
	<atom:link href="http://technosailor.com/tag/fail-whale/feed/" rel="self" type="application/rss+xml" />
	<link>http://technosailor.com</link>
	<description>Business and Technology with Common Sense</description>
	<lastBuildDate>Wed, 08 Feb 2012 17:54:00 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4-alpha-19888</generator>
		<item>
		<title>99.96% Uptime is Bogus Marketing</title>
		<link>http://technosailor.com/2008/09/03/9996-uptime-is-bogus-marketing/</link>
		<comments>http://technosailor.com/2008/09/03/9996-uptime-is-bogus-marketing/#comments</comments>
		<pubDate>Thu, 04 Sep 2008 00:26:33 +0000</pubDate>
		<dc:creator>Aaron</dc:creator>
				<category><![CDATA[Aaron Brazell]]></category>
		<category><![CDATA[biz stone]]></category>
		<category><![CDATA[dnc08]]></category>
		<category><![CDATA[fail whale]]></category>
		<category><![CDATA[infrastructure]]></category>
		<category><![CDATA[it]]></category>
		<category><![CDATA[rnc08]]></category>
		<category><![CDATA[summize]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://technosailor.com/?p=4338</guid>
		<description><![CDATA[Reliability Update Twitter has been making great progress in terms of uptime and reliability. Fail Whale sightings are far less frequent these days thanks to our efforts but we still have a long journey ahead. Last month we saw 99.88% &#8230; <a href="http://technosailor.com/2008/09/03/9996-uptime-is-bogus-marketing/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<blockquote><p>Reliability Update</p>
<p>Twitter has been making great progress in terms of uptime and<br />
reliability. Fail Whale sightings are far less frequent these<br />
days thanks to our efforts but we still have a long journey<br />
ahead. Last month we saw 99.88% uptime and so far this month we<br />
are at 99.96%. Our engineering and operations teams have been<br />
taking a very methodical approach to improving Twitter. We&#8217;re<br />
using the word &#8220;craftsmanship&#8221; to characterize our work here at<br />
the office. Reliability and dependability continue to be top on<br />
or list of key goals.</p></blockquote>
<p>The above passage is from an email from Biz Stone at <a href="http://twitter.com">Twitter</a> today. After a horrid June, things could only go up at Twitter HQ. Fortunately, it looked like they got serious about the uptime issues they had their and things <em>have</em> been better.</p>
<p>In the meantime, they purchased the super reliable and speedy Summize and branded it with Twitter branding at <a href="http://search.twitter.com">search.twitter.com</a>.</p>
<p>This could only be a good thing, right?</p>
<p>Well, you&#8217;d think. Except the purchase of the super speedy and efficient Summize has only driven the tool into the pond. To be fair, it&#8217;s not horrible, but it suffers from the same weaknesses that Twitter does.</p>
<p>That is, it can&#8217;t keep up.</p>
<p>As an example, I&#8217;ve been following <a href="http://search.twitter.com/search?q=%23dnc08">#dnc08</a> and <a href="http://search.twitter.com/search?q=%23rnc08">#rnc08</a> searches on Summize to watch what people are saying about the political conventions. During the high traffic tweet windows during the evenings of the conventions, Twitter is reliable. That is, they are reliably late. Usually 1-2 hours behind the actual tweet stream.</p>
<p>This is completely unacceptable, and it is complete spin, I guess in the spirit of the conventions, for Biz to tout 99.96% uptime.</p>
<p>Let me be clear, when things are slow and not performing up to standard, you cannot claim 99.96% uptime. Technically you can. Uptime is technically defined by if the web server serves a 404 Page not Found (or Twitter <a href="http://buzzfeed.com/buth/fail-whale">Fail Whale</a> in their case) or a 200 Page found status code.</p>
<p>But from a common sense user experience, this is not uptime. And to claim so is disingenuous.</p>
<p>I appreciate the efforts Twitter has put into improving, but why are we fighting the ability to use the tools during high-demand times. In essence, that makes the tools completely useless.</p>
<p>I look forward to better results, but my skepticism remains in place about Twitter. They do not have the staying power to make it.</p>
<p>I have been on a 3 month hiatus on Twitter blogging. I have refused to blog about it, but there&#8217;s another post that has been in the back of my mind for some time. What happens when companies and businesses trying to use Twitter as a marketing and communications tool cannot. What happens when your brand relies on the communication lines and those communications lines dying?</p>
<p>Another day, another post. For today, the spin needs to be exposed.</p>
]]></content:encoded>
			<wfw:commentRss>http://technosailor.com/2008/09/03/9996-uptime-is-bogus-marketing/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
	
	</item>
	</channel>
</rss>

