Infrastructure Filtering
The problem with infrastructure IPs
A significant portion of internet traffic comes from cloud providers, CDNs, VPNs, and proxies rather than real company networks. Without filtering, these IPs would pollute your account lists with entries like “Amazon Web Services” or “Cloudflare, Inc.” — not the companies you care about.
Evident automatically detects and flags infrastructure IPs so your Accounts dashboard shows real businesses, not hosting noise.
What Evident filters
Evident identifies and flags IPs belonging to:
| Category | Examples |
|---|---|
| Cloud providers | AWS, Microsoft Azure, Google Cloud Platform, Oracle Cloud |
| CDNs | Cloudflare, Akamai, Fastly |
| VPNs | Consumer and commercial VPN services |
| Proxies | Open proxies, anonymous proxies |
| Hosting networks | Generic hosting providers and data center ranges |
Each enriched IP includes boolean flags for each category:
is_cloudis_cdnis_vpnis_proxyis_hosting
How it works in the dashboard
The Accounts page excludes infrastructure IPs from the default view. They are still processed and available in enrichment results (CSV download), but they don’t appear as “companies” in the visitor intelligence dashboard.
This means your account list reflects real organizational visitors — not the infrastructure their traffic passes through.
Infrastructure IPs in enrichment results
In CSV output and API responses, infrastructure IPs are still returned with whatever company data is available, plus the relevant flags set to true. This gives you full visibility while keeping the dashboard clean.
If you need to analyze traffic from specific cloud regions (e.g., you’re tracking API callers or bot traffic), you can use the raw enrichment data with the infrastructure flags as a filter.
False positives
Some legitimate company traffic routes through cloud or VPN infrastructure — for example:
- A company using AWS Workspaces or Azure Virtual Desktop for remote work
- An employee using a corporate VPN that egresses through a data center IP
- A company whose website traffic is proxied through Cloudflare
In these cases, the IP is correctly flagged as infrastructure even though a real company is behind it. This is an inherent limitation of IP-based identification. Confidence scores reflect this uncertainty.