« Topics
BillyH1,288 posts since 4 Jan 2003
You can't even access the pages, it just shows a warning page and doesn't let you progress further. For EVERY SINGLE SITE.

I'm amazed how quickly this is spreading across the net!
Asa3,422 posts since 22 Mar 2001 Administrator
Wouldn't like to be the developer who let that one go live. I can only imagine what the CEO on the phone to the team was saying...!
DVB Cornwall7,794 posts since 4 Dec 2003
The BBC website article about this has been updated and explains it ...


Google attributed the fault to human error and said most users were affected for about 40 minutes. "What happened? Very simply, human error," wrote Marissa Mayer, vice president, search products and user experience, on the Official Google Blog. The internet search engine works with stopbadware.org to ascertain which sites install malicious software on people's computers and merit a warning.

Stopbadware.org investigates consumer complaints to decide which sites are dangerous. The list of malevolent sites is regularly updated and handed to Google.

When Google updated the list on Saturday, it mistakenly flagged all sites as potentially dangerous. "We will carefully investigate this incident and put more robust file checks in place to prevent it from happening again," Ms Mayer wrote.
DVB Cornwall posted:
The BBC website article about this has been updated and explains it ...

It doesn't really though. It just says 'human error', it could have swapped that term for 'technical problem', "circumstances beyond our control' or 'unforeseen circumstances' and we would still have no more information as to why it happened.

Edit: In fact, the headline on the BBC artcle is 'Human error' hits Google search but the first paragraph says Google's search service has been hit by technical problems . Which one is it? It can't be both.
DVB Cornwall7,794 posts since 4 Dec 2003
No issue with the explanation afaic,

The technical problem was that users were blocked erroneously from moving on from their legitimate searches, this was caused by human error in implementing the stopbadaware file on Google's servers.

It seems a robust enough answer to me.