The IP addresses logged in the stats database are internal addresses. There's probably a remote proxy messing about. Try parsing the X-FORWARDED-FOR header when it's available.
Judging from the logs, this was probably introduced on 2011-10-12. Who will hunt down the culprit?
The forwarded-for trick appears to have done it. The database is populated by IP addresses, as well as corresponding geodata again.
I've purged the private address from the records: