Privacy relay · file snapshot 2026-09-21
iCloud Private Relay IP ranges
The iCloud Private Relay file fetched on 2026-09-21 contained 41,814 distinct IPv4 prefix strings and 243,357 IPv6 prefix strings. Inspect the source URL, recorded fields and content hash below.
- IPv4
- 41,814
- IPv6
- 243,357
- Fetched
- 2026-09-21
- Publisher
- iCloud Private Relay
- Category
- Privacy relay
- IPv4 prefix strings
- 41,814
- IPv6 prefix strings
- 243,357
- File format
- TEXT
- Size
- 12,050,014 bytes
- Fetched (UTC)
- SHA-256
- 88d74dbf1844603d04c7dc4d4d8acadd00e783fcd8fc99f8ade0aa677fd25ff7
File measurement
- 41,814
- IPv4 prefix strings
- 243,357
- IPv6 prefix strings
- 12,050,014
- bytes
- TEXT
- file format
Fields recorded from the file
The parser recorded no publisher version or timestamp field for this file.
No selected facet values were collected by this measurement.
Reproduce the count
provider-file, download the Python measurement script, then run it. The result includes counts, fields and a hash; a different hash means you measured different bytes. Full counting method.python3 ip-ranges-measure.py provider-fileASN reference records
Interpreting this snapshot
- Where is the iCloud Private Relay IP range file?
- The selected snapshot was downloaded from https://mask-api.icloud.com/egress-ip-ranges.csv. The source and documentation links on this page let you inspect the publisher's current data and scope.
- What does a matching prefix establish?
- A match means an address falls inside a prefix in this selected file. The measurement does not establish the identity of a requester, a device location or ownership of every address. Check the publisher’s documentation before applying access rules.
- How often is this file updated?
- This record measures the file fetched at 2026-09-21T19:35:38.821719+00:00. Publisher fields are reproduced as recorded, without inferring a future update schedule. Download the current source and compare hashes to check for a change.
To test an address against a saved file, follow the Python cloud CIDR matching guide. Its example parses AWS JSON; adapt the parser to this publisher's schema and preserve all matching records.
Sources
- [1]https://developer.apple.com/support/prepare-your-network-for-icloud-private-relay/
- [2]https://mask-api.icloud.com/egress-ip-ranges.csv
- [3]https://stat.ripe.net/data/as-overview/data.json?resource=AS36183
- [4]https://stat.ripe.net/data/as-overview/data.json?resource=AS20940
- [5]https://stat.ripe.net/data/as-overview/data.json?resource=AS13335
- [6]https://stat.ripe.net/data/as-overview/data.json?resource=AS54113
A range file lists addresses the publisher attributes to its service. Matching an address against it shows only that the address falls inside a listed prefix; it does not identify the requester or the location of a device.