IP Databases
Many websites, anti-bot providers, fraud prevention systems, and security platforms rely on third-party IP databases to classify internet traffic.
There are several IP databases that serve critical purposes, such as mapping IPs to ASNs to identify traffic sources and suspicious activity, determining geolocation, detecting proxy or VPN usage, and enforcing access controls.
Why Does This Matter?
Section titled “Why Does This Matter?”When new ISP proxy ranges are deployed or when servers are launched on newly leased IP ranges, it can take time for the IP databases to update their records.
During this update period, some databases may display incorrect geolocation data, outdated ASN ownership information, or incorrect proxy classifications. As a result, certain website ors anti-bot systems may incorrectly classify traffic until the database refresh their records. This behavior is normal and does not necessarily indicate an issue with the proxy itself.
Please note, we would never launch a range that is not ready for the main use cases of our customers. If you are seeing questionable data/classifications on a database, cross check against the databases below.
Commonly Used IP Databases:
Section titled “Commonly Used IP Databases:”- IP2Location – Offers detailed IP geolocation and proxy detection
- IPinfo – Popular for IP enrichment, including ASN, company, privacy flags (VPN/hosting), and geolocation data.
- DB-IP – Provides lightweight IP geolocation and ASN databases
- MaxMind (GeoIP) – One of the most widely adopted databases, heavily used in fraud prevention, e-commerce, and security applications.
You can visit these websites above to check quality of you ISP proxies.
Geolocation Mismatches
Section titled “Geolocation Mismatches”An incorrect geolocation does not mean the server or proxy is physically located elsewhere. IP geolocation data is maintained by third-party databases and can occasionally be inaccurate or outdated.
We host all servers and proxy infrastructure in the locations advertised. If a database reports the wrong city, state, or country, this is typically a geolocation database issue rather than an indication of where the server is actually hosted.
You can often verify the true hosting location by running a latency test to the advertised region on speedtest.net. Latency and network routing will align with the actual hosting location rather than the incorrect geolocation record.