What are robust strategies for proxy detection in geo-targeting?

Hey everyone, following up on the recent discussion about geolocation API accuracy, our SaaS is running into some significant issues with users masking their true locations. We rely heavily on accurate geo-targeting for content delivery and compliance, and this has become a real headache.

The problem is that a growing number of users appear to be utilizing proxies or VPNs, leading to highly inaccurate IP geolocation data. This directly impacts our ability to enforce regional restrictions and deliver region-specific features correctly, which is critical for us.

What we've tried so far: We've integrated with a couple of the leading IP geolocation providers (e.g., MaxMind, IPinfo), which offer built-in proxy detection flags. We've also attempted to maintain our own custom IP blacklists for known VPN/proxy ranges.

However, we've hit some limitations and observations:

• The is_proxy or vpn_detected flags from standard APIs are often inconsistent or fail to identify newer services, especially residential proxies.
• Maintaining a blacklist is a constant, resource-intensive battle against ever-changing IP ranges, and it feels like we're always playing catch-up.
• The APIs often return the location of the proxy server, not the user's actual physical location, which completely defeats our geo-targeting efforts.

To give you a clearer picture, here's a fake console output example of what we often see:

// Pseudocode for a user session where geo-targeting fails
const userIP = "198.51.100.25"; // Example IP, often from a data center or proxy

// Result from a typical Geolocation API with proxy detection
const geoApiResult = {
  ip: userIP,
  country: "US",
  city: "Ashburn",
  region: "VA",
  asn: "AS16509", // Amazon.com, Inc.
  is_proxy: true,
  proxy_type: "datacenter",
  vpn_detected: "high_confidence"
};

console.log("User IP:", userIP);
console.log("Geolocation API Result:");
console.log("  Country:", geoApiResult.country);
console.log("  City:", geoApiResult.city);
console.log("  Is Proxy:", geoApiResult.is_proxy);
console.log("  VPN Detected:", geoApiResult.vpn_detected);

console.log("\nOur internal analytics/user profile suggests actual user location: Germany.");
console.log("This discrepancy allows users to bypass region-specific content.");

Given these challenges, what are the most effective strategies, advanced tools, or specific services for robust proxy detection and VPN identification that go beyond the standard API flags, ensuring accurate geo-targeting when it's absolutely critical for our business model?