A while back, we were using zoneedit.com to keep track of changing DSL addresses at some of our offices. We had a little daemon running that checked the external IP every 15 minutes and shoulder-tapped zoneedit if there was a change. It started failing after a while, and we discovered the external server we were using to query our IP was wigging out.
So we googled for some alternatives. None were much good. So we wrote two of our own, one hosted at the company's main site and one at a free Google App Engine site. That was a good move, as both mostly outperform the various freebies out there.
Along the way, I wrote a little script to test a bunch of alternative IP sources. Just for fun, I added a version of your Google query to the mix, along with the OP's site, and just reran it, with the following results:
The Google hack got the wrong IP. I assume the reason is that script is downloading the page and parsing out the first thing that looks like an IP address it comes across, but the part of the Google response that shows your IP bold and clear occurs further down in the result. So, it could be made to work, but would require a less trivial parse.
BTW, FWIW, www.[cynwoody's company].com is hosted at FutureQuest. Attaboy FutureQuest!
And internetaddress.me did best of all, responding in only 74 ms (I'm located in the Boston area), but one has to wonder what popularity will do.