Rotating proxy pools on leased infrastructure.
Proxy exits running on datacenter address space, with observation counts across a rolling ninety-day window.
Schema
See documentation →Published as CSVGZ and MMDB. Every column is described in the docs.
| ip | provider | first_seen | last_seen | hits | hits_days_pct | providers_num |
|---|---|---|---|---|---|---|
| 46.203.63.189 | floppydata | 2026-06-11 | 2026-07-30 | 13 | 9 | 3 |
| 18.237.13.41 | floppydata | 2026-07-06 | 2026-09-04 | 9 | 8 | 2 |
| 45.67.3.193 | floppydata | 2026-08-29 | 2026-09-06 | 2 | 1 | 2 |
| 52.52.254.47 | floppydata | 2026-06-30 | 2026-06-30 | 1 | 1 | 1 |
| 217.80.249.248 | floppydata | 2026-08-30 | 2026-08-30 | 1 | 1 | 1 |
The operators behind the ids.
provider is an id that holds from build to build. Datacenter Proxy Provider resolves each one to the provider's name and homepage, whether we track its addresses and whether it has gone defunct. Join it on provider.
| id | name | url | active | note | defunct |
|---|---|---|---|---|---|
| dataimpulse | DataImpulse | https://dataimpulse.com/ | t | f | |
| ipvanish | IPVanish | https://www.ipvanish.com/ | t | VPN service that offers a SOCKS5 proxy via datacenter nodes. | f |
| privateproxy_me | PrivateProxy.me | https://privateproxy.me/ | t | f |
Downloading it from code.
Database API reference →One call gets you the current Datacenter Proxy IP build. Every official client wraps it three ways: straight to disk, a time-limited link you hand to your own runner, or bytes in memory. A file written to disk lands only once the whole transfer has arrived, and checksums() returns the published digests to verify it against.
download()downloadUrl()downloadBytes()metadata()checksums()What it's used for
Three decisions Datacenter Proxy IP is bought for, and what each needs from the data rather than from a score.
Cheap abuse arrives here first
Datacenter proxies are the lowest-cost way to rotate an address, which makes them the highest-volume source of automated abuse.
Distinct from plain hosting
A server range is not necessarily a proxy. This dataset is the subset actually observed exiting proxy traffic.
Rotation is visible
First seen, last seen and hit counts show how a pool churns, so short-lived exits can be scored differently.
Official SDKs
All SDKs on GitHub →Twelve official clients, each wrapping the database endpoints as well as the lookup: list what you're licensed for, poll a build, follow the download redirect. Install commands are in the docs.
Common questions
What does a row tell us?
One address seen exiting a datacenter proxy pool in the window, the provider that sold it, the first and last day it appeared, how many times, the share of days it appeared on, and how many providers resold it.
How is it different from Hosting IP?
Hosting IP is the space hosting providers own. This is the individual addresses inside it that we saw a proxy service sell as exits: one says an address is infrastructure, the other that someone is renting it out.
Which window should we use?
90 days is the widest net. The 1, 7, 14, 30 and 60-day windows are the same observations over shorter spans, each its own dataset, for when an address seen two months ago is too old to act on.
How do we read hits and hits_days_pct?
hits counts the observations in the window and hits_days_pct is the share of its days the address appeared on. An address seen most days is a standing exit; one seen once may have joined a pool for an afternoon.
How often is it rebuilt?
Daily, over a rolling 90-day window that first_seen and last_seen fall inside. The metadata call says when the current build landed and how many rows it holds, so you fetch only a new one.
Which formats does it ship in?
Gzipped CSV and MMDB, both cut from the same build. The MMDB opens in any MaxMind DB reader, so lookups run in memory on your own servers.
How do we get it?
Under a database license, agreed per dataset and bundled with Enterprise plans. Request access names Datacenter Proxy IP to us, and once it's licensed it downloads from the console, the database API or any official client, or each new build is announced to your webhook, or written to your AWS S3 or S3-compatible storage, Google Cloud Storage, Azure Blob Storage, or an SFTP or FTPS server. Download sample gets you rows from the current build first.
Is it the same data the API answers from?
Yes. A lookup's is_dcproxy comes from these builds, so the file and the API agree on an address.
What if a row looks wrong?
Send it to us and we'll tell you what we hold on it, when we last saw it and how. Corrections land in the next build.
Start without signing up.
Paste it into a terminal. No account needed. 1,000 lookups a day per address, answering ip and is_vpn.
{"ip": "146.70.116.130","is_vpn": true}