Why is my Geolocation API suddenly having a mid-life crisis?

Hey AdsVolt community!

Hope you're all having a less frustrating day than I am. We run an IP Lookup Tool - Geo-locate Any IP Address & Get Details, and usually, our Geolocation API is an absolute rockstar. Seriously, it's been the most reliable workhorse in our stack for ages. But lately, I swear it's developed a personality disorder – it's started sending perfectly valid IP addresses on imaginary vacations.

The problem is specific and maddeningly intermittent. For certain IP addresses, especially those originating from the APAC region (or so it seems), our tool is either returning wildly inaccurate geolocation data or, even worse, just completely blanking on the city/country. This is new. Last week, everything was hunky-dory, and now it's like our API decided to become a travel agent for fictional destinations.

Of course, I've gone through the usual troubleshooting dance:

• Double-checked all our API keys and credits – everything's active, plenty of headroom. No expired subscriptions or sudden rate limit hits.
• Scoured the Geolocation API provider's documentation and forums for any recent updates, deprecations, or known issues. Crickets. Nothing that explains this specific behavior.
• Ran extensive tests with multiple IPs from various regions. Some resolve perfectly, showing pinpoint accuracy, while others (especially those APAC ones) are just completely off the mark. It's like a roulette wheel.
• Cross-referenced the 'misbehaving' IPs with other reputable public IP lookup services (you know the ones). Every single one of them shows the correct, expected location. This confirms it's our tool's API output that's gone rogue, not the IPs themselves suddenly relocating to Narnia.

Here's a snippet of what I'm seeing. For a specific IP (dummy example, of course), our tool outputs something like this, while other services are totally different:

--- Our Tool's Console Output (Problematic IP) ---
IP Address: 203.0.113.42
Country: United States
Region: California
City: Los Angeles
ISP: Example ISP

--- Expected/Other Services Output ---
IP Address: 203.0.113.42
Country: Singapore
Region: Central
City: Singapore
ISP: Another Example ISP

It's driving me nuts! Has anyone else experienced sudden, inexplicable inconsistencies with their Geolocation API, especially concerning specific regional IP ranges? I'm particularly interested if anyone has faced issues affecting IP geolocation accuracy in the APAC region. Any pointers on debugging this kind of intermittent, 'moody' behavior? Is there some obscure cache setting or GeoIP database update I might be missing?

Thanks in advance for any insights!