Urgent: IP lookup tool's geolocation failing consistently post-migration, showing incorrect city data.

Hey everyone, I'm completely tearing my hair out over here. Our "What is my City Name" web tool, which was a core utility for our users, is absolutely broken after a recent server migration. It's showing wildly inaccurate results, and frankly, it's making the tool useless.

We recently moved our entire stack from AWS EC2 to a brand new DigitalOcean droplet. The migration itself seemed smooth, and most other services came back online without a hitch. Critically, this tool worked flawlessly before the migration – it was rock solid.

However, the core IP lookup functionality, which is central to determining the user's location via IP geolocation, is now consistently returning incorrect city names. Instead of the user's actual city, it often shows data center locations (like Ashburn, VA, or Frankfurt, Germany) or generic region names such as "United States." This completely defeats the purpose of the tool and makes it unusable for our users.

I've been banging my head against this for hours, trying everything I can think of:

• Verified API keys for our primary geolocation service (MaxMind GeoLite2). Confirmed they are active and correct.
• Checked firewall rules on the new DigitalOcean droplet to ensure outbound API calls aren't being blocked. Everything looks open for standard HTTP/S traffic.
• Confirmed DNS resolution for the geolocation API endpoint. No issues resolving hostnames.
• Tried switching to a different geolocation API (Ipinfo.io) as a sanity check – same incorrect results, which makes me think it's not the API provider itself.
• Cleared all application-level caches, both Redis and local file caches.
• Checked server time and timezone settings on the new droplet. They seem to be configured correctly.

The discrepancy between expected and actual output is stark:

• Expected: User's actual city (e.g., "New York City", "London", "Sydney").
• Actual: Often "Ashburn", "Frankfurt", "Amsterdam", or just "United States" (which are typically data center locations or very broad regions).

Here's a snippet of a typical console output demonstrating the incorrect IP geolocation data being returned:

# User IP: 203.0.113.42 (Example IP, this is a placeholder)
# API Endpoint: https://api.maxmind.com/geoip/v2.1/city/203.0.113.42

{
  "ipAddress": "203.0.113.42",
  "country": {
    "iso_code": "US",
    "name": "United States"
  },
  "city": {
    "name": "Ashburn" 
  },
  "location": {
    "latitude": 39.0437,
    "longitude": -77.4875
  },
  "traits": {
    "isp": "DigitalOcean LLC",
    "organization": "DigitalOcean",
    "connection_type": "Data Center" 
  }
}

I've been banging my head against this for hours and I'm completely stuck. This issue is critical for our tool's functionality. Any insights, suggestions, or even wild guesses would be a lifesaver. Help a brother out please!