A Disturbance in the Force (Updated)

Is it my imagination or is there something wrong with Google this morning? I’m not having problems with other search engines.

Update

I see I wasn’t imagining things:

We’re not quite sure what’s going on, but a couple of minutes ago any search result from Google started being flagged as malware with a message stating “This site may harm your computer”. Including Google’s own websites as you can see above.

Twitter is abuzz with people reporting the massive error (also look for tags #googmayharm or #googmayhem), and it’s clear that this is happening around the world. Apparently, it’s happening with any browser on any platform too.

Google explains:

If you did a Google search between 6:30 a.m. PST and 7:25 a.m. PST this morning, you likely saw that the message “This site may harm your computer” accompanied each and every search result. This was clearly an error, and we are very sorry for the inconvenience caused to our users.

What happened? Very simply, human error. Google flags search results with the message “This site may harm your computer” if the site is known to install malicious software in the background or otherwise surreptitiously. We do this to protect our users against visiting sites that could harm their computers. We maintain a list of such sites through both manual and automated methods. We work with a non-profit called StopBadware.org to come up with criteria for maintaining this list, and to provide simple processes for webmasters to remove their site from the list.

We periodically update that list and released one such update to the site this morning. 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. Fortunately, our on-call site reliability team found the problem quickly and reverted the file. Since we push these updates in a staggered and rolling fashion, the errors began appearing between 6:27 a.m. and 6:40 a.m. and began disappearing between 7:10 and 7:25 a.m., so the duration of the problem for any particular user was approximately 40 minutes.

Frankly, I’m puzzled by this. Human error, of course, I can understand. However, isn’t best practice supposed to be to separate development from operations?

1 comment… add one

Leave a Comment