IP lookup acting wonky?

hey folks,

i'm scratching my head over here with my little web tool, What is My ISP? - Find Your Internet Service Provider. for the longest time, it's been pretty solid, you know? you punch in an IP, it tells you the ISP, city, all that good stuff. but lately, it's like it's developed a mind of its own, giving me some truly bizarre or just plain wrong isp results for some users.

the problem is, for certain ip addresses, instead of showing what i'd expect (like, say, comcast or at&t), it's either returning 'unknown', or even weirder, a generic data center name. sometimes it's just completely off the mark. and it's not consistent, which is the most frustrating part. one minute an IP address lookup is spot on, the next it's having an identity crisis. this inconsistency is really messing with my data for ISP identification.

i've tried a few things already:

• checked my geoip database (maxmind) – it's updated regularly, so that shouldn't be the issue.
• tested with various vpns and proxies to simulate different user locations and isps – some work perfectly, some completely fail and show the wrong info.
• monitored server logs for any obvious errors or api timeouts – nothing screamingly obvious is popping up. it's all very quiet, which is almost worse.
• cross-referenced results with other ip lookup tools – and they often show the correct isp where mine just throws its hands up.

here’s a little peek at what i’m seeing sometimes. it's kinda silly, really:

// Expected Output (for a known IP, say, from my neighbor)
ISP: 'Comcast Cable Communications, LLC'
City: 'Philadelphia'

// Actual Output (for the same IP, sometimes, just to mess with me)
ISP: 'Amazon Technologies Inc.'
City: 'Ashburn'
// or even worse...
ISP: 'Unknown'
City: 'N/A'

i'm wondering if maybe it's an issue with a specific ip range being miscategorized upstream by some provider? or could i be hitting some sort of silent rate limit with my geoip provider or a secondary api i use for verification? maybe there's a super common pitfall when integrating isp data that i'm totally overlooking, like some cache invalidation issues that are only affecting certain lookups?

looking for anyone who's faced similar issues with their ISP identification tools or geoip data. any insights, debugging tips, or alternative approaches would be super helpful. this little bugger is really starting to get on my nerves.

help a brother out please...