It’s because the IP you’re coming from which may in fact be a proxy has something whacking their servers. If you are an Enterprise of 300,000+ people it could be anyone of them constantly requesting somethign from google too quickly which does in fact make it look like a virus. You need to track down the offending devices in your network and get them to stop

In the past people used WPG to scrape serps or xenu or other similar progs to snatch google data. The thing is that a determined scraper would be a little more sophisitcanted and use a tool that spoofed user agents and used proxified IP’s so I dont quite get where they fet off on what for me is prolly related to some general IP based abuse capture.

Take BT or NTL or any big UK ISP as an example and you’ll notice that they pretty much randomise IP ranges for their users. I think google might have a little aspect of their scripts that identifies say the st 3 aspects of the IP adress eg 192.168.2. and then wildcards everything else. So, any user with that IP will get hammered for a short period. This is because a user on the same IP range could have been abusing the resource so they decide to take action. Yet the reality is that they penalise everyone as a result, or at least a huge number of people, which is kinda sucky and bad for them too as it just weakens the user experience and makes them think damn you google. As for that spyware virus message that’s even worse cos if anything it’ll just alarm users into thinking they have a problem…”ooh Google told me I might have a virus…it must be true ” kinda thinking.