Network research / 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.
Totals add each file’s counts. Overlapping networks and overlap between providers are retained.
Cloud platforms
Compare the selected files for cloud providers. A file may cover only part of a provider’s services.
Amazon Web Services IP ranges
11,277 prefix strings
7,799 IPv4 / 3,478 IPv6
ip-ranges.amazonaws.com
Microsoft Azure IP ranges
62,018 prefix strings
45,160 IPv4 / 16,858 IPv6
download.microsoft.com
Google Cloud IP ranges
1,103 prefix strings
1,008 IPv4 / 95 IPv6
www.gstatic.com
Google IP ranges
145 prefix strings
130 IPv4 / 15 IPv6
www.gstatic.com
Oracle Cloud Infrastructure IP ranges
1,327 prefix strings
1,107 IPv4 / 220 IPv6
docs.oracle.com
DigitalOcean IP ranges
1,230 prefix strings
1,082 IPv4 / 148 IPv6
www.digitalocean.com
Akamai Connected Cloud (Linode) IP ranges
5,505 prefix strings
5,409 IPv4 / 96 IPv6
geoip.linode.com
Vultr IP ranges
500 prefix strings
445 IPv4 / 55 IPv6
geofeed.constant.com
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.
GitHub IP ranges
7,634 prefix strings
6,119 IPv4 / 1,515 IPv6
api.github.com
Atlassian IP ranges
298 prefix strings
175 IPv4 / 123 IPv6
ip-ranges.atlassian.com
Okta IP ranges
2,116 prefix strings
2,116 IPv4 / 0 IPv6
s3.amazonaws.com
Salesforce IP ranges
61 prefix strings
39 IPv4 / 22 IPv6
ip-ranges.salesforce.com
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.
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.
Research library
Network registries & open data
Find the reference behind a network decision. Browse the records, follow their sources and download the available datasets.