IP geo-location acting weird, showing IPs on the moon?

Hey everyone,

I'm scratching my head over here with our IP Lookup Tool - Geo-locate Any IP Address & Get Details. It's usually a reliable workhorse, providing pretty accurate IP location data for our users, but lately, it seems to have developed a severe case of wanderlust. My software is now confidently telling me that valid IPs are chilling in places they absolutely shouldn't be!

The problem is pretty wild: the tool is suddenly giving wildly inaccurate IP geo-location results. I'm talking about a US IP address supposedly residing in Antarctica, a German IP floating around in the middle of the Pacific Ocean, and for a good laugh, it even pinpointed one IP as being somewhere near the Sea of Tranquility. Yes, the moon. I'm starting to think my server is secretly a NASA project.

Here's what I've tried to debug this cosmic misadventure:

• Verified API keys and credits for our geo-location provider. Everything looks green there.
• Checked for recent database updates or schema changes on our end and with the provider's documentation. Nothing obvious.
• Tested with various known IP ranges (local, international, mobile, VPNs). All of them are getting bizarre results.
• Inspected network configurations and server logs for any connectivity issues to the geo-location service. No red flags.
• Double-checked frontend parsing logic for displaying coordinates. The coordinates themselves are coming back weird, so it's not just a display issue.

Normally, our tool provides precise city and country data, but now it's returning coordinates that are miles — or light-years — off the mark, or completely nonsensical region names. It's like the geo-location service is having an existential crisis.

Here’s a snippet from what our backend is spitting out for a fairly standard IP (changed for privacy, of course):

{
  "ip": "192.168.1.100",
  "country_code": "XX",
  "country_name": "Imaginary Land",
  "region_name": "Quadrant 4, Sector 7G",
  "city": "Nowhereville",
  "latitude": "-89.9999",
  "longitude": "179.9999",
  "timezone": "UTC+00:00",
  "provider": "Lunar Corp."
}

Has anyone else encountered such bizarre IP geo-location anomalies with their tools or services? It's driving me nuts! Any ideas on potential causes or debugging strategies I might be overlooking? Could it be a subtle API change I missed, or something deeper?

Thanks in advance for any insights!