Proxy detection failing hard

man, i'm still totally stuck on this vpn detection thing. thought i had a handle on it after the last thread, but it's just gotten worse. we're trying to prevent abuse but it's just hurting legit users now.

i integrated a new proxy detection service, hoping it'd be more robust, but it's acting super erratic. it's flagging some perfectly clean residential ips as proxies, blocking them, and then letting obvious datacenter ips right through. our support inbox is full of complaints. this is so frustrating cause the whole point was to improve accuracy.

Here's what i'm seeing in my console when it acts up:

Attempting IP lookup for 192.168.1.100...
Detected as: CLEAN (Legitimate Residential)

Attempting IP lookup for 10.0.0.5...
Detected as: PROXY (Flagged - VPN/TOR/Datacenter)
... (user reports this is a legit home IP)

Attempting IP lookup for 203.0.113.12 (known bad proxy)...
Detected as: CLEAN (No Proxy Detected)
... (this should have been flagged!)

Error: Inconsistent proxy detection results.

is there some trick to calibrating these services, or am i missing a fundamental approach to robust proxy detection? anyone faced this before with services being too aggressive or too lax at the same time?