Carrier-assigned addresses sold as proxies.
Mobile network addresses enrolled into proxy networks. They inherit a carrier's reputation and rotate with the tower.
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 |
|---|---|---|---|---|---|---|
| 142.169.77.36 | floppydata | 2026-06-17 | 2026-08-23 | 5 | 3 | 2 |
| 185.117.151.243 | dataimpulse | 2026-06-18 | 2026-08-06 | 7 | 6 | 2 |
| 84.15.181.69 | dataimpulse | 2026-08-14 | 2026-08-14 | 1 | 1 | 1 |
| 2600:1008:a034:f0d1:fab9:135b:3ef9:293 | floppydata | 2026-06-10 | 2026-06-10 | 1 | 1 | 1 |
| 2a00:23ee:2300:136a:4cd1:51ff:fee0:b836 | floppydata | 2026-07-30 | 2026-07-30 | 1 | 1 | 1 |
The operators behind the ids.
provider is an id that holds from build to build. Mobile 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 | |
| floppydata | Floppydata | https://floppydata.com/ | t | f | |
| vibeproxies | VibeProxies | https://vibeproxies.com/ | t | f |
Downloading it from code.
Database API reference →One call gets you the current Mobile 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 Mobile Proxy IP is bought for, and what each needs from the data rather than from a score.
Carrier NAT hides a lot
One mobile address can front thousands of real customers, so blocking it outright is expensive. Knowing it is also a proxy exit changes the calculus.
The premium tier of abuse
Mobile proxies cost the most and are used where the target is most valuable: account takeover, ticketing, sneaker drops.
Rotation is fast
Addresses move between customers within hours, which is why first seen and last seen matter more here than anywhere else.
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 mobile 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.
Why does persistence matter more here?
Carriers rotate addresses among many subscribers, so a mobile proxy exit can be someone's ordinary phone a day later. first_seen, last_seen and hits_days_pct say how long each address has stayed a proxy.
Should we block a mobile proxy address?
Rarely outright. A carrier puts many subscribers behind one address, so the same address can be a proxy exit and an ordinary phone at once: a challenge costs the real customer far less than a block.
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 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 Mobile 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 asks us for a slice of the current build.
Is it the same data the API answers from?
Yes. A lookup's is_mobproxy 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}