iCloud Private Relay IP ranges
iCloud Private Relay uses 41,768 IPv4 blocks and 243,361 IPv6 blocks, covering about 105,681 unique IPv4 addresses. IPDebrief has analysed 92 addresses in these ranges; 0 (0%) currently carry a higher risk score.
- IPv4 blocks
- 41,768
- IPv6 blocks
- 243,361
- Unique IPv4 addresses
- 105,681
- Countries
- 235
- Analysed addresses
- 92
- Higher risk
- 0%
Range data updated 2026-11-07
About iCloud Private Relay
iCloud Private Relay is Apple's privacy service for iCloud+ subscribers. It sends Safari traffic through two separate relays so that no single party sees both the user's address and the site visited. Apple publishes the egress ranges with the country and region each one represents, so sites can still localise content without learning the user's address.
What traffic from iCloud Private Relay addresses usually means
Traffic from Private Relay egress addresses is almost always a real person using Safari on an Apple device, not a bot or a commercial VPN. Many users share each egress address, so per-address blocking or rate limiting can affect many legitimate visitors at once.
How to verify a iCloud Private Relay IP address
Check the address against Apple's published egress ranges. The geolocation attached to each range is the user's approximate region, not the location of the relay server.
Largest iCloud Private Relay IPv4 ranges
172.225.75.0/24172.225.76.0/24172.225.90.0/24172.225.113.0/24172.225.237.0/24172.226.30.0/24172.226.222.0/24172.225.5.0/25
Top countries by address blocks
- 馃嚭馃嚫 United States
- 馃嚛馃嚜 Germany
- 馃嚙馃嚪 Brazil
- 馃嚡馃嚨 Japan
- 馃嚚馃嚦 China
- 馃嚚馃嚘 Canada
- 馃嚠馃嚦 India
- 馃嚞馃嚙 United Kingdom
- 馃嚝馃嚪 France
- 馃嚪馃嚭 Russia
- 馃嚠馃嚬 Italy
- 馃嚫馃嚜 Sweden
Recently analysed iCloud Private Relay addresses
- 104.28.141.165
- 104.28.147.176
- 172.225.189.205
- 104.28.140.195
- 172.226.108.4
- 172.225.120.98
- 172.225.176.248
- 172.225.120.105
- 104.28.142.172
- 104.28.142.164
- 104.28.143.216
- 104.28.143.209
- 104.28.147.112
- 104.28.142.167
- 104.28.142.212
- 104.28.142.168
- 104.28.42.52
- 104.28.140.193
- 104.28.147.180
- 104.28.143.213
- 104.28.141.63
- 104.28.42.37
- 104.28.143.210
- 104.28.143.211
- 172.225.116.172
- 104.28.140.200
- 104.28.140.66
- 104.28.147.175
- 104.28.139.154
- 104.28.42.22
- 172.225.189.204
- 172.226.29.19
- 172.226.148.34
- 104.28.142.206
- 140.248.41.24
- 104.28.143.215
- 104.28.141.169
- 104.28.143.214
- 104.28.142.165
- 172.226.148.35
- 104.28.141.192
- 104.28.42.47
- 104.28.62.14
- 104.28.139.156
- 140.248.41.25
- 104.28.143.241
- 172.226.29.18
- 104.28.138.131
- 104.28.149.188
- 104.28.136.48
- 104.28.151.15
- 104.28.143.67
- 104.28.151.17
- 104.28.151.7
- 104.28.135.19
- 104.28.137.81
- 104.28.151.19
- 104.28.147.177
- 104.28.151.14
- 104.28.142.217
Frequently asked questions
How many IP addresses does iCloud Private Relay have?
iCloud Private Relay uses 41,768 IPv4 and 243,361 IPv6 address blocks. After merging overlapping ranges, the IPv4 blocks cover about 105,681 unique addresses. Counts change as the provider adds, retires or transfers address space.
How can I check if an IP address belongs to iCloud Private Relay?
Enter the address in the IPDebrief IP lookup. If it falls inside one of iCloud Private Relay's ranges, the profile names the provider alongside the announcing network, location and risk signals. Check the address against Apple's published egress ranges. The geolocation attached to each range is the user's approximate region, not the location of the relay server.
Is traffic from iCloud Private Relay IP addresses safe?
Traffic from Private Relay egress addresses is almost always a real person using Safari on an Apple device, not a bot or a commercial VPN. Many users share each egress address, so per-address blocking or rate limiting can affect many legitimate visitors at once. Of the 92 iCloud Private Relay addresses IPDebrief has analysed, 0 (0%) currently score as higher risk, so judge each address on its own profile.
Where does this IP range data come from?
Ranges are compiled from address lists the operator publishes and from global routing data, refreshed regularly. Address-level risk comes from independent observations of each address, recomputed in the background.