IP range registry · snapshot 2026-09-21

Cloud and datacenter IP range files

Inspect 20 public files from cloud platforms, CDNs and other networks. Each record shows the source, measured prefix counts and a content hash you can compare with your own download.

20
selected provider files
116,237
IPv4 prefix strings
267,064
IPv6 prefix strings
60
distinct ASN reference records
Explore the datasetDownload JSON

Totals add each file’s counts. Overlapping networks and overlap between providers are retained.

All provider files

Prefix strings counted in each downloaded file. Select a provider for its source URL, hash, sample prefixes and ASN records.

20 files

Cloud and datacenter IP range files
NameIPv4IPv6
Amazon Web Services IP rangesCloud platform7,7993,478
Microsoft Azure IP rangesCloud platform45,16016,858
Google Cloud IP rangesCloud platform1,00895
Google IP rangesCloud platform13015
Cloudflare IP rangesCDN157
Fastly IP rangesCDN192
Oracle Cloud Infrastructure IP rangesCloud platform1,107220
DigitalOcean IP rangesCloud platform1,082148
Akamai Connected Cloud (Linode) IP rangesCloud platform5,40996
Vultr IP rangesCloud platform44555
GitHub IP rangesSaaS6,1191,515
Zscaler IP rangesSecurity835223
Atlassian IP rangesSaaS175123
Bunny.net IP rangesCDN5870
Imperva IP rangesSecurity111
Gcore IP rangesCDN992849
Okta IP rangesSaaS2,1160
Salesforce IP rangesSaaS3922
iCloud Private Relay IP rangesPrivacy relay41,814243,357
Tor IP rangesAnonymity network1,3750

Cloud platforms

Compare the selected files for cloud providers. A file may cover only part of a provider’s services.

Content delivery networks

Published range files grouped by CDN provider, with separate IPv4 and IPv6 counts.

Application platforms

Selected files for software platforms. Read the linked documentation for each file’s scope.

Security services

File measurements for security services, with source links and fetch dates.

Privacy relays

Relay address files are listed separately from cloud and hosting files.

Anonymity networks

Individual addresses are counted as host prefixes: /32 for IPv4 and /128 for IPv6.

Reproduce a file measurement

Download the source linked on a provider page and run our Python script against that saved file. It validates address strings, counts distinct entries and hashes the bytes. Matching hashes let you compare measurements of the same file.

Download the Python counting script or read the counting rules and limitations.

Using these records

What do the counts measure?
Distinct valid prefix strings within each downloaded file. An individual IPv4 or IPv6 address becomes a /32 or /128 host prefix. Nested and overlapping ranges remain separate. The total adds the per-file counts; it is not a count of unique IP addresses across providers.
Does a range match identify a datacenter or a person?
It establishes that the address falls inside a range in the selected file. This registry does not measure ownership, the original user, traffic intent or the location of a device. Read each provider’s documentation before interpreting a match.
How current is this registry?
Every file has its own recorded fetch time and SHA-256 hash. The pages are dated snapshots. Use the linked source for current data and compare its hash before expecting the same results.
Does the registry cover every provider and network?
No. It measures 20 selected public files. A missing address or provider is not evidence that an address belongs to a residential network. Provider categories organize the reference; they are not classifications of every address in a file.

Use a range file in your application

Follow the Python cloud CIDR matching guide to retain overlapping records and source hashes. For search crawler identity, use the Googlebot and Bingbot verification procedure with crawler-specific sources.

Research library

Network registries & open data

Find the reference behind a network decision. Browse the records, follow their sources and download the available datasets.

Explore research