<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
      xmlns:thr="http://purl.org/syndication/thread/1.0">
  <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php" />
  <link rel="self" type="application/atom+xml" href="http://www.readwriteweb.com/atom.xml" />
  <id>tag:www.readwriteweb.com,2011:/1/tag:www.readwriteweb.com,2009://1.13621-</id>
  <updated>2011-08-16T17:49:44Z</updated>
  <title>Comments for Human Error Causes Google&apos;s &apos;Epic Fail&apos;</title>
  
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.35-en</generator>
  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13621</id>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.readwriteweb.com/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=13621" title="Human Error Causes Google's 'Epic Fail'" />
    <published>2009-01-31T17:51:22Z</published>
    <updated>2009-02-01T13:55:53Z</updated>
    <title>Human Error Causes Google&apos;s &apos;Epic Fail&apos;</title>
    <summary>After what many were calling an epic fail by Google this morning, Marissa Mayer has published a post on the official Google blog apologizing for the inconvenience and dubbing the incident &apos;human error&apos;. This morning between 6:30 a.m. PST and 7:25 a.m. PST every Google search result displayed the notice &quot;This site may harm your...</summary>
    <author>
      <name>Lidija Davis</name>
      
    </author>
    
    <category term="News" />
    
    <content type="html" xml:lang="en" xml:base="http://www.readwriteweb.com/">
      <![CDATA[<p><img alt="google_logo_jan_09.jpg" src="http://www.readwriteweb.com/images/google_logo_jan_09.jpg" width="206" height="77" />After what many were calling an <a href="http://search.twitter.com/search?q=This+site+may+harm+your+computer">epic fail</a> by Google this morning, Marissa Mayer has published a <a href="http://googleblog.blogspot.com/2009/01/this-site-may-harm-your-computer-on.html">post</a> on the official Google blog apologizing for the inconvenience and dubbing the incident 'human error'.</p>

<p>This morning between 6:30 a.m. PST and 7:25 a.m. PST every Google search result displayed the notice "This site may harm your computer." Clicking on the link would take you to a <a href="http://www.google.com/support/websearch/bin/answer.py?answer=45449&topic=360&hl=en&ei=EGWESb6YMYaR-gbTu40o&sa=X&oi=malwarewarninglink&resnum=1&ct=help">support</a> page effectively blocking any access to all sites in the results.</p>]]>
      <![CDATA[<p>Monitoring malicious sites is pretty much part of the territory for Google, and shows they take malware on the Web seriously.  Google receives a list of malicious sites from <a href="http://stopbadware.org/">StopBadware.org</a> that is used to flag search results that may pose threats to users.  According to Mayer, the list is maintained by humans due to the research involved for each case.</p>

<p>"We periodically receive updates to that list and received one such update to release on the site this morning." Mayer said in the post, "unfortunately (and here's the human error), the URL of '/' was mistakenly checked in as a value to the file and '/' expands to all URLs."</p>

<p>Google reports the errors first appeared between 6:27 a.m. and 6:40 a.m. and began disappearing between 7:10 and 7:25 a.m.</p>

<p>If you're interested in learning more about Google's efforts when it comes to malware, take a look at their analysis of malware in <a href="http://www.usenix.org/events/hotbots07/tech/full_papers/provos/provos.pdf">The Ghost in the Browser</a> (PDF).</p>

<p><strong>Update: The StopBadware blog talks about the 'Google Glitch'</strong></p>

<p>StopBadware <a href="http://blog.stopbadware.org/2009/01/31/google-glitch-causes-confusion">says</a> that the glitch "led to a denial of service of our website, as millions of Google users attempted to visit our site for more information." </p>

<p>Additionally, StopBadware claims Mayer's statement about Google getting URLs from StopBadware is not accurate:  "Google generates its own list of badware URLs, and no data that we generate is supposed to affect the warnings in Google's search listings. We are attempting to work with Google to clarify their statement."</p>

<p><strong>Update 2: Google post updated</strong></p>

<p>Google updated its post to say that StopBadware does not in fact provide a list; instead, it helps Google to "come up with criteria for maintaining this list."</p>

<p>Matt Cutts <a href="http://twitter.com/mattcutts/status/1165042990">tweets</a> that the error was on Google's side</p>]]>
    </content>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13621-comment:125158</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13621" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php#c125158" />
    <title>Comment from Ken Bradley on 2009-02-02</title>
    <author>
        <name>Ken Bradley</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>Being an amateur I see from these reports something undefined has gone wrong with Google.  Sadly, you are all too darned fond of languages most decent honest people do not understand.  As a result, can someone advise one what has gone wrong since I seem to have got an irreparable or unremmovable virus by what seems to be the fault of Google.  My PC keeps seizing up after rebooting when it reaches the Desktop.  It began with the sudden appearance on the screen of a programme telling me to open it.  After I done this it seems to have got installed and jiggered my system.  Can someone help me out at this address.  Omaghhlad@Gmail.com  Thanking you in anticipation of some help.</p>

<p>Ken Brasdlet,  Northern Ireland</p>]]>
    </content>
    <published>2009-02-02T16:42:42Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13621-comment:125112</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13621" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php#c125112" />
    <title>Comment from Engago Team on 2009-02-02</title>
    <author>
        <name>Engago Team</name>
        <uri>http://www.leadsexplorer.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.leadsexplorer.com">
        <![CDATA[<p>Google management have felt how vulnerable Google can be.<br />
</p>]]>
    </content>
    <published>2009-02-02T08:22:26Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13621-comment:125095</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13621" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php#c125095" />
    <title>Comment from Ranjeet Walunj on 2009-02-01</title>
    <author>
        <name>Ranjeet Walunj</name>
        <uri>http://ranjeetwalunj.wordpress.com/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://ranjeetwalunj.wordpress.com/">
        <![CDATA[<p>its good on google's part on admitting the problem. </p>

<p>Effect of downsizing (right) people ? </p>]]>
    </content>
    <published>2009-02-02T05:12:12Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13621-comment:125056</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13621" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php#c125056" />
    <title>Comment from liiwaan on 2009-02-01</title>
    <author>
        <name>liiwaan</name>
        <uri>http://www.liiwaan.blogspot.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.liiwaan.blogspot.com">
        <![CDATA[<p>liiwaan</p>]]>
    </content>
    <published>2009-02-01T11:45:31Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13621-comment:125051</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13621" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php#c125051" />
    <title>Comment from Erwin Chua on 2009-02-01</title>
    <author>
        <name>Erwin Chua</name>
        <uri>http://winning2win.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://winning2win.com">
        <![CDATA[<p>Sorry for Google's error, but hey we're all human. </p>

<p>All the best!</p>

<p>Regards,</p>

<p>Erwin Chua<br />
IM Entrepreneur<br />
<a href="http://winning2win.com" rel="nofollow">http://winning2win.com</a></p>]]>
    </content>
    <published>2009-02-01T09:45:43Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13621-comment:125046</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13621" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php#c125046" />
    <title>Comment from Anrkist on 2009-01-31</title>
    <author>
        <name>Anrkist</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>I noticed this about 5 minutes before it was fixed, you know what? It was one of the worst 5 minutes of my life. I could not Google... I almost had to Yahoo!</p>]]>
    </content>
    <published>2009-02-01T06:05:41Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13621-comment:125045</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13621" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php#c125045" />
    <title>Comment from venkat on 2009-01-31</title>
    <author>
        <name>venkat</name>
        <uri>http://computersservicing.blogspot.com/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://computersservicing.blogspot.com/">
        <![CDATA[<p>How much this caused websites to loose traffic in that short span of time.</p>]]>
    </content>
    <published>2009-02-01T04:23:48Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13621-comment:125039</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13621" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php#c125039" />
    <title>Comment from JAB_au on 2009-01-31</title>
    <author>
        <name>JAB_au</name>
        <uri>http://www.webwhitenoise.com/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.webwhitenoise.com/">
        <![CDATA[<p>It's a PEBCAK error, that the best part about it. At least Google is willing to admit it: <a href="http://googleblog.blogspot.com/2009/01/this-site-may-harm-your-computer-on.html" rel="nofollow">http://googleblog.blogspot.com/2009/01/this-site-may-harm-your-computer-on.html</a></p>]]>
    </content>
    <published>2009-02-01T02:22:42Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13621-comment:125035</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13621" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php#c125035" />
    <title>Comment from John Franks on 2009-01-31</title>
    <author>
        <name>John Franks</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>Most companies enjoy “security” insofar as they haven’t been targeted yet, or suffered a human error resulting in a catastrophic exposure – something Google found out the hard way.  While various systems of security are important, no system can overcome laxity, ignorance, or deliberate intent to harm.  Necessary is a sustained culture and awareness; an efficient prism through which every activity is viewed from a security perspective prior to action.  <br />
Price Waterhouse Cooper and Carnegie-Mellon’s CyLab have recent surveys that show the senior executive class to be, basically, clueless regarding IT risk and its tie to overall enterprise (business) risk.  Data breaches and accidents are due to a lagging business culture – absent a new eCulture, breaches and accidents will - and continue to - increase.   Here, Google was fortunate, and hopefully its #1 asset, its reputation, will remain intact, but where I am CIO we cannot take chances.   Check your local library:  A book that is required reading is "I.T. WARS:  Managing the Business-Technology Weave in the New Millennium."  It also helps outside agencies understand your values and practices.<br />
The author, David Scott, has an interview that is a great exposure:  www.businessforum.com/DScott_02.html -  <br />
The book came to us as a tip from an intern who attended a course at University of Wisconsin, where the book is an MBA text.  In the realm of risk, unmanaged possibilities become probabilities –Read the book BEFORE you suffer a bad outcome or, worse, propagate one.</p>]]>
    </content>
    <published>2009-02-01T00:47:24Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13621-comment:125032</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13621" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php#c125032" />
    <title>Comment from MacroPhoto.NET on 2009-01-31</title>
    <author>
        <name>MacroPhoto.NET</name>
        <uri>http://www.macrophotos.net/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.macrophotos.net/">
        <![CDATA[<p>In a second I was thinking Google was censoring all the results. Just another validation on its power. Who would click on an unknown link given such warning from the almighty Google?</p>]]>
    </content>
    <published>2009-01-31T23:28:01Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13621-comment:125031</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13621" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php#c125031" />
    <title>Comment from fjpoblam on 2009-01-31</title>
    <author>
        <name>fjpoblam</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>I expected Go Ogle to say, "If you don't like it, don't use it." Go Ogle Search Beta. Lots of search engines out there. Don't put all yer searches in one basket.</p>]]>
    </content>
    <published>2009-01-31T21:57:01Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13621-comment:125027</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13621" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php#c125027" />
    <title>Comment from Jackie on 2009-01-31</title>
    <author>
        <name>Jackie</name>
        <uri>http://www.jackiesjungle.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.jackiesjungle.com">
        <![CDATA[<p>what's going on Google? You're slacking in your macking, slipping on your pimping. Mayer's mistake, slow emails forced to load basic HTML. come on guys.</p>]]>
    </content>
    <published>2009-01-31T20:41:15Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13621-comment:125020</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13621" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php#c125020" />
    <title>Comment from Euronomist on 2009-01-31</title>
    <author>
        <name>Euronomist</name>
        <uri>http://eurobserver.wordpress.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://eurobserver.wordpress.com">
        <![CDATA[<p>Is it not weird that every website's sublink indicated potential "harm for your computer"?</p>

<p>On the other hand, could Google publicly admit that they have been hacked?</p>]]>
    </content>
    <published>2009-01-31T19:02:40Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13621-comment:125019</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13621" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php#c125019" />
    <title>Comment from Bob Warfield on 2009-01-31</title>
    <author>
        <name>Bob Warfield</name>
        <uri>http://smoothspan.wordpress.com/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://smoothspan.wordpress.com/">
        <![CDATA[<p>It's an interesting tale, but the question of what exactly the human error was is even more interesting.  More on my blog:</p>

<p><a href="http://smoothspan.wordpress.com/2009/01/31/balancing-process-and-agility-googles-cautionary-tale/" rel="nofollow">http://smoothspan.wordpress.com/2009/01/31/balancing-process-and-agility-googles-cautionary-tale/</a></p>]]>
    </content>
    <published>2009-01-31T18:46:58Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13621-comment:125018</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13621" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php#c125018" />
    <title>Comment from Surendra Singhi on 2009-01-31</title>
    <author>
        <name>Surendra Singhi</name>
        <uri>http://blog.kreeti.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://blog.kreeti.com">
        <![CDATA[<p>I saw this happening, and was wondering what was wrong with google. If I was trying to go to the site by copying, pasting the url, Firefox wasn't still letting me in.</p>]]>
    </content>
    <published>2009-01-31T18:46:45Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.13621-comment:125017</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.13621" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/human_error_causes_googles_epi.php#c125017" />
    <title>Comment from Lenny Rachitksy on 2009-01-31</title>
    <author>
        <name>Lenny Rachitksy</name>
        <uri>http://www.transparentuptime.com/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.transparentuptime.com/">
        <![CDATA[<p>Glad to see the clear and human explanation of what went wrong so quickly after the event, from none other then Melissa Mayer.</p>]]>
    </content>
    <published>2009-01-31T18:19:55Z</published>
  </entry>

</feed>
