by Christian Scholz on February 14, 2009
Update 2: I have written a little summary of what on a technical level has happened today regarding this issue. Read it here.
Update: I apologize to Google as it seems not to be their fault but OpenDNS’ fault. If are using OpenDNS and you have shortcuts enabled then Google seems to be unreachable because of that. Disabling shortcuts in your dashboard in OpenDNS will most likely make Google work again.
So the text below is outdated now.
After Google marked all search results as malware not too long ago, they are again in trouble.
While trying to reach www.google.de or www.google.com I receive an error that the connection is refused. A quick test in a shell confirms that indeed google.de is not responding on port 80. DNS is working (that means if it’s pointing to a Google server and not somewhere else).
On Twitter you can also see people complaining about it so it’s not just me.
From another server of mine in a different network (not T-Home as I am now) I can reach Google though but it’s also a different IP address it resolves to (22.214.171.124 is working, 126.96.36.199 is not).
So once again one gets reminded how important Google has become and how problematic it is if it’s not reachable. Search might be the least problematic thing as there are at least some alternatives out there but think of all the other services Google wants you to rely on them.