iCloud Private Relay’s Exit Network

Home › Guides › iCloud Private Relay’s Exit Network

✓ checked 17 October 2026 · sources: Apple’s iCloud Private Relay egress list, iptoasn.com · method · caveats · download the data

The list of exit addresses Apple publishes for iCloud Private Relay covers 105,647 IPv4 addresses and 243,357 IPv6 prefixes in 235 country codes. Routing data from iptoasn.com puts 66.2% of the IPv4 addresses on Akamai’s networks, 18.7% on Cloudflare’s and 15.2% on Fastly’s. These are the addresses websites see when someone with an iCloud+ subscription browses in Safari with Private Relay turned on.

IPv4 exit addresses 105,647on Akamai 66.2%in the US 43.0%

Headline findings

  1. Three networks carry all of it. Every address on the list maps to one of four autonomous systems: Akamai’s AS36183 (59,354 IPv4 addresses) and AS20940 (10,560), Cloudflare’s AS13335 (19,723) and Fastly’s AS54113 (16,010). Akamai’s share is larger still for IPv6, at 85.5% of prefixes, against 27,238 for Cloudflare and 8,005 for Fastly.
  2. The list is mostly IPv6. Of its 285,091 entries, 85.4% are IPv6 prefixes, 204,970 of them /64s; 41,734 are IPv4 prefixes.
  3. The US has 45,409 IPv4 exit addresses, the most of any country, followed by Japan with 3,657. Entries name 15,685 country-and-city pairs; 2,176 entries give a region but no city.
  4. Apple designs the addresses to keep a user’s region, not their identity. Apple says Private Relay “preserves the region the user is in, so your server can trust the region assigned to the IP address it sees”, and that “The assigned relay IP address may be shared among more than one Private Relay user in the same area”. For sites, one address on this list can stand for many Apple users in the same area.

By network

iCloud Private Relay egress IPv4 addresses by networkAkamaiAkamai: 69,91469,914CloudflareCloudflare: 19,72319,723FastlyFastly: 16,01016,010
IPv4 addresses on Apple’s egress list, 17 October 2026, by the network iptoasn.com shows announcing them. Sources: Apple; iptoasn.com.
ASNNameOperatorIPv4 addressesShareIPv6 prefixes
AS36183AKAMAI-ASAkamai59,35456.2%167,272
AS13335CLOUDFLARENETCloudflare19,72318.7%27,238
AS54113FASTLYFastly16,01015.2%8,005
AS20940AKAMAI-ASN1Akamai10,56010.0%40,842

By country

iCloud Private Relay egress IPv4 addresses by country, top 15USUS: 45,40945,409JPJP: 3,6573,657CACA: 2,5032,503ININ: 2,0832,083BRBR: 2,0692,069DEDE: 1,9501,950GBGB: 1,9021,902RURU: 1,7241,724MXMX: 1,2591,259KRKR: 1,2351,235CNCN: 1,0751,075AUAU: 1,0711,071FRFR: 940940ESES: 785785TRTR: 758758
IPv4 exit addresses by the country code Apple assigns, top 15. Source: Apple.

Our proxy checker flags addresses on this list as iCloud Private Relay. For the protocol Private Relay is built on, see the MASQUE tracker, and for how other companies publish the address ranges of their automated traffic, AI Fetcher IP Ranges.

Method

On 17 October 2026 we downloaded Apple’s egress list from mask-api.icloud.com, merged overlapping IPv4 prefixes and counted addresses, and matched each IPv4 range and each IPv6 prefix’s first address against iptoasn.com’s routing tables downloaded the same day. A separate script recomputes every number from the saved files.

Caveats

  • The network shown is the one announcing the address in iptoasn.com’s data. Apple doesn’t label the list by operator.
  • Country and city are Apple’s assignments for the user’s region, not where the servers are.
  • IPv6 prefixes vary in size from /40 to /64, so we count prefixes rather than addresses.
  • The list changes often. We couldn’t retrieve Wayback Machine history for it, so this page is a single snapshot.

Download the data

  • By network (CSV): ASN, name, operator, IPv4 addresses, IPv6 prefixes.
  • By country (CSV): IPv4 prefixes and addresses and IPv6 prefixes per country code.

Cite as: ProxyPicker, “iCloud Private Relay’s Exit Network”, 17 October 2026, https://proxypicker.com/icloud-private-relay-egress/. Data: Apple, iptoasn.com.

Related: Proxy checker · MASQUE tracker · AI Fetcher IP Ranges.

Press & data requests: email [email protected] for interviews, the raw data behind this page, or corrections. See also our contact page.