Mobile carrier space, by operator.
Address ranges mobile network operators assign to their subscribers, with the operator, its MCC and MNC, and the country, so a phone on cellular data is not mistaken for a proxy.
Schema at a glance.
See documentation →The database's schema and metadata are documented carefully. It is published as CSVGZ and MMDB.
| start_ip | end_ip | name | mcc | mnc | country | confidence |
|---|---|---|---|---|---|---|
| 2.165.13.0 | 2.165.14.255 | Telekom | 262 | 01 | DE | high |
| 12.35.116.0 | 12.35.134.255 | AT&T | 310 | 410 | US | high |
| 31.160.238.0 | 31.160.241.255 | KPN | 204 | 08 | NL | high |
| 46.97.244.0 | 46.97.255.255 | Vodafone | 226 | 01 | RO | high |
| 2409:8a2a:9500:: | 2409:8a2a:98ff:ffff:ffff:ffff:ffff:ffff | China Mobile | 460 | 00 | CN | high |
Downloading it from code.
Database API reference →One call gets you the current Carrier 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()import osfrom internetdata import InternetDataclient = InternetData(os.environ["INTERNETDATA_API_KEY"])# what is in today's build, without moving the filemeta = client.database.metadata("carrier_ip_v1")client.database.download("carrier_ip_v1", "mmdb", "./carrier_ip_v1.mmdb")sums = client.database.checksums("carrier_ip_v1", "mmdb")print(meta.updated, meta.entries, sums["sha256"])
Getting your hands on it.
The file is the product. Teams join Carrier IP against traffic they already log, inside their own infrastructure, and never send an address anywhere to get an answer.
Account and payment risk
Tell a phone on cellular data from a proxy, so a mobile customer is not challenged for an address their carrier shares.
Analytics
Segment traffic by mobile operator and country.
An official client for every major language.
All SDKs on GitHub →Twelve official clients for the languages you ship in, each wrapping the database endpoints — list what you are licensed for, poll a build, follow the download redirect, verify what landed. Install commands are in the docs.
No loose ends.
How often does this database rebuild?
Daily. The metadata call answers when the current build landed and how many rows it holds, before you fetch it.
What is in a row?
One range: a start and an end address, both inclusive, and what this database says about it. IPv4 and IPv6 are in the same file.
Which formats does a build ship in?
Gzipped CSV and MMDB, both cut from the same build. The schema section above names them.
Test the real build first.
An evaluation license puts a full current build in your hands — every row, every column, no sampling — so you can measure it against your own traffic before anyone talks about terms.