<?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>trendyreel.com &#187; Google</title>
	<atom:link href="http://trendyreel.com/category/google/feed/" rel="self" type="application/rss+xml" />
	<link>http://trendyreel.com</link>
	<description></description>
	<lastBuildDate>Tue, 31 Jan 2012 21:42:28 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>The Day Google Crashed</title>
		<link>http://trendyreel.com/2009/05/the-day-google-servers-crash/</link>
		<comments>http://trendyreel.com/2009/05/the-day-google-servers-crash/#comments</comments>
		<pubDate>Thu, 14 May 2009 20:45:24 +0000</pubDate>
		<dc:creator>Trendy</dc:creator>
				<category><![CDATA[Google]]></category>
		<category><![CDATA[Trendy Bits]]></category>

		<guid isPermaLink="false">http://trendyreel.com/?p=355</guid>
		<description><![CDATA[If you were one of the fortunates who tried to access a aray of Google apps around 9 a.m. est you then joined thousands or others who couldn&#8217;t access anything Google. From Youtube to Gmail the server crash resulted in either very slow or no service at all to any Google application.  Although some are saying it only affected certain U.S. cities, I think the crash sent all Google apps everywhere out of whack. This mornings down time also was a revelation that mostly half of the websites on the internet use some kind of Google app. First hand account shows that this morning for about a hour I could not access any website that used Google Analytics or Gmail and I am located in Washington D.C. zdnet.com&#8216;s Google Fail Whale So what was the cause of this lasp? Google blames it on a traffic jam due to a error in their system. Imagine if you were trying to fly from New York to San Francisco, but your plane was routed through an airport in Asia. And a bunch of other planes were sent that way too, so your flight was backed up and your journey took much longer than expected. That&#8217;s basically what happened to some of our users today for about an hour, starting at 7:48 am Pacific time. An error in one of our systems caused us to direct some of our web traffic through Asia, which created a traffic jam. As a result, about 14% of our users experienced slow services or even interruptions. We&#8217;ve been working hard to make our services ultrafast and &#8220;always on,&#8221; so it&#8217;s especially embarrassing when a glitch like this one happens. We&#8217;re very sorry that it happened, and you can be sure that we&#8217;ll be working even harder to make sure that a similar problem won&#8217;t happen again. All planes are back on schedule now. Google Blog I&#8217;m sure today was a good day over at Yahoo!]]></description>
			<content:encoded><![CDATA[<p>If you were one of the fortunates who tried to access a aray of Google apps around 9 a.m. est you then joined thousands or others who couldn&#8217;t access anything Google. From Youtube to Gmail the server crash resulted in either very slow or no service at all to any Google application.  Although some are saying it only affected certain U.S. cities, I think the crash sent all Google apps everywhere out of whack. This mornings down time also was a revelation that mostly half of the websites on the internet use some kind of Google app. First hand account shows that this morning for about a hour I could not access any website that used Google Analytics or Gmail and I am located in Washington D.C.</p>
<p><a href="http://blogs.zdnet.com/BTL/?p=18064" target="_blank">zdnet.com</a>&#8216;s Google Fail Whale</p>
<p><img class="alignnone size-full wp-image-356" title="google_failwhale" src="http://trendyreel.com/wp-content/uploads/2009/05/google_failwhale.jpg" alt="google_failwhale" width="640" height="346" /></p>
<p>So what was the cause of this lasp? Google blames it on a traffic jam due to a error in their system.</p>
<blockquote><p><span style="color: #800000;">Imagine if you were trying to fly from New York to San Francisco, but your plane was routed through an airport in Asia. And a bunch of other planes were sent that way too, so your flight was backed up and your journey took much longer than expected. That&#8217;s basically what happened to some of our users today for about an hour, starting at 7:48 am Pacific time.</span></p>
<p><span style="color: #800000;">An error in one of our systems caused us to direct some of our web traffic through Asia, which created a traffic jam. As a result, about 14% of our users experienced slow services or even interruptions. We&#8217;ve been working hard to make our services ultrafast and &#8220;always on,&#8221; so it&#8217;s especially embarrassing when a glitch like this one happens. We&#8217;re very sorry that it happened, and you can be sure that we&#8217;ll be working even harder to make sure that a similar problem won&#8217;t happen again. All planes are back on schedule now.</span></p></blockquote>
<p><a href="http://googleblog.blogspot.com/2009/05/this-is-your-pilot-speaking-now-about.html" target="_blank">Google Blog</a></p>
<p>I&#8217;m sure today was a good day over at Yahoo!</p>
<iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Ftrendyreel.com%2F2009%2F05%2Fthe-day-google-servers-crash%2F&amp;layout=standard&amp;show_faces=true&amp;width=450&amp;action=like&amp;colorscheme=light&amp;height=80" scrolling="no" frameborder="0" style="border:none; overflow:hidden; width:450px; height:80px;" allowTransparency="true"></iframe>]]></content:encoded>
			<wfw:commentRss>http://trendyreel.com/2009/05/the-day-google-servers-crash/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

